Enabled hardware type 'ucs' does not exist

Bug #1752975 reported by Mark Goddard on 2018-03-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bifrost
In Progress
Undecided
Mark Goddard

Bug Description

During classic driver deprecation [1], the ucs hardware type was added to the list of default enabled hardware types. This hardware type does not exist - the Cisco UCS hardware types are cisco-ucs-managed and cisco-ucs-standalone. This causes conductor to fail to start.

This was not caught during testing as only the ipmi ironic hardware type is configured when testing. Now that VBMC is in use, perhaps it is no longer necessary to use a different set of drivers for testing?

[1] https://github.com/openstack/bifrost/commit/46453661badf83c2c45a008908d4476de6785ccd

Mark Goddard (mgoddard) wrote :

With cisco-ucs-managed and cisco-ucs-standalone added, I now hit this:

2018-03-02 20:24:32.571 29979 ERROR ironic.conductor.base_manager [req-8d5e6af3-307c-43ed-a579-3304bbfd4e81 - - - - -] Failed to register hardware types. For hardware type 'ilo', no default value found for management interface.: NoValidDefaultForInterface: For hardware type 'ilo', no default value found for management interface.

Mark Goddard (mgoddard) wrote :

Looking are the hardware type code, I think cisco types load ok because they support IPMI management interface. Ilo requires the Ilo specific management interface, which is not enabled by default.

Mark Goddard (mgoddard) wrote :
Changed in bifrost:
status: New → In Progress
assignee: nobody → Mark Goddard (mgoddard)
Michael Still (mikal) wrote :

I have a related issue, as posted on openstack-dev at http://lists.openstack.org/pipermail/openstack-dev/2018-March/127886.html . I'll patch in this change and redeploy and see if that helps.

Michael Still (mikal) wrote :

This patch resolves my node enrolment problems. I now have entries in "ironic driver-list" and "ironic node-enroll" runs without error.

This issue was fixed in the openstack/bifrost 5.0.1 release.

This issue was fixed in the openstack/bifrost 5.1.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers