openstack baremetal configure boot is hardcoded to bm-deploy-ramdisk

[Sai Sindhur Malleni]

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/e45b4298af127c0dd93efcc95c23d38f

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE