Bug 1430874

Summary: openstack baremetal configure boot is hardcoded to bm-deploy-ramdisk
Product: Red Hat OpenStack Reporter: Sai Sindhur Malleni <smalleni>
Component: python-tripleoclientAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED WONTFIX QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: beth.white, hbrock, jslagle, mburns, rhel-osp-director-maint, tvignaud
Target Milestone: Upstream M2Keywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: scale_lab
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-29 15:38:35 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 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: