Bug 1480699 - instackenv validate not supporting custom ports
instackenv validate not supporting custom ports
Status: ASSIGNED
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient (Show other bugs)
11.0 (Ocata)
Unspecified Unspecified
low Severity low
: ---
: 11.0 (Ocata)
Assigned To: Dmitry Tantsur
mlammon
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-11 13:45 EDT by Gregory Charot
Modified: 2017-08-23 09:25 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1712568 None None None 2017-08-23 08:59 EDT

  None (edit)
Description Gregory Charot 2017-08-11 13:45:38 EDT
Description of problem:

OSP11 introduces the usage of Virtual BMC to simulate IPMI on libvirt VMs.

When configuring Virtual BMC we need to specify the ip and port on which the VBMC should listen to. This ip/port is then referenced into the instackenv json file.

If the user specify a non standard IPMI port (623) the instackenv validation fails with the following error.

Error: Unable to establish IPMI v2 / RMCP+ session
ERROR: ipmitool failed

Skipping validation, registering nodes and introspecting them works fine.

Version-Release number of selected component (if applicable):
11

How reproducible:
Always

Steps to Reproduce:
1. Configure virtual bmc - use non standard ports
2. create an instackenv json file
3. run openstack baremetal instackenv validate

Actual results:
For each node:
Error: Unable to establish IPMI v2 / RMCP+ session
ERROR: ipmitool failed

If running verbose:
Checking node 192.168.122.1
Identified baremetal node
Executing: ipmitool -R 1 -I lanplus -H 192.168.122.1 -U admin -P xxx chassis status
Error: Unable to establish IPMI v2 / RMCP+ session
ERROR: ipmitool failed

We can see that the cli is not passing the -p port option and instead uses the default port.

Expected results:

cli should use the port referenced into the instackenv (pm_port)

Additional info:



# vbmc list
+---------------------+---------+---------+------+
|     Domain name     |  Status | Address | Port |
+---------------------+---------+---------+------+
|   overcloud-ceph01  | running |    ::   | 6230 |
|   overcloud-ceph02  | running |    ::   | 6231 |
|   overcloud-ceph03  | running |    ::   | 6232 |
| overcloud-compute01 | running |    ::   | 6233 |
| overcloud-compute02 | running |    ::   | 6234 |
|   overcloud-ctrl01  | running |    ::   | 6235 |
|   overcloud-ctrl02  | running |    ::   | 6236 |
|   overcloud-ctrl03  | running |    ::   | 6237 |
| overcloud-networker | running |    ::   | 6238 |
+---------------------+---------+---------+------+

instackenv:

  "nodes": [
    {
      "pm_user": "admin",
      "mac": [
        "52:54:00:1b:b1:ee"
      ],
      "pm_type": "pxe_ipmitool",
      "pm_port": "6235",
      "pm_password": "xxx",
      "pm_addr": "192.168.122.1",
      "capabilities": "profile:control",
      "name": "overcloud-ctrl01"
    },
(...)
Comment 1 Dmitry Tantsur 2017-08-23 06:58:32 EDT
Hi! Indeed, this command has not been updated for ages. We have a new validation workflow that should be used instead. This should be easy to fix for OSP 12, but for 11 is requires backporting this new workflow. I will ask the folks if it's possible. If it's not, I'll fix it for 12 on.

A workaround is to not use this command for now.

Note You need to log in before you can comment on or make changes to this bug.