Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1620245

Summary: openstack baremetal node bios setting list <NODE ID> error: 404 not found
Product: Red Hat OpenStack Reporter: bjacot
Component: python-ironicclientAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: bjacot
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: apevec, bfournie, dtantsur, jkreger, lhh, mburns, mlammon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
OSP14 virtual env 1: undercloud-0 2: overcloud
Last Closed: 2018-08-28 08:26:17 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 bjacot 2018-08-22 19:34:55 UTC
Description of problem:
When issuing "openstack baremetal node bios setting list <NODE ID>" the end user is notified error: 404 not found.  

Version-Release number of selected component (if applicable):
osp14
core_puddle: 2018-08-21.2

How reproducible:
always

Steps to Reproduce:
1. Deploy undercloud
2: source stackrc
3: Perform introspection 
4: Post introspection issue command "openstack baremetal node bios setting list <NODE>"

Actual results:
openstack baremetal node bios setting list fdbcbd64-b4e3-4247-a58b-15aedc82a976
{"code": 404, "description": "", "title": "Not Found"} (HTTP 404)

Expected results:
Bios settings information is displayed for the node that the enduser specified.

Additional info:
none

Actual output:
(undercloud) [stack@undercloud-0 ~]$ openstack baremetal node bios setting list fdbcbd64-b4e3-4247-a58b-15aedc82a976
{"code": 404, "description": "", "title": "Not Found"} (HTTP 404)

Comment 2 Dmitry Tantsur 2018-08-28 08:26:17 UTC
Duplicate, API version negotiation issue.

*** This bug has been marked as a duplicate of bug 1620232 ***