Bug 1405391 - cloud-init of Fedora Base Cloud Image 25 fails to reach servers
cloud-init of Fedora Base Cloud Image 25 fails to reach servers
Product: Fedora
Classification: Fedora
Component: cloud-init (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Garrett Holmstrom
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-12-16 06:25 EST by Victor Stinner
Modified: 2016-12-16 09:41 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-16 09:41:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Victor Stinner 2016-12-16 06:25:48 EST
I downloaded a cloud image of Fedora 25 from:

At boot, cloud-init fails to fetch my config and so I cannot connect to the VM through SSH: the VM doesn't listen to tcp/22!

I'm sorry, I didn't keep logs of the failing cloud-init. I only know that it tried to connect to but failed with a timeout. It tried other IPs like if I recall correctly.

I don't know which login/password I am supposed to use, it's very hard to find any information about Fedora cloud images :-(

See also my complain about the lack of documentation, bug report on the website tracker:

I will now try a cloud image from another "random URL" (not mentionned on the main Fedora website, so should I trust it or not?):

Comment 1 Victor Stinner 2016-12-16 09:41:04 EST
Sorry, it seems like my (virtual) router was broken after a reboot of an OpenStack controller.

I suspected the new Fedora image before last week it worked fine, but in fact the router crashed during the weekend. Moreover, the router still replied to ping, the issue was more subtle than that...

I didn't know that the router can cause issues at cloud-init...

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