Bug 1319841
Summary: | openstack-ironic-conductor service failing silently with bad config | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Harry Rybacki <hrybacki> |
Component: | openstack-ironic | Assignee: | Lucas Alvares Gomes <lmartins> |
Status: | CLOSED ERRATA | QA Contact: | Raviv Bar-Tal <rbartal> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 (Kilo) | CC: | ddomingo, dtantsur, jschluet, mburns, rhel-osp-director-maint, srevivo |
Target Milestone: | Upstream M3 | Keywords: | Triaged |
Target Release: | 10.0 (Newton) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-ironic-6.1.1-0.20160823055226.46dc395.el7ost | Doc Type: | Bug Fix |
Doc Text: |
The openstack-ironic-conductor service now checks whether all drivers specified in the 'enabled_drivers' option are unique. The service then removes duplicated entries and logs a warning. In previous releases, duplicate entries in the 'enabled_drivers' option simply caused the openstack-ironic-conductor service to fail, thereby preventing the Bare Metal provisioning service from loading any drivers.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-14 15:29:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harry Rybacki
2016-03-21 16:05:45 UTC
Thanks for filling this out, I've opened a bug upstream and submitted a fix for it. I can backport it once it's merged there. (added links to the external trackers) Merged in OSP 10 and I've proposed a backport to OSP 9. This bug is verified. New bug was open with some more enabled_driver formatting problem causing conductor to fail without error message https://bugzilla.redhat.com/show_bug.cgi?id=1377103 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://rhn.redhat.com/errata/RHEA-2016-2948.html |