This bug was fixed in the package cloud-init - 0.7.9-267-g922c3c5c-
0ubuntu1
---
cloud-init (0.7.9-267-g922c3c5c-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- Ec2: only attempt to operate at local mode on known platforms.
(LP: #1715128)
- Use /run/cloud-i
Just commenting to myself as it confused me.
The warning above shows:
# A new feature in cloud-init identified possible datasources for #
# this system as: #
# [] #
# However, the datasource used was: Ec2 #
I was confused that ds-identify identified nothing but cloud-init
still ran. This
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/330361
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715128
Title:
Crashes in convert_ec2_metadata_
It appears that Ec2Local Datasource gets searched before OpenStack
(network mode) does and is selected.
EC2Local should not enable without the positive id via UUID; that is
(EC2-Strict-mode IIRC), if we're in a MAYBE mode (where we are searching
all datasources) we can't select a DS if we've not f
[13:38] apw, a... /o\ what cloud-init regression?
[13:38] is there a bug number? do you add bug number when pushing hints?
[13:39] cpaelzer, we are currently undergoing investigations in scaling
stack failing to talk to the metadata sources. and cloud-init was mistakenly
identifying and (u
Per former discussions please evaluate the log provided by Laney and decide if
this is an instance of bug 1715241.
If so depending on your planned release timing would a hot-fix back to the last
working version make any sense?
--
You received this bug notification because you are a member of Ub
Further discussion:
[11:11] cpaelzer, if this is going to take days to fix, can we not revert
the whole of the cloud-init update somehow
[11:11] cpaelzer, given it is cratering testing
[11:11] apw: absolutely
[11:12] apw: I planned to jump into the cloud-init standup today to
dsicuss options
cpaelzer asked for these logs - bos01 broken, lgw01 working.
** Attachment added: "cloud-init-logs-lp1715128.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1715128/+attachment/4945762/+files/cloud-init-logs-lp1715128.tar.xz
--
You received this bug notification because you
Copy from IRC:
[10:03] cpaelzer: it's probably
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1715128
[10:04] Launchpad bug 1715128 in cloud-init (Ubuntu) "Crashes in
convert_ec2_metadata_network_config on ScalingStack bos01 (ppc64el)"
[Undecided,New]
[10:20] I opened bug 171 f
I came here tracking a bug in vagrant-mutate dep8 tests that block qemu
migrating.
This effectively blocks every artful package migration that needs access
through the proxies, therefore setting prio critical - since Artful is not
released yet I'm not setting update-regression.
** Changed in: c
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (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/1715128
Title:
Ok, I found the commit that introduced this code.
https://git.launchpad.net/cloud-
init/commit/?id=3c45330af2a301f2bf219da556844d01cef6778e
Chad, please can you help us out here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
12 matches
Mail list logo
