86de3c3501
With recent version of libvirt, nova-compute don't come up correct when tls-everywhere (use_tls_for_live_migration) is set. The enable_live_migration_tunnelled condition did not consider tls-livemigration and got disabled. Nova-compute fails to start with: 2021-05-12 12:49:09.278 7 ERROR oslo_service.service nova.exception.Invalid: Setting both 'live_migration_tunnelled' and 'live_migration_with_native_tls' at the same time is invalid. If you have the relevant libvirt and QEMU versions, and TLS configured in your environment, pick 'live_migration_with_native_tls'._ This change enhance the enable_live_migration_tunnelled condition to not configure tunnelled mode when use_tls_for_live_migration is true. Conflicts: - deployment/nova/nova-compute-container-puppet.yaml NOTE(dvd): - |
||
---|---|---|
.. | ||
nova-api-container-puppet.yaml | ||
nova-apidb-client-puppet.yaml | ||
nova-az-config.yaml | ||
nova-base-puppet.yaml | ||
nova-compute-common-container-puppet.yaml | ||
nova-compute-container-puppet.yaml | ||
nova-conductor-container-puppet.yaml | ||
nova-db-client-puppet.yaml | ||
nova-ironic-container-puppet.yaml | ||
nova-libvirt-container-puppet.yaml | ||
nova-libvirt-guests-container-puppet.yaml | ||
nova-manager-container-puppet.yaml | ||
nova-metadata-container-puppet.yaml | ||
nova-migration-target-container-puppet.yaml | ||
nova-scheduler-container-puppet.yaml | ||
nova-vnc-proxy-container-puppet.yaml |