Cloud-init now supports event reporting, so closing this item. If you
believe this to be not completed please open a new bug against cloud-
init on Github with more details.
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because
This bug has not seen any activity in the last 6 months, so it is being
automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team
** Changed in: maas
Status: Incomplete => Expired
--
You received this bug notification because you are a member
** Changed in: cloud-init (Ubuntu Zesty)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for
Cloud-init will likely need a couple of fixes to support this feature:
- A new reporting handler which will POST collected cloud-init logs
on cloud-init failure/exception conditions
- Add #cloud-config support for
reporting:
opaquekey_maas_errorlogs:
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: cloud-init
Importance: Wishlist => Medium
** Changed in: cloud-init
Assignee: Chad Smith (chad.smith) => (unassign
** Changed in: cloud-init
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: maas
Milestone: 2.5.x => 2.6.0
** No longer affects: maas/2.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for
Can someone please reopen this for cloud-init, since the fix wasn't the
right one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for
** Changed in: maas
Milestone: 2.5.0 => 2.5.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To manage notif
** Changed in: maas
Milestone: 2.5.0beta2 => 2.5.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To manage
** Changed in: maas
Milestone: 2.5.0beta1 => 2.5.0beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To ma
** Changed in: maas
Milestone: 2.5.0alpha2 => 2.5.0beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To m
** Changed in: maas
Milestone: 2.5.x => 2.5.0alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To manage
** Changed in: maas
Importance: Wishlist => High
** Changed in: maas/2.4
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to
For the wider audience, this issue has *not* really been fixed in cloud-
init for MAAS to be able to use it to collect logs. SO cloud-init needs
to address this before MAAS can start collecting logs.
** Changed in: maas
Status: Triaged => Incomplete
** Changed in: maas/2.4
Status: T
Marking as incomplete for MAAS for the lack of a better status until
cloud-init supports sending logs back, so that it is not confused with
the cloud-init status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Also affects: maas/2.4
Importance: Undecided
Status: New
** Changed in: maas/2.4
Milestone: None => 2.4.x
** Changed in: maas/2.4
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: maas
Milestone: 2.3.x => 2.5.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To manage notif
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To manage notifications
This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1~16.04.1
---
cloud-init (17.1-27-geb292c18-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
instances. (LP: #
This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1~17.04.1
---
cloud-init (17.1-27-geb292c18-0ubuntu1~17.04.1) zesty-proposed; urgency=medium
* New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
instances. (LP: #1
=== abridged SRU Verification output ===
for release in xenial zesty;
> do
> ref=$release-proposed;
> name=test-$release;
> lxc-proposed-snapshot --proposed --publish $release $ref;
> lxc launch $ref $name;
> sleep 10;
> lxc exec $name ubuntu-bug cloud-init
> done
Creati
Hello Jason, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/17.1-27-geb292c18-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this n
Hello Jason, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/17.1-27-geb292c18-0ubuntu1~17.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this ne
=== cloud-init SRU Verification output ===
--- xenial
root@test-xenial:~# ubuntu-bug cloud-init
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Your device details (lshw) may b
This bug is missing the SRU template but I believe this is just adding
an apport hook so I'll let it in without one. However, we should have
one before accepting the package into -updates.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (
26 matches
Mail list logo
