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

Bug 2017980

Summary:	[RFE][Ironic] Re-assign instance.host for baremetal instances whose compute host is disabled or deleted (Sharded API access)
Product:	Red Hat OpenStack	Reporter:	Artom Lifshitz <alifshit>
Component:	openstack-nova	Assignee:	Julia Kreger <jkreger>
Status:	CLOSED DEFERRED	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	alifshit, dasmith, eglynn, igallagh, jhakimra, kchamart, sbauza, sgordon, smooney, vromanso
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-11-12 16:15:12 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:	2013329

Description Artom Lifshitz 2021-10-27 20:10:02 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Have Ironic overcloud, with nova-compute running on the controllers.
2. Perform the controller replacement process, with the replacement controller having a different hostname from the original.

Actual results:

'splosions. Instances with instance.host set to the replaced controller become unmanageable, as their instance.host now refers to a nova-compute service that no longer exists.


Expected results:

No 'splosions.


Additional info:

Comment 1 Artom Lifshitz 2021-10-27 20:13:00 UTC

Coming out of DFG:Compute tech call on October 27th [1], filing this BZ to track the existing WIP patch at [2]

[1] https://docs.google.com/document/d/1vw9wJndmU_4U9mha4HhClEG4jAZPEItn4FysHEqhO_o/edit#heading=h.edqw67arx7si
[2] https://review.opendev.org/c/openstack/nova/+/813897

Comment 2 Julia Kreger 2022-11-29 16:57:07 UTC

Update: The upstream nova project has rejected automatic remedy of the the field value with the existing hash ring design. The forward only solution which was agreed upon during the last upstream PTG is to basically utilize a shard key to be added to ironic's API in order to create reliable pairing/matching of nodes. This is presently being worked in two separate spec documents upstream and contributors are already working on code to make this happen.

* https://review.opendev.org/c/openstack/nova-specs/+/862833
* https://review.opendev.org/c/openstack/ironic-specs/+/861803

Comment 3 Julia Kreger 2023-02-27 18:21:42 UTC

The work has merged in the Ironic project upstream. Community contributors are pushing forward the nova side of the equation which is anticipated to merge in the Bobcat cycle upstream.

Given we were not able to negotiate this to be a bugfix, and the agreed upon solution is quite intertwined, I'm going to mark this as a future feature.