Cloud-init is the one performing the resize and MAAS images are based
off the Ubuntu cloud images, it is more an issue with cloud-init and the
cloud images than MAAS.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1835008
Title:
** Changed in: maas
Status: In Progress => Invalid
** Changed in: maas
Assignee: LaMont Jones (lamont) => (unassigned)
** Changed in: maas
Milestone: 2.1.3 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => High
** Changed in: maas
Milestone: None => 2.2.1
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
When deploying Ubuntu Core with MAAS I am seeing this error in /var/log
/cloud-init.log:
2017-04-26 18:11:45,172 - cc_apt_configure.py[DEBUG]: Nothing to do: No apt
config and running on snappy
2017-04-26 18:11:45,172 - handlers.py[DEBUG]: finish:
Public bug reported:
example config:
'reporting': {
'maas': {
'type': 'webhook',
'endpoint': absolute_reverse(
'metadata-status', args=[node.system_id],
base_url=base_url),
'consumer_key':
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Changed in: maas/1.9
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1574113
Public bug reported:
MAAS uses the power_condition feature to prevent poweroff when enlisting
and commissioning with Ubuntu. This works on Xenial but to keep the code
path the same and make trusty perform as expected this feature needs to
be SRU'd into trusty.
** Affects: cloud-init
This is an issue with cloud-init not MAAS.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
** No longer affects: cloud-init
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas
Importance: High => Critical
** Changed in: maas
Assignee: (unassigned) => Blake Rouse (blake-rouse)
** Changed in: maas
Milestone: None => 2.0.0
--
in: cloud-init
Status: New => Confirmed
** Changed in: maas
Status: In Progress => Triaged
** Changed in: maas
Assignee: Blake Rouse (blake-rouse) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is s
Scott,
What can MAAS do to tell cloud-init that its should use the MAAS
datasource first and always in the enlistment and commissioning
environment. We don't want cloud-init to look at the disk first in the
case of MAAS.
** Also affects: cloud-init
Importance: Undecided
Status: New
**
This seems like a very strange thing that cloud-init should be doing.
Maybe for the first interface that MAAS brings up it makes since for
cloud-init to do, but all the other interfaces are brought up by the
MAAS commissioning scripts. That process is a direct process as well and
does not place
So the configuration that MAAS emits and curtin generates looks correct.
Cloud-init just waits for the signal so I actually think the issue is
with ifupdown. I have targeted that package as well, will leave the
others for now just to track.
** Also affects: ifupdown
Importance: Undecided
This might also be related to curtin and cloud-init. Targeting them as
well.
** Also affects: curtin
Importance: Undecided
Status: New
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Incomplete
** Changed in: maas
This is either because curtin is not installing the cloud configuration
for MAAS, cloud-init is not reading the correct config, or cloud-init
cannot talk to MAAS.
I believe cloud-init changed to python-oauthlib instead of python-oauth
so that might be the issue. Going to target to both curtin and
** No longer affects: maas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1478103
Title:
need support for configuring syslog
Status in cloud-init:
New
Bug description:
in order
17 matches
Mail list logo
