Bug 1398388 - cloud-init 0.7.8 doesn't work in GCE
Summary: cloud-init 0.7.8 doesn't work in GCE
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cloud-init
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Garrett Holmstrom
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 16:18 UTC by Peter Schiffer
Modified: 2017-12-12 10:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:21:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter Schiffer 2016-11-24 16:18:00 UTC
Description of problem:
Fedora 25 cloud image doesn't work in GCE - cloud-init is not able to connect to the GCE metadata server. Logs: http://paste.fedoraproject.org/489121/47999081/

Fedora 24 cloud image with cloud-init 0.7.7 works fine.

Version-Release number of selected component (if applicable):
Cloud-init v. 0.7.8

How reproducible:
always

Steps to Reproduce:
1. upload f25 cloud image to gce
2. create instance
3.

Actual results:
cloud-init is not able to connect to the gce metadata servers

Expected results:
it works and cloud-init is able to download public ssh keys

Additional info:

Comment 1 Peter Schiffer 2016-12-02 09:15:00 UTC
Copying the logs here, so they won't vanish:

SeaBIOS (version 1.8.2-20160912_142702-google)
Total RAM Size = 0x000000006cc00000 = 1740 MiB
CPUs found: 1     Max CPUs supported: 1
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=41943040 = 20480 MiB
drive 0x000f4780: PCHS=0/0/0 translation=lba LCHS=1024/255/63 s=41943040
Booting from Hard Disk 0...
[    3.081045] piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
%G%G[    3.376174] cloud-init[586]: Cloud-init v. 0.7.8 running 'init-local' at Thu, 24 Nov 2016 10:59:22 +0000. Up 3.11 seconds.
[    3.928298] cloud-init[859]: Cloud-init v. 0.7.8 running 'init' at Thu, 24 Nov 2016 10:59:22 +0000. Up 3.77 seconds.
[    3.928456] cloud-init[859]: ci-info: +++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
[    3.928596] cloud-init[859]: ci-info: +--------+------+-----------+-----------+-------+-------------------+
[    3.928715] cloud-init[859]: ci-info: | Device |  Up  |  Address  |    Mask   | Scope |     Hw-Address    |
[    3.928829] cloud-init[859]: ci-info: +--------+------+-----------+-----------+-------+-------------------+
[    3.928938] cloud-init[859]: ci-info: |  lo:   | True | 127.0.0.1 | 255.0.0.0 |   .   |         .         |
[    3.929075] cloud-init[859]: ci-info: |  lo:   | True |     .     |     .     |   d   |         .         |
[    3.929191] cloud-init[859]: ci-info: | eth0:  | True |     .     |     .     |   .   | 42:01:0a:f0:00:02 |
[    3.929303] cloud-init[859]: ci-info: | eth0:  | True |     .     |     .     |   d   | 42:01:0a:f0:00:02 |
[    3.929409] cloud-init[859]: ci-info: +--------+------+-----------+-----------+-------+-------------------+
[    3.929519] cloud-init[859]: 2016-11-24 10:59:22,960 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7ff27cc18828>: Failed to establish a new connection: [Errno 101] Network is unreachable',))]
[    4.936471] cloud-init[859]: 2016-11-24 10:59:23,968 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: bad status code [404]
[    5.942534] cloud-init[859]: 2016-11-24 10:59:24,974 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: bad status code [404]
[    6.949472] cloud-init[859]: 2016-11-24 10:59:25,981 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: bad status code [404]
[    7.956459] cloud-init[859]: 2016-11-24 10:59:26,988 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [4/120s]: bad status code [404]
[    8.963219] cloud-init[859]: 2016-11-24 10:59:27,995 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: bad status code [404]
[   10.970025] cloud-init[859]: 2016-11-24 10:59:30,002 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [7/120s]: bad status code [404]
[   12.978346] cloud-init[859]: 2016-11-24 10:59:32,010 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]: bad status code [404]
[   14.986481] cloud-init[859]: 2016-11-24 10:59:34,018 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [11/120s]: bad status code [404]
[   16.994657] cloud-init[859]: 2016-11-24 10:59:36,026 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [13/120s]: bad status code [404]
[   19.001936] cloud-init[859]: 2016-11-24 10:59:38,034 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [15/120s]: bad status code [404]
[   22.010340] cloud-init[859]: 2016-11-24 10:59:41,042 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [18/120s]: bad status code [404]
[   25.018534] cloud-init[859]: 2016-11-24 10:59:44,050 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [21/120s]: bad status code [404]
[   28.026682] cloud-init[859]: 2016-11-24 10:59:47,058 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [24/120s]: bad status code [404]
[   31.035157] cloud-init[859]: 2016-11-24 10:59:50,067 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [27/120s]: bad status code [404]
[   34.043670] cloud-init[859]: 2016-11-24 10:59:53,075 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [30/120s]: bad status code [404]
[   38.052536] cloud-init[859]: 2016-11-24 10:59:57,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [34/120s]: bad status code [404]
[   42.061660] cloud-init[859]: 2016-11-24 11:00:01,093 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [38/120s]: bad status code [404]
[   46.071066] cloud-init[859]: 2016-11-24 11:00:05,103 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [42/120s]: bad status code [404]
[   50.080590] cloud-init[859]: 2016-11-24 11:00:09,112 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [46/120s]: bad status code [404]
[   54.089850] cloud-init[859]: 2016-11-24 11:00:13,121 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: bad status code [404]
[   59.100175] cloud-init[859]: 2016-11-24 11:00:18,132 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [55/120s]: bad status code [404]
[   64.111207] cloud-init[859]: 2016-11-24 11:00:23,143 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [60/120s]: bad status code [404]
[   69.121916] cloud-init[859]: 2016-11-24 11:00:28,153 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [65/120s]: bad status code [404]
[   74.132161] cloud-init[859]: 2016-11-24 11:00:33,164 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [70/120s]: bad status code [404]
[   79.142983] cloud-init[859]: 2016-11-24 11:00:38,175 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [75/120s]: bad status code [404]
[   85.154589] cloud-init[859]: 2016-11-24 11:00:44,186 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [81/120s]: bad status code [404]
[   91.166490] cloud-init[859]: 2016-11-24 11:00:50,198 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [87/120s]: bad status code [404]
[   97.180167] cloud-init[859]: 2016-11-24 11:00:56,212 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [93/120s]: bad status code [404]
[  103.191850] cloud-init[859]: 2016-11-24 11:01:02,223 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [99/120s]: bad status code [404]
[  109.203813] cloud-init[859]: 2016-11-24 11:01:08,235 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [105/120s]: bad status code [404]
[  116.216251] cloud-init[859]: 2016-11-24 11:01:15,248 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [112/120s]: bad status code [404]
[  123.227281] cloud-init[859]: 2016-11-24 11:01:22,259 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7ff27cc2e4a8>: Failed to establish a new connection: [Errno 115] Operation now in progress',))]
[  130.235914] cloud-init[859]: 2016-11-24 11:01:29,267 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 126 seconds
[  180.271712] cloud-init[859]: 2016-11-24 11:02:19,303 - url_helper.py[WARNING]: Calling 'http://10.240.0.1/latest/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='10.240.0.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7ff27cc2b978>, 'Connection to 10.240.0.1 timed out. (connect timeout=50.0)'))]
[  231.325690] cloud-init[859]: 2016-11-24 11:03:10,357 - url_helper.py[WARNING]: Calling 'http://10.240.0.1/latest/meta-data/instance-id' failed [101/120s]: request error [HTTPConnectionPool(host='10.240.0.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7ff27cc18978>, 'Connection to 10.240.0.1 timed out. (connect timeout=50.0)'))]
[  249.346528] cloud-init[859]: 2016-11-24 11:03:28,378 - url_helper.py[WARNING]: Calling 'http://10.240.0.1/latest/meta-data/instance-id' failed [119/120s]: request error [HTTPConnectionPool(host='10.240.0.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7ff27cc18400>, 'Connection to 10.240.0.1 timed out. (connect timeout=17.0)'))]
[  250.349337] cloud-init[859]: 2016-11-24 11:03:29,380 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://10.240.0.1/latest/meta-data/instance-id'] after 120 seconds
         Starting Hostname Service...
[[0;32m  OK  [0m] Started Hostname Service.
[[0;32m  OK  [0m] Started Initial cloud-init job (metadata service crawler).
         Starting OpenSSH server daemon...
[[0;32m  OK  [0m] Reached target Network is Online.
         Starting Permit User Sessions...
[[0;32m  OK  [0m] Reached target Cloud-config availability.
         Starting Apply the settings specified in cloud-config...
[[0;32m  OK  [0m] Started Permit User Sessions.
         Starting Hold until boot process finishes up...
[[0;32m  OK  [0m] Started Command Scheduler.
         Starting Terminate Plymouth Boot Screen...
[  259.505377] cloud-init[1076]: Cloud-init v. 0.7.8 running 'modules:config' at Thu, 24 Nov 2016 11:03:38 +0000. Up 259.38 seconds.
ci-info: no authorized ssh keys fingerprints found for user fedora.
<14>Nov 24 11:03:39 ec2:
<14>Nov 24 11:03:39 ec2: #############################################################
<14>Nov 24 11:03:39 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
<14>Nov 24 11:03:39 ec2: 256 SHA256:UjzyAxcQfhHE7J8qsaMkINRyWxQj/P1G/zbmRpQ2Z4s no comment (ECDSA)
<14>Nov 24 11:03:39 ec2: 256 SHA256:Vxnf9z9cPPKnX3WgzSJu6RCndhxdBeEne6zL785EnRY no comment (ED25519)
<14>Nov 24 11:03:39 ec2: 2048 SHA256:ROHEyj35JW4daEWsvpNZsrO3hNZqpRiACx3Mg7366FM no comment (RSA)
<14>Nov 24 11:03:39 ec2: -----END SSH HOST KEY FINGERPRINTS-----
<14>Nov 24 11:03:39 ec2: #############################################################
-----BEGIN SSH HOST KEY KEYS-----
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBJ+k5ScDxIsYh3ymg+LgUrMfGZiv0lABDdvwvisPGzL3Z73uqQZvyt7RKkxw0l4SfkZOr+X2GQIizKsX+JZZo2Y=
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIObLcEOJC7nN+/iZBwAJ8nuYM2IedIuMcQaUuHrl/adr
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCX/SpeeMormaStows4R5bqzVLiDSH0zK0toxAJ3bnLeLW4tTHGARzPvNFr5dWB53DM/zl8+tEv5B0BYGGTrAA+0sp/YdEuYVz6NpxiZYtjTu7q5xV2F6dyR0/eYZdkuWl1UvLsXl7cVX/EQreUEZSSDfx4IYNeYkLJdlyWXlvPyY9f4Yc45FMxAruHLDhGvIU323LUphasc/p2tx6sdy3ZpalVj1j4NRR2Id+z3WQPgts8vEkzuH3Z8Efb7P8hNDzCi7hkE9EsU3JUWrxETdtS9ovdvbxNC9m+5r+G9iZUTui4uQV4gJmwMTWaXE8UuIXmBO8FSlaAOwwgHzTHCmrd
-----END SSH HOST KEY KEYS-----
[  260.202960] cloud-init[1095]: Cloud-init v. 0.7.8 running 'modules:final' at Thu, 24 Nov 2016 11:03:38 +0000. Up 259.89 seconds.
[  260.217484] cloud-init[1095]: ci-info: no authorized ssh keys fingerprints found for user fedora.
[  260.229453] cloud-init[1095]: Cloud-init v. 0.7.8 finished at Thu, 24 Nov 2016 11:03:39 +0000. Datasource DataSourceNone.  Up 260.19 seconds
[  260.245455] cloud-init[1095]: 2016-11-24 11:03:39,234 - cc_final_message.py[WARNING]: Used fallback datasource
 
 
Fedora 25 (Cloud Edition)
 
Kernel 4.8.6-300.fc25.x86_64 on an x86_64 (ttyS0)
 
gce-agents login:

Comment 2 Fedora End Of Life 2017-11-16 18:58:10 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:21:30 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.