usr-share-oem-cloud\x2dconfig.yml.service unit failure - ssh lockout #1588
Comments
I've paused automatic updates until we figure out what is going on. Glad to see that the new service timeout for coreos-cloudinit was useful -_- |
In light of #1562, these are the differences between 1164.1.0 and 1180.0.0: On 1180.0.0 no motd is shown. Differences in files: # /usr/lib/systemd/system/locksmithd.service, 1164.1.0 → 1180.0.0
+ Requires=update-engine.service
+ After=update-engine.service user-config.target system-config.target Then |
The commit mentioned above fixes the issue. When I fixed this the first time, I backported it to the Alpha at the time but forgot to fix it in the master branch. We should have a new image later today. |
Thanks for the speed! |
CoreOS Linux 1185.0.0 is now available with the fix. We'll begin rolling it out shortly. Thanks for your patience. |
Issue Report
Bug
Instance cannot be accessed for 10 minutes (services timeouts)
CoreOS Version
1180.0.0
Environment
What hardware/cloud provider/hypervisor is being used to run CoreOS?
AWS Instances (several sizes)
Expected Behavior
Boot up normally
Actual Behavior
Instances boot but cannot be accessed for 10~ minutes
Reproduction Steps
Other Information
CoreOS alpha (1180.0.0)
Failed Units: 1
system-cloudinit@usr-share-oem-cloud\x2dconfig.yml.service
Similar to #1562 #1559
The text was updated successfully, but these errors were encountered: