Detailed bug description:
4 Nova-related Tempest tests failed on configuration with detached components. It looks like the root of the issue in the configuration of services with detached components (when database and keystone service locates on separate hosts)
Bug was found on MOS 8.0, separate components don't work with MOS 9.0 for now (we need to update plugins).
Steps To Reproduce:
1. Deploy OpenStack cluster with the following configuration: Neutron VLANs, enable DVR, enable SAHARA, enable MURANO, enable IRONIC, enable MONGO, HA, Cinder LVM, Swift. Add nodes with separate database and separate Keystone service.
2. Run full Tempest tests suite.
Expected Results:
All Tempest tests passed
Actual Results:
3-Nova related tests failed:
test_aggregate_add_host_create_server_with_az
test_show_host_detail
test_can_create_server_with_max_number_personality_files
Reproducibility:
100 %
Workaround:
We don't know the workaround yet.
Impact:
All users who will install separate components with MOS 8.0 are affected.
We will target the issue on MOs 9.0 as well to not miss the fix for 9.0
Detailed bug description:
4 Nova-related Tempest tests failed on configuration with detached components. It looks like the root of the issue in the configuration of services with detached components (when database and keystone service locates on separate hosts)
Bug was found on MOS 8.0, separate components don't work with MOS 9.0 for now (we need to update plugins).
Steps To Reproduce:
1. Deploy OpenStack cluster with the following configuration: Neutron VLANs, enable DVR, enable SAHARA, enable MURANO, enable IRONIC, enable MONGO, HA, Cinder LVM, Swift. Add nodes with separate database and separate Keystone service.
2. Run full Tempest tests suite.
Expected Results:
All Tempest tests passed
Actual Results: add_host_ create_ server_ with_az host_detail create_ server_ with_max_ number_ personality_ files
3-Nova related tests failed:
test_aggregate_
test_show_
test_can_
Reproducibility:
100 %
Workaround:
We don't know the workaround yet.
Impact:
All users who will install separate components with MOS 8.0 are affected.
We will target the issue on MOs 9.0 as well to not miss the fix for 9.0