*** This bug is a duplicate of bug 1382190 ***
https://bugs.launchpad.net/bugs/1382190
IMHO, the current MAAS DNS management is bad. It uses static zones and when you
try modifying the templates, the whole zone-writing/reloading mechanism blows
up, celery tasks for freeze/thaw won't do. Dyna
*** This bug is a duplicate of bug 1382190 ***
https://bugs.launchpad.net/bugs/1382190
** This bug has been marked a duplicate of bug 1382190
LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: maas
Milestone: None => next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc instances deployed via MAAS don't have resolvable hostnames
To manage notificat
To clarify: comment #12 was for clustered rabbitmq (as already reported
above), FYI trying to force the charm to use plain IPs instead of hostnames
(recall that other units need to be able to refer to each other as
e.g.. rabbit@$OTHER_HOST) fails with e.g.:
2014-10-16 18:51:13 INFO config-changed
FYI this is voiding current trusty/rabbitmq charm from deploying on MaaS
1.7beta + LXC, 1.5 had at least PTR resolution for every dhcp'd IP as e.g:
IN PTR 10-1-57-22.maas. , while 1.7beta has none afaicT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
FYI nova services output also refers to hostnames (which are then
unresolvable):
Here below, nova-compute services are deployed to the metal-s, others
to LXCs on them:
$ nova service-list
++--+--+-+---+-...
| Binary | Host
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc instances deployed via MAAS don't have resolvable hostnames
To manage notifications about th
This issue makes several HA services to fail (or split-brain):
* rabbitmq-server:
Followup from above, this MP[0] forces rabbit nodename to be the resolvable
hostname for private-address[0], and fixes it clustering.
* mongodb:
No way: mongod uses gethostname() at rs.initiate() to initialize clust
** Tags added: dns
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc instances deployed via MAAS don't have resolvable hostnames
To manage notifications about this bug go to:
ht
We also see this behaviour on LXC containers deployed to MAASified
machines where MAAS does *not* manage DHCP/DNS.
We are trying to smoosh OpenStack infra into LXC units on MAASified
machines for HA.
It is most visible with rabbitmq-server, which bails out on NXdomain for
the unit.
It's also rep
** Changed in: maas (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: maas (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju
This is a related problem https://bugs.launchpad.net/bugs/1250435
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc instances deployed via MAAS don't have resolvable hostnames
T
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc instances deployed via MAAS don't have resolvable hostnames
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju
OK I guess we need to add some API call for CNAME inclusion. Still,
seems a bit weird that MAAS itself should be doing it. Hmmm, maybe we
need a brainstorming session.
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Wishlist
--
You received thi
One use case for this is rabbitmq-server; to make active/active rabbitmq
clusters, rabbit nodes need to be joined just using the hostname; if
this does not resolve, clustering fails.
I think this is actually an erlang issue (which behaves oddly when DNS
is not configured properly).
** Changed in:
Juju uses the machine name as the hostname
so you get something like
juju-precise-mysql-0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc instances deployed via MAAS don't
Wait - so you want MAAS to add DNS entries for hosts it's not managing?
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
juju lxc in
What hostname does juju give the LXCs? FWIW all of the DHCP addresses
that MAAS assigns do have a default DNS entry of N-N-N-N.domain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947
Title:
j
19 matches
Mail list logo
