diff options
| author |   Jiri Stransky <jistr@redhat.com> | 2017-04-20 11:25:23 +0200 |
|---|---|---|
| committer | Jiri Stransky <jistr@redhat.com> | 2017-04-21 15:24:55 +0200 |
| commit | 8c171167f6e6d00b2426e5242d4a3227bb42d0e6 (patch) | |
| tree | 26329bf5af299146be3715dafb702bf8fae74b1e /tools/yaml-nic-config-2-script.py | |
| parent | 8eaecb64893ff7ebeaca14eb5172e3320202343b (diff) | |
Don't attempt to configure live migration
When configuring nova containers via puppet, the puppet class chain
includes a class for live migration, which configures live migration
aspects in nova and libvirt.
Some of the libvirt config parts try to notify Service[libvirt], but
that service definition is only included in nova-libvirt service, it's
not included in the control plan nova services. However, our hieradata
is currently global on the node, it's not per-service, which means even
though only nova-compute and nova-libvirt service set
tripleo::profile::base::nova::manage_migration: true
this hiera setting is applied to all containers running puppet, most
notably the ones which configure nova control plane services. As a
result, configuration of nova control plane services failed, and in turn
the whole deployment failed.
This commit disables the libvirt part of live migration config until we
implement some better solution (e.g. hieradata separation between
different puppet containers, or move the libvirt config parts only to
nova-compute manifests in puppet-tripleo).
Change-Id: I0328406607d451e6bdce4d92c441c03648925fa7
Closes-Bug: #1684107
Diffstat (limited to 'tools/yaml-nic-config-2-script.py')
0 files changed, 0 insertions, 0 deletions