Skip to content
This repository has been archived by the owner on May 7, 2021. It is now read-only.

Fix coreos.cloudinit.basic and coreos.ignition.v2_1.resource.local on Packet #797

Merged
merged 4 commits into from
Jan 29, 2018
Merged

Conversation

bgilbert
Copy link
Contributor

No description provided.

Avoid warnings with Ignition >= 0.21.0.
When a cloud-config is provided, we were running coreos-cloudinit
twice: once with the config passed to coreos-install and once via
oem-cloudinit.service. The two runs were in no particular order and
the latter would set the hostname from Packet metadata, potentially
overriding any hostname set by the former. When passing a cloud-config
to the instance, provide a no-op Ignition config to prevent Ignition
from enabling oem-cloudinit.service via default.ign.
Allow tests to check the cluster platform without type assertions so
we don't need to make every cluster type public.
On Packet, Ignition runs before the machine's private IP has been
configured. On that platform only, contact the TFTP server via its
public IP.
Copy link
Contributor

@arithx arithx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -45,14 +45,15 @@ type BaseCluster struct {

name string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could also switch this from string to platform.Name

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the cluster name, not the platform name. The intent of platform.Name is that it should be treated as an enumerated type.

@bgilbert bgilbert merged commit 30b0dca into coreos:master Jan 29, 2018
@bgilbert bgilbert deleted the packet branch January 29, 2018 20:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants