Bug 1430874 - openstack baremetal configure boot is hardcoded to bm-deploy-ramdisk
Summary: openstack baremetal configure boot is hardcoded to bm-deploy-ramdisk
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M2
: 13.0 (Queens)
Assignee: Jiri Tomasek
QA Contact: Arik Chernetsky
URL:
Whiteboard: scale_lab
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-09 18:42 UTC by Sai Sindhur Malleni
Modified: 2019-07-29 15:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-29 15:38:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1671597 0 None None None 2017-03-09 18:45:14 UTC

Description Sai Sindhur Malleni 2017-03-09 18:42:23 UTC 
Description of problem:

Talking to Ben Nemec on doing an openstack baremetal configure boot the ramdisk image name is hardcoded at https://github.com/openstack/python-tripleoclient/blob/f47c62732036f9926733da0a51926d3e2aa72204/tripleoclient/v1/overcloud_deploy.py#L779

I faced an issue when I modified the ramdisk image, renamed it and updated the ramdisk UUID using ironic node-update <node uuid> add driver_info/deploy_ramdisk=UUID/ The change is reflected in ironic node-show yet when trying to deploy TripleO complains of a mismatch between expected ramdisk UUID the UUID set(modified name).


Details Here: https://gist.github.com/smalleni/e45b4298af127c0dd93efcc95c23d38fase number of selected component (if applicable):



Version-Release number of selected component (if applicable):
RHOP 10 Puddle 2017-03-03.1


How reproducible:
100%

Steps to Reproduce:
1. Assign kernel and ramdisk initially
2. Later upload new ramdisk with another name and aupdate the ironic node property
3. Attempt Deploy

Actual results:
Deploy should go through with new ramdisk

Expected results:
Fails

Additional info:
Note You need to log in before you can comment on or make changes to this bug.