clean up nova IDs for newer cloudvirts
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	fgiunchedi
	Jul 2 2026, 11:11 AM

Project Tags

Referenced Files

None

Subscribers

Description

Specifying a nova ID in puppet is not needed since https://gerrit.wikimedia.org/r/c/operations/puppet/+/1005065 and over time we kept adding IDs for cloudvirts, which should not be hardcoded in puppet anymore.

Verify that the IDs added in these reviews match fqdn_uuid:

And remove the ones that match

Related Objects
Search...

Status	Assigned	Task
Open	None	T417393 Carry out controlled network switch down tests in cloud
Open	VRiley-WMF	T424658 Ensure cloudvirt capacity is more evenly spread out among racks
Resolved	fgiunchedi	T429563 Put cloudvirt10[77-80] in service
Open	None	T430933 clean up nova IDs for newer cloudvirts

Event Timeline

fgiunchedi created this task.Jul 2 2026, 11:11 AM

fgiunchedi removed fgiunchedi as the assignee of this task.Jul 8 2026, 7:36 AM

fnegri removed a project: cloud-services-team (FY2025/2026-Q3-Q4).Mon, Jul 13, 3:14 PM

I think I'm behind on something. When you say...

should not be hardcoded in puppet anymore

Are you talking about the profile::openstack::base::nova::compute::id values in hiera, or a different nova ID somewhere else in puppet?

In T430933#12132469, @Andrew wrote:

I think I'm behind on something. When you say...

should not be hardcoded in puppet anymore

Are you talking about the profile::openstack::base::nova::compute::id values in hiera, or a different nova ID somewhere else in puppet?

Yes that's correct, profile::openstack::base::nova::compute::id

ok, I'm caught up now! I hadn't realized that we had reproducible uuids for new hosts, I was still just taking nova's word for it :(

clean up nova IDs for newer cloudvirtsOpen, Needs TriagePublicActions

Description

Related ObjectsSearch...

Event Timeline

clean up nova IDs for newer cloudvirts
Open, Needs TriagePublic
Actions

Related Objects
Search...