[Bug 1298921] Re: cloud-init should give up on 404 errors

[Thiago Martins]

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]: unexpected error ['NoneType' object has no attribute 'status_code']
2015-10-10 02:27:48,704 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [29/30s]: unexpected error ['NoneType' object has no attribute 'status_code']
2015-10-10 02:27:49,705 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 30 seconds
2015-10-10 02:27:49,717 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [0/120s]: bad status code [404]
2015-10-10 02:27:50,730 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [1/120s]: bad status code [404]
2015-10-10 02:27:51,740 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [2/120s]: bad status code [404]
2015-10-10 02:27:52,750 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [3/120s]: bad status code [404]
2015-10-10 02:27:53,760 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [4/120s]: bad status code [404]
2015-10-10 02:27:54,772 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [5/120s]: bad status code [404]
2015-10-10 02:27:56,783 - url_helper.py[WARNING]: Calling 'http://192.168.122.1//latest/meta-data/instance-id' failed [7/120s]: bad status code [404]
---

I'm seeing this problem, inside by testing environment, where I do NOT
have any Metadata server...

I tried to reduce the timeout, by creating the following file:

10_ec2_timeouts.cfg:

---
datasource:
  MAAS:
    timeout : 50
    max_wait : 120
  OpenStack:
    timeout : 20
    max_wait : 30
  Ec2:
    timeout : 20
    max_wait : 30
---

But, it didn't worked!

The first Metadaserver "http://169.254.169.254" was reduced but, the
second Metadata server "http://192.168.122.1" still have 120s of
timeout!

How to reduce the timeout for all tries that cloud-init will execute?

Thanks!
Thiago

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1298921

Title:
  cloud-init should give up on 404 errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1298921/+subscriptions