Learn more about these different git repos.
Even though autocloud managed to ssh, when I tried to ssh into an instance on our OpenStack, it never allowed a connection. Opening this ticket to dig more into this.
Note: strangely the vagrant libvirt is also failing for me with ssh issues.
http://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20161025.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20161025.0.x86_64.vagrant-libvirt.box
Looks like the instance is shutting itself down:
https://paste.fedoraproject.org/460804/14774076
actually I don't think it shut itself down now. looks like the gssproxy service fails to come up and has to time out before other things can continue during boot:
-bash-4.3# systemctl status gssproxy.service ● gssproxy.service - GSSAPI Proxy Daemon Loaded: loaded (/usr/lib/systemd/system/gssproxy.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Tue 2016-10-25 14:58:00 UTC; 9min ago Process: 1460 ExecStart=/usr/sbin/gssproxy -D (code=killed, signal=TERM) Oct 25 14:56:30 localhost.localdomain systemd[1]: Starting GSSAPI Proxy Daemon... Oct 25 14:58:00 host-172-17-1-6 systemd[1]: gssproxy.service: Start operation timed out. Terminating. Oct 25 14:58:00 host-172-17-1-6 systemd[1]: Failed to start GSSAPI Proxy Daemon. Oct 25 14:58:00 host-172-17-1-6 systemd[1]: gssproxy.service: Unit entered failed state. Oct 25 14:58:00 host-172-17-1-6 systemd[1]: gssproxy.service: Failed with result 'timeout'.
The following bug seems to be the problem.
https://bugzilla.redhat.com/show_bug.cgi?id=1212082#c21
This issue is now resolved. We can set the status as Fixed?
Fixed
@dustymabe changed the status to Closed
Closed
Login to comment on this ticket.