Skip to content
This repository was archived by the owner on Feb 5, 2020. It is now read-only.

Conversation

@trawler
Copy link
Contributor

@trawler trawler commented Jan 17, 2018

NTP servers on Container Linux default to CoreOS time servers,
which may not be accessible on private cluster deployments.
Allow users to set a list of primary NTP servers with the CoreOS
servers as the default fallback.

This is rebased onto track-1 branch from @lander2k2 PR: #2652

@coreosbot
Copy link

Can one of the admins verify this patch?

@trawler
Copy link
Contributor Author

trawler commented Jan 17, 2018

ok to test

@trawler
Copy link
Contributor Author

trawler commented Jan 17, 2018

test this please

@trawler
Copy link
Contributor Author

trawler commented Jan 19, 2018

ok to test

@trawler
Copy link
Contributor Author

trawler commented Jan 23, 2018

ok to test

@cpanato
Copy link
Contributor

cpanato commented Jan 23, 2018

retest this please

@trawler trawler requested a review from alexsomesan January 23, 2018 16:11
@cpanato
Copy link
Contributor

cpanato commented Jan 23, 2018

following this PR to react in test failures

@cpanato
Copy link
Contributor

cpanato commented Jan 23, 2018

retest this please, AZURE/GOVCLOUD

Levi Blackstone and others added 3 commits January 23, 2018 19:09
NTP servers on Container Linux default to CoreOS time servers,
which may not be accessible on private cluster deployments.
Allow users to set a list of primary NTP servers with the CoreOS
servers as the default fallback.
@cpanato
Copy link
Contributor

cpanato commented Jan 23, 2018

retest this please. aws/metal. azure and gov are green

@trawler trawler dismissed spangenberg’s stale review January 24, 2018 08:50

count has been removed from template definition, therefore the fix is no longer necessary

@trawler trawler requested a review from squat January 24, 2018 10:47
Copy link
Contributor

@alexsomesan alexsomesan left a comment

Choose a reason for hiding this comment

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

Look ok.

@trawler trawler merged commit a22faa3 into coreos:track-1 Jan 24, 2018
@carlosaya
Copy link

carlosaya commented Jan 25, 2018

has this been tested with vmware at all? I cannot terraform init. Get the following:

[root@ta030621-dev ite13]# ../../tectonic-installer/linux/terraform init ../../platforms/vmware
Downloading modules...
Error getting plugins: module root:
    5 error(s) occurred:

* module 'masters': unknown variable referenced: 'tectonic_ntp_servers'. define it with 'variable' blocks
* module 'ignition_masters': unknown variable referenced: 'tectonic_ntp_servers'. define it with 'variable' blocks
* module 'ignition_workers': unknown variable referenced: 'tectonic_ntp_servers'. define it with 'variable' blocks
* module 'workers': unknown variable referenced: 'tectonic_ntp_servers'. define it with 'variable' blocks
* module 'etcd': unknown variable referenced: 'tectonic_ntp_servers'. define it with 'variable' blocks
    module masters: ign_ntp_dropin_id is not a valid parameter
    module workers: ign_ntp_dropin_id is not a valid parameter
  module workers.root: 1 error(s) occurred:

* resource 'data.ignition_config.node' config: unknown variable referenced: 'ign_ntp_dropin_id'. define it with 'variable' blocksmodule masters.root: 1 error(s) occurred:

* resource 'data.ignition_config.node' config: unknown variable referenced: 'ign_ntp_dropin_id'. define it with 'variable' blocks

@coresolve
Copy link
Contributor

@kalmog can you address the vmware question above?

@trawler
Copy link
Contributor Author

trawler commented Jan 25, 2018

It was indeed tested. Are you sure you have a clean branch?

karena@Karens-MacBook-Pro:~/go/src/github.com/coreos/tectonic-installer/build/kalmog (track-1) [ 10139283 ] $ terraform init ../../platforms/vmware
Initializing modules...
- module.etcd
- module.ignition_masters
- module.masters
- module.ignition_workers
- module.workers
- module.kube_certs
- module.etcd_certs
- module.ingress_certs
- module.identity_certs
- module.bootkube
- module.tectonic
- module.flannel_vxlan
- module.calico
- module.canal

Initializing provider plugins...

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

rerun this command to reinitialize your working directory. If you forget, other

@trawler
Copy link
Contributor Author

trawler commented Jan 25, 2018

@carlosaya Also, seems that you're using an older version of terraform. Please make sure your TF binary is version v0.11.1 and try again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants