I can confirm both that this bug exists and that the referenced workaround deals with the issue.
Context: nova-cloud-controller deployment was producing
hook failed: "cloud-compute-relation-changed" for nova-compute:cloud-compute
On the unit machine, the /etc/netplan/99-juju.yaml started as below:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 00:16:3e:9c:a1:5c
addresses:
- 10.246.114.24/21
gateway4: 10.246.112.1
nameservers:
addresses: [10.246.112.3]
Adding a search domain under nameservers, as below:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 00:16:3e:9c:a1:5c
addresses:
- 10.246.114.24/21
gateway4: 10.246.112.1
nameservers:
search: [maas]
addresses: [10.246.112.3]
and then running a netplan apply allowed the deployment to continue as expected.
I can confirm both that this bug exists and that the referenced workaround deals with the issue.
Context: nova-cloud- controller deployment was producing compute- relation- changed" for nova-compute: cloud-compute
hook failed: "cloud-
On the unit machine, the /etc/netplan/ 99-juju. yaml started as below:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 00:16:3e:9c:a1:5c
addresses:
- 10.246.114.24/21
gateway4: 10.246.112.1
nameservers:
addresses: [10.246.112.3]
Adding a search domain under nameservers, as below:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 00:16:3e:9c:a1:5c
addresses:
- 10.246.114.24/21
gateway4: 10.246.112.1
nameservers:
search: [maas]
addresses: [10.246.112.3]
and then running a netplan apply allowed the deployment to continue as expected.