New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to start CoreOS Metadata Agent (SSH Keys). #1306

Closed
h0tbird opened this Issue May 28, 2016 · 2 comments

Comments

Projects
None yet
4 participants
@h0tbird

h0tbird commented May 28, 2016

On my master nodes there is no public-ipv4 and I get this error:

Last login: Sat May 28 22:06:30 2016 from 10.0.0.235
CoreOS alpha (1053.2.0)
Failed Units: 1
  coreos-metadata-sshkeys@core.service
core@master-1 ~ $ systemctl status coreos-metadata-sshkeys@core.service
● coreos-metadata-sshkeys@core.service - CoreOS Metadata Agent (SSH Keys)
   Loaded: loaded (/usr/lib64/systemd/system/coreos-metadata-sshkeys@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2016-05-28 16:11:00 UTC; 6h ago
 Main PID: 799 (code=exited, status=1/FAILURE)

May 28 16:10:54 localhost systemd[1]: Starting CoreOS Metadata Agent (SSH Keys)...
May 28 16:11:00 localhost coreos-metadata[799]: fetching "http://169.254.169.254/2009-04-04/meta-data/public-ipv4": attempt #1
May 28 16:11:00 localhost coreos-metadata[799]: failed to fetch metadata: couldn't parse "" as IP address
May 28 16:11:00 localhost systemd[1]: coreos-metadata-sshkeys@core.service: Main process exited, code=exited, status=1/FAILURE
May 28 16:11:00 localhost systemd[1]: Failed to start CoreOS Metadata Agent (SSH Keys).
May 28 16:11:00 localhost systemd[1]: coreos-metadata-sshkeys@core.service: Unit entered failed state.
May 28 16:11:00 localhost systemd[1]: coreos-metadata-sshkeys@core.service: Failed with result 'exit-code'.
core@master-1 ~ $ coreos-metadata --cmdline --ssh-keys=core
fetching "http://169.254.169.254/2009-04-04/meta-data/public-ipv4": attempt #1
failed to fetch metadata: couldn't parse "" as IP address
@jonboulle

This comment has been minimized.

jonboulle commented Jun 3, 2016

Several other reproductions running in eu-central-1a (just using kube-aws to spin up a cluster)

@mcalhoun

This comment has been minimized.

mcalhoun commented Jun 7, 2016

+1

I also don't have a public IP addresses on my controller or workers and I get the same on both the controller and the workers...

systemctl status coreos-metadata-sshkeys@core.service
● coreos-metadata-sshkeys@core.service - CoreOS Metadata Agent (SSH Keys)
   Loaded: loaded (/usr/lib64/systemd/system/coreos-metadata-sshkeys@.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2016-06-07 13:48:28 UTC; 1min 40s ago
 Main PID: 738 (code=exited, status=1/FAILURE)

Jun 07 13:48:23 localhost systemd[1]: Starting CoreOS Metadata Agent (SSH Keys)...
Jun 07 13:48:28 localhost coreos-metadata[738]: fetching "http://169.254.169.254/2009-04-04/meta-data/public-ipv4": attempt #1
Jun 07 13:48:28 localhost coreos-metadata[738]: failed to fetch metadata: couldn't parse "" as IP address
Jun 07 13:48:28 localhost systemd[1]: coreos-metadata-sshkeys@core.service: Main process exited, code=exited, status=1/FAILURE
Jun 07 13:48:28 localhost systemd[1]: Failed to start CoreOS Metadata Agent (SSH Keys).
Jun 07 13:48:28 localhost systemd[1]: coreos-metadata-sshkeys@core.service: Unit entered failed state.
Jun 07 13:48:28 localhost systemd[1]: coreos-metadata-sshkeys@core.service: Failed with result 'exit-code'.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment