Bug 1468242 - Default DC & Cluster has fixed UUIDs
Default DC & Cluster has fixed UUIDs
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
All Linux
high Severity urgent
: ovirt-4.2.0
: ---
Assigned To: Eli Mesika
Petr Matyáš
: Regression, ZStream
Depends On:
Blocks: 1468968
  Show dependency treegraph
Reported: 2017-07-06 08:47 EDT by Julio Entrena Perez
Modified: 2018-03-19 11:13 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1468968 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3106571 None None None 2017-07-06 09:09 EDT
oVirt gerrit 79171 master MERGED core: different DC/Cluster UUID per installation 2017-07-09 09:10 EDT
oVirt gerrit 79174 ovirt-engine-4.1 MERGED core: different DC/Cluster UUID per installation 2017-07-09 10:36 EDT

  None (edit)
Description Julio Entrena Perez 2017-07-06 08:47:10 EDT
Description of problem:
This seems to be a regression of bug 1026885.

All new deployments of RHV-M seem to assign fixed UUID 00000001-0001-0001-0001-000000000311 to the Default datacenter and fixed UUID 00000002-0002-0002-0002-00000000017a to the Default cluster.

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

How reproducible:

Steps to Reproduce:
1. Deploy a new RHV-M
2. Check the UUID of the Default datacenter

Actual results:
Default DC has UUID 00000001-0001-0001-0001-000000000311.
Default cluster has UUID 00000002-0002-0002-0002-00000000017a.

Expected results:
UUID of the Default datacenter and the Default cluster are different across different RHV-Ms.

Additional info:

# pwd

# grep -r 00000001-0001-0001-0001-000000000311
data/00300_insert_storage_pool.sql:INSERT INTO storage_pool (id, name, description, storage_pool_type, storage_pool_format_type, status, master_domain_version, spm_vds_id, compatibility_version, _create_date, _update_date, quota_enforcement_type, free_text_comment, is_local) VALUES ('00000001-0001-0001-0001-000000000311', 'Default', 'The default Data Center', 1, NULL, 0, 0, NULL, '4.1', '2016-07-05 12:03:14.099256+03', NULL, NULL, NULL, NULL);
# grep -r 00000002-0002-0002-0002-00000000017a

data/00400_insert_vds_groups.sql:INSERT INTO vds_groups (vds_group_id, name, description, cpu_name, _create_date, _update_date, storage_pool_id, max_vds_memory_over_commit, compatibility_version, transparent_hugepages, migrate_on_error, virt_service, gluster_service, count_threads_as_cores, emulated_machine, trusted_service, tunnel_migration, cluster_policy_id, cluster_policy_custom_properties, enable_balloon, free_text_comment, detect_emulated_machine, architecture, optimization_type, spice_proxy, ha_reservation, enable_ksm, serial_number_policy, custom_serial_number, optional_reason, required_rng_sources) VALUES ('00000002-0002-0002-0002-00000000017a', 'Default', 'The default server cluster', NULL, '2016-07-05 12:03:14.797477+03', NULL, '00000001-0001-0001-0001-000000000311', 100, '4.1', true, 1, true, false, false, NULL, false, false, 'b4ed2332-a7ac-4d5f-9596-99a439cb2812', NULL, false, NULL, true, 0, 0, NULL, false, true, NULL, NULL, false, 'RANDOM');
Comment 11 Petr Matyáš 2018-01-24 05:45:16 EST
Verified on ovirt-engine-

Note You need to log in before you can comment on or make changes to this bug.