container name resolution not working properly
Bug #1584164 reported by
Scott Croft
This bug report is a duplicate of:
Bug #1513165: Containers registered with MAAS use wrong name.
Edit
Remove
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
New
|
Undecided
|
Unassigned | ||
Bug Description
When lxd containers are created during a bundle deployment, the name of the host container does not match what MAAS thinks the DNS name is for that container. Subsequently, charms like rabbitmq will not deploy correctly as it doesn't know the proper naming of the machine via name resolution.
When deploying the rabbitmq charm this occurs. There is a work around by putting the IP address, container hostname, and MAAS DNS name in /etc/hosts on the container, then restarting rabbitmq. There have been instances of that not resolving the issue, and rabbitmq still doesn't restart properly because of a pid file missing. Touching the pid file, then restarting rabbitmq corrects the issue.
To post a comment you must log in.
This is with Juju 2.0 beta8, MAAS 2.0 beta5 and Xenial