This bug is believed to be fixed in cloud-init in 1705804. 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
** Merge proposal unlinked:
https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2 nodes
** Merge proposal unlinked:
https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Merge proposal linked:
https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/333904
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2 nodes
** Merge proposal linked:
https://code.launchpad.net/~yeazelm/cloud-init/+git/cloud-init/+merge/331897
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2 nodes
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334072
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334070
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334071
--
You received this bug notification because you are a member of Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334066
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334065
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334063
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334051
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
Changing manage_etc_hosts seems to do something. If I set it to "yes",
and do "systemctl restart cloud-init", my /etc/hosts gets updated. The
main reason I do this is as an easy way to get the local hostname+fqdn
inside /etc/hosts, for resolution purposes. I could modify /etc/hosts
directly, but I
James,
I do not think that manage_etc_hosts has any implication on cloud-init after an
'update'.
Unless your hostname were to change during that update.
I think the best thing for you to do is
a.) stop doing that
b.) figure out why you needed to do it and file a bug.
Basically we do not expect
Thanks Scott. We set `manage_etc_hosts` to Yes when we configure new
hosts. That requires a restart of cloud-init to pick up the changes, as
far as I know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package cloud-init -
17.1-41-g76243487-0ubuntu1
---
cloud-init (17.1-41-g76243487-0ubuntu1) bionic; urgency=medium
* debian/cloud-init.templates: Fix capitilazation in 'AliYun' name.
(LP: #1728186)
* New upstream snapshot.
- integration test:
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334001
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334003
** Merge proposal linked:
James,
We believe we have a fix for this now in trunk and will be uploading eventually
to Ubuntu 16.04.
Your use case of running 'cloud-init init' after upgrade (without first running
'cloud-init init --local') is something we're confused by.
Is there a reason that you're doing that? Normally
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333999
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333998
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333927
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2
The additional failures in that log starting at 21:10 are me trying to
debug it by adding some print statements in the associated libraries.
Nothing obvious - for whatever reason the fallback_nic is set to None
which causes the error.
--
You received this bug notification because you are a
Hi Ryan, all I did was remove entries prior to restarting cloud-init
(the prior entries ended at Nov 15). But I can paste the entire thing
here if it helps.
** Attachment added: "cloud-init.log"
Is is possible for you to paste the entire /var/log/cloud-init.log file?
The attached log only shows one stage of cloud-init boot.
In particular, cloud-init local mode will attempt to bring up a network
interface to talk to Ec2 metadata service to collect network config;
Given the failure path in
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/333923
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2 nodes
I tried running 'cloud-init collect-logs' but the command just hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1 update breaks EC2 nodes
To manage notifications about this
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1732917/+attachment/5010665/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Scott, GMT time zone here so excuse the delay. Yes this is running on
AWS, on t2 instances. I'll try to gather the logs for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
Title:
17.1
James,
Chad and I have been unsuccessful in reproducing this issue.
Could you provide some info?
Running 'cloud-init collect' should get most of the info we want.
Were you actually running this on Amazon AWS (as opposed to another
cloud that immitates the EC2 Metadata service) ?
Thanks,
Scott
** Changed in: cloud-init (Ubuntu)
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/1732917
Title:
17.1 update breaks EC2 nodes
To manage notifications about this bug
James,
Thanks for taking the time to report this.
We'll look at this asap.
could you post the full /var/log/cloud-init.log ?
Thanks.
Scott
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
This only seems to happen when trying to restart cloud-init on a running
node after the update. Maybe some transient state that is incompatible
after the update? After rebooting the node, cloud-init can be restarted
successfully.
--
You received this bug notification because you are a member of
32 matches
Mail list logo
