This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-
0ubuntu1~16.04.1
---
cloud-init (0.7.9-90-g61eb03fe-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* debian/cloud-init.templates: add Bigstep to list of sources. (LP: #1676460)
* New upstream snapshot.
- Ope
This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-
0ubuntu1~16.10.1
---
cloud-init (0.7.9-90-g61eb03fe-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/cloud-init.templates: add Bigstep to list of sources. (LP: #1676460)
* New upstream snapshot.
- OpenStack:
For xenial:
With the current cloud-init, where the problem appears:
*** 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 500
500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
# remove generated files
root@15-89:/run/cloud-init# rm cloud.cfg ds-identify.log
# cloud-init confi
It's hard to reproduce the same error condition, as this happened during
the development of a new feature (deploying ubuntu-core via MAAS). The
closest I could get to it after some help from Ryan Harper was to run
ds-identify on a normally deployed MAAS node with the current cloud-init
and the prop
I have verified deployment of nodes with maas 2.2 and upgrading the
installed system to -proposed during the install.
that can be accomplished by adding the following to
/etc/maas/preseeds/curtin_userdata_ubuntu
system_upgrade: {enabled: True}
apt:
sources:
proposed.list:
source: deb
** Tags removed: dsid verification-needed
** Tags added: verification-done-xenial verification-needed-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677710
Title:
ds-identify does not find m
** Tags added: dsid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677710
Title:
ds-identify does not find maas datasource
To manage notifications about this bug go to:
https://bugs.launchpad.net/c
** Description changed:
=== Begin SRU Template ===
[Impact]
- On systems deployed with MAAS xenial and yakkety systems would put a
- warning on the login screen stating that the datasource was not found.
+ On Ubuntu core systems deployed with MAAS xenial and yakkety systems
+ would put a warni
I'm having difficulties in reproducing the problematic case. I added
this to /etc/maas/preseeds/curtin_userdata:
(...)
system_upgrade:
enabled: True
late_commands:
(...)
Deploying yakkety without -proposed, I don't see any error regarding not
finding a datasource, either in the logs, or in the
** Description changed:
=== Begin SRU Template ===
[Impact]
On systems deployed with MAAS xenial and yakkety systems would put a
warning on the login screen stating that the datasource was not found.
-
[Test Case]
The full test case involves
* deploying through MAAS
* enablin
Hello Scott, 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/0.7.9-90
-g61eb03fe-0ubuntu1~16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Hello Scott, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Description changed:
=== Begin SRU Template ===
- [Impact]
- On systems deployed with MAAS:
- * yakkety systems would not find a MAAS datasource
- * xenial systems would show a warning.
-
+ [Impact]
+ On systems deployed with MAAS xenial and yakkety systems would put a
+ warning on the l
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ On systems deployed with MAAS:
+ * yakkety systems would not find a MAAS datasource
+ * xenial systems would show a warning.
+
+ [Test Case]
+ The full test case involves
+ * deploying through MAAS
+ * enabling -proposed (w
** Changed in: cloud-init
Importance: Undecided => High
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Status: New
This bug was fixed in the package cloud-init - 0.7.9-87-gd23543eb-
0ubuntu1
---
cloud-init (0.7.9-87-gd23543eb-0ubuntu1) zesty; urgency=medium
* debian/cloud-init.templates: add Bigstep to list of sources. (LP: #1676460)
* New upstream snapshot.
- net: in netplan renderer dele
** Changed in: cloud-init
Status: New => Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received
18 matches
Mail list logo
