Comment 2 for bug 1852057

Revision history for this message
Frank Heimes (fheimes) wrote :

Hello and thanks for opening this bug and sharing the logs via the sosreport.
The cloud-init logs as well as the syslog show several error, like:
"
2019-11-04 09:27:36,346 - url_helper.py[DEBUG]: [0/1] open 'http://xxx.xxx.xxx.xxx/2009-04-04/meta-data/instance-id' with {'allow_redirects': True, 'headers': {'User-Agent': 'Cloud-Init/19.2-36-g059d049c-0ubuntu2~16.04.1'}, 'method': 'GET', 'url': 'http://169.254.169.254/2009-04-04/meta-data/instance-id', 'timeout': 50.0} configuration
2019-11-04 09:28:26,389 - url_helper.py[WARNING]: Calling 'http://xxx.xxx.xxx.xxx/2009-04-04/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='xxx.xxx.xxx.xxx', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x3fffb30ebe10>, 'Connection to xxx.xxx.xxx.xxx timed out. (connect timeout=50.0)'))]
"
and
"
2019-11-04 09:27:36,346 - url_helper.py[DEBUG]: [0/1] open 'http://xxx.xxx.xxx.xxx/2009-04-04/meta-data/instance-id' with {'allow_redirects': True, 'headers': {'User-Agent': 'Cloud-Init/19.2-36-g059d049c-0ubuntu2~16.04.1'}, 'method': 'GET', 'url': 'http://xxx.xxx.xxx.xxx/2009-04-04/meta-data/instance-id', 'timeout': 50.0} configuration
2019-11-04 09:28:26,389 - url_helper.py[WARNING]: Calling 'http://xxx.xxx.xxx.xxx/2009-04-04/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='xxx.xxx.xxx.xxx', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x3fffb30ebe10>, 'Connection to xxx.xxx.xxx.xxx timed out. (connect timeout=50.0)'))]"

This let's me assume that cloud-init does not seem to be able to find the meta data service, or there is a network/connection problem (due to the timeout above).

Please make sure and double check if the connectivity is given.

Btw. is there a particular reason why you are using cloud-init in this case? Since a regular ISO install of 16.04 on P8 via virtual cdrom shall not 'require' the use of cloud.init.