Non idempotent libvirt host uuid generation for computes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Oleksiy Molchanov | ||
Mitaka |
Won't Fix
|
Medium
|
Oleksiy Molchanov | ||
Newton |
Won't Fix
|
Medium
|
Oleksiy Molchanov |
Bug Description
There is a custom function generate() [0] which would return new uuid each time it has been called.
Note, this doesn't affect the libvirt.conf file, but only the entities being generated in the catalog. But it makes the CMDB and the real conf files inconsistent, see https:/
1. If I delete the libvirtd.conf and run puppet my UUID will be different. 2. Kept the way it is I can never use PuppetDB queries to identify a UUID to host mapping.
This issue with an inconsistent and idempotent catalog is also affects the Noop tests. But there is a simple w/a for Noop tests (currently implemented as a https:/
The complete fix should be submitted upstream as well.
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Dmitry Ilyin (idv1985) → Bogdan Dobrelya (bogdando) |
summary: |
- Non idempotent libvirt host uuid generation for computes for Noop tests - only + Non idempotent libvirt host uuid generation for computes |
description: | updated |
Changed in fuel: | |
assignee: | Bogdan Dobrelya (bogdando) → Oleksiy Molchanov (omolchanov) |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
Changed in fuel: | |
status: | Triaged → Won't Fix |
Probably this uuid must come from the Nailgun backend