-
Bug
-
Resolution: Done
-
Undefined
-
rhos-18.0 Dev Preview 3
-
None
It's recommended to enable the following hostname validation
edpm_nodes_validation_validate_fqdn: true
in the EDPM Adoption example since this validation is important in the EDPM nova adoption process, if not we encounter a situation as the folling:
following DB contents for nova service records:
oc exec openstack-cell1-galera-0 -c galera -- mysql -rs -uroot -p$PODIFIED_DB_ROOT_PASSWORD -e "select * from nova_cell1.services where services.binary='nova-compute';"
2024-02-26 10:08:23 2024-02-27 18:29:22 NULL 69 overcloud-novacompute-0.localdomain nova-compute compute 1499 0 0 NULL 2024-02-27 18:29:22 0 56 644ddb5f-1bf5-45e0-9327-a332bc0b5214
2024-02-28 08:38:15 2024-02-28 15:23:05 NULL 71 overcloud-novacompute-0 nova-compute compute 981 0 0 NULL 2024-02-28 15:23:05 0 66 b6a4a35d-f591-4761-b1df-6acf830152a0
where looks like the updated record was for overcloud-novacompute-0, mismatching the expected overcloud-novacompute-0.localdomain ?
Failing with:
Error updating resources for node overcloud-novacompute-0.localdomain
- is related to
-
-
- Closed
-
