** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies
I believe this fix in MAAS to be wrong :/
If we look in /etc/hosts after this fix landed there is no entry for the
node's name
http://paste.ubuntu.com/8600284/
This breaks juju bootstrap:
http://paste.ubuntu.com/8600331/
--
You received this bug notification because you are a member of
Just did another bootstrap and it went without issue. Continuing to
investigate...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration
So it seems that I was actually hitting bug 1383329 - because there is
no entry in /etc/hosts anymore (fine) juju bootstrap is relying on DNS,
which was flaky (as per bug).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
** Changed in: maas
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts:
** Changed in: maas
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts:
** Changed in: maas
Assignee: (unassigned) = Raphaël Badin (rvb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies
** Branch linked: lp:~rvb/maas/fix-etc-hosts-bug-1087183-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts:
** Changed in: maas
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
We (Landscape team) had a meeting to discuss this with the server team
(James Page, Scott Moser). Based on our discussion, there's consensus
that it would be great if MAAS simply adhered to the Debian policy (see
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1087183/comments/7 )
That would
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To manage notifications
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To manage
** Changed in: maas
Milestone: None = 1.7.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To
** Changed in: juju
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts:
Now, is a dhcp lease a permanent address? :) I think it's permanent
enough for this scenario where MAAS is giving it out, as it even
updates the DNS record.
In this case, yes, I think it is permanent. MAAS promises to keep that
address for that node until it is released. DHCP is simply the
** Changed in: maas
Status: Incomplete = Triaged
** Changed in: maas
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS
Pertains to bug 1087183
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To manage notifications
About Scott's (a) point, the debian document says you should have host.domain
in /etc/hosts if the system has a permanent address, and the host.domain line
should be for that address, not 127.0.1.1:
For a system with a permanent IP address, that permanent IP address should be
used here instead
Can someone mark the pyjuju task as won't fix?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To
** Changed in: juju
Importance: Undecided = Low
** Changed in: juju
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS
Some context. The situation is not at all simple. Here are some things to
think about:
a.) debian manual says what you see in /etc/hosts is actually *correct*
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution
Ie, there *should* be an entry for
The commit message on the revno (from 2012-10-03) that added
manage_etc_hosts says:
--
specify 'preserve_sources_list' to cloud-init in install preseed
This moves the cloud-init/local-cloud-config out of the preseed
explicitly
and instead renders it in
I can remove it, but I don't know enough about cloud-init to know what,
if anything, it will break. So if someone can confirm it's ok I'll do
it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: New = Confirmed
** Changed in: juju
Status: New = Confirmed
** Changed in: maas (Ubuntu)
Status: New = Confirmed
** Changed in: maas (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of
I thought this was enabled to resolve an issue of using avahi with
maas/juju?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies
Dave, see this bug about that:
bug 1086307
I suspect these are related.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies
26 matches
Mail list logo