© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
... Ceph is the culprit.
Looks like the Ceph stack re-introduced 127.0.1.1 into the hosts file during its lifecycle right under the explicitly commented-out prior entry. No idea how the CLI commands work but the Ansible-run ones dont; but we need a safety check for that hostsfile entry because it can apparently be re-introduced by other things fairly quietly and then cause nondescript failures in the MQ managed here.