This bug was fixed in the package cloud-init -
18.1-35-ge0f644b7-0ubuntu1
---
cloud-init (18.1-35-ge0f644b7-0ubuntu1) bionic; urgency=medium
* debian/cloud-init.templates: enable IBMCloud datasource.
* New upstream snapshot.
- IBMCloud: Initial IBM Cloud datasource.
- test
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342011
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up o
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=097a2967
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Merge proposal linked:
https://code.launchpad.net/~kgarloff/cloud-init/+git/cloud-init/+merge/341844
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 4
See also issue #1702160
https://bugs.launchpad.net/cloud-init/+bug/1702160
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 404 errors
To manage notificatio
Any news on this? I'm also seeing 404 errors and a 2 minute timeout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 404 errors
To manage notifications abo
Scott,
This is the first time I'm hearing about "cloudsigma", I'm pretty sure
that I'm not running there, since this is a KVM Guest running at my own
Ubuntu physical host, that I installed using Ubuntu ISO.
So, this might be another bug... Or maybe not, because it is not giving
up on 404 errors..
Thiago,
the CloudSigma datasource is the one that is doing the http requests listed
above. That datasource cannot be configured with timeout. It should be a
fairly easy fix to add that.
Note, though that if you're hitting the cloudsigma datasource, you are
likely running on cloudsigma or the
Any news on this guys?
I'm trying to create a QCoW2 image with Cloud Init, using Packer,
everything seems t be okay but, I'm seeing the following problem:
---
2015-10-10 02:27:39,689 - url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [20/30s]:
une
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 404 errors
To manage notifications about
CloudStack was add to default list at revno 217 during the Quantal
cycle. So its been there for a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 404
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/1298921
Title:
> In one way or another, the CloudStack datasource was explicitly enabled.
> You or something explicitly configured this datasource on, and to be run
> before the Ec2 datasource, so generally its functioning > as designed.
Well it wasn't explicitly disabled :-)
> Additionally, its not a 404 that
Juergh,
Thanks for posting the log.
Relevant info from the log:
Mar 31 10:00:05 hlinux [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.2 running
'single' at Mon, 31 Mar 2014 10:00:05 +. Up 3090.59 seconds.
pt.conf.d/90cloud-init-pipelining with apt pipeline depth setting 0
...
Mar 31 10:01:10
It would seem you've mis-configured something if you're hitting this.
Default settings put OpenStack before CloudStack, so it should only do this if
you've somehow not found a openstack datasource.
can you post your whole cloud-init.log ?
--
You received this bug notification because you are a
** Branch linked: lp:~juergh/cloud-init/lp1298921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298921
Title:
cloud-init should give up on 404 errors
To manage notifications about this bug go to:
16 matches
Mail list logo
