Failed to start CoreOS Metadata Agent (SSH Keys). #1306
Comments
Several other reproductions running in |
+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...
|
Hello all,
OS version:
Any Ideas? |
@sampcoug What cloud platform are you running on? What does |
@bgilbert I am on Google Cloud Platform.
|
@sampcoug thanks for the followup. Can you please post what's the content at the URL of the last/successful fetch? It looks like one its lines is not in the format we expect for ssh keys. |
@lucab I apologize, appears that the some portions were cut off. Hope below helps.
|
@sampcoug, @lucab was asking about the contents of http://metadata.google.internal/computeMetadata/v1/project/attributes/sshKeys for that instance. It appears that one of the keys is formatted incorrectly. |
@bgilbert, sorry. hope this helps?
|
@sampcoug there is a mandatory header to be attached to requests:
|
@lucab, it is returning the SSH key that I have added to the Metadata section in GCE gui. Are you referring that there is something wrong with the SSH key? |
@sampcoug Each line should be formatted as |
Indeed, it should follow the format described by @bgilbert above and specified at https://cloud.google.com/compute/docs/storing-retrieving-metadata#default. |
On my master nodes there is no
public-ipv4
and I get this error:The text was updated successfully, but these errors were encountered: