Red Hat Bugzilla – Bug 1489655
IPMI User is optional for some BMCs but tripleo requires it to be in instackenv.json
Last modified: 2018-08-29 12:35:50 EDT
Description of problem: IMPI User is optional for some BMCs but tripleo requires it to be in instackenv.json. Version-Release number of selected component (if applicable): openstack-tripleo-common all versions python-tripleoclient all versions How reproducible: 100% for FSP based POWER8 systems no username is expected.
I'm not certain how to link this correctly to flag this is needed in RHOS 12 if https://bugzilla.redhat.com/show_bug.cgi?id=1491837 is approved
Tony - if https://bugzilla.redhat.com/show_bug.cgi?id=1491837 is approved and merged you could clone this bug and set the rhos-12 flag.
Changed flags to osp-13, we shouldn't need to create another BZ.
Tony - per your last comment in the associated fix -https://review.openstack.org/#/c/501937/, it looks like this is being pushed to Rocky. Setting flags accordingly.
Hey Bob, It's being pushed to Rocky with Queens backports so we'll deliver this via 13.0.z Once that flag is available I'll go through and setup the target releases and flags appropriately.
Installed latest OSP13 cat /etc/yum.repos.d/latest-installed 13 -p 2018-08-07.4 Verified gerrit changes are included in this release. Please reopen if this issue still persists.
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
The docs associated with this bug are going to be delivered outside of the Errata process and are being tracked at: https://bugzilla.redhat.com/show_bug.cgi?id=1599782
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2574