Bug 1645571
Summary: | ironic-inspector introspection fails when updating port with missing switch_id | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Bob Fournier <bfournie> | |
Component: | openstack-ironic-inspector | Assignee: | Bob Fournier <bfournie> | |
Status: | CLOSED ERRATA | QA Contact: | mlammon | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 13.0 (Queens) | CC: | bfournie, dwojewod, jschluet, mariel, mburns, mlehmann, slinaber | |
Target Milestone: | z4 | Keywords: | Triaged, ZStream | |
Target Release: | 13.0 (Queens) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-ironic-inspector-7.2.1-5.el7ost | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1655076 (view as bug list) | Environment: | ||
Last Closed: | 2019-01-16 17:56:44 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1655076 |
Description
Bob Fournier
2018-11-02 14:42:23 UTC
Regarding the attached case, as a workaround the customer should edit /etc/ironic-inspector/inspector.conf and remove the "local_link_connection" field from this line: processing_hooks=$default_processing_hooks,extra_hardware,lldp_basic,local_link_connection then restart ironic-inspector 13 -p 2018-12-13.4 Env: openstack-ironic-inspector-7.2.1-5.el7ost.noarch We see the new code in place. This should no longer be an issue. Please re-open or file new BZ if issue still seen from ironicclient import exceptions try: node_info.patch_port(port, patches) except exceptions.BadRequest as e: LOG.warning("Failed to update port %(uuid)s: %(error)s", {'uuid': port.uuid, 'error': e}, node_info=node_info) 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-2019:0092 |