Skip to content
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

Fix NTP issue that was causing SES5 deployment to fail #108

Merged
merged 4 commits into from
Feb 17, 2020

Conversation

smithfarm
Copy link
Collaborator

@smithfarm smithfarm commented Feb 17, 2020

With these patches, a functioning NTP server setup is deployed on the admin node before DeepSea starts, and DeepSea is instructed -- via time_init: ntp -- to configure NTPD on all the cluster nodes, pointing at the admin node.

Unfortunately, DeepSea has to be patched for this to work...

Fixes: #107

Signed-off-by: Nathan Cutler <ncutler@suse.com>
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Signed-off-by: Nathan Cutler <ncutler@suse.com>
@smithfarm smithfarm added the bug label Feb 17, 2020
@smithfarm smithfarm changed the title Fix SES5 deployment Fix NTP issue that was causing SES5 deployment to fail Feb 17, 2020
Copy link
Contributor

@ImTheKai ImTheKai left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Contributor

@ricardoasmarques ricardoasmarques left a comment

Choose a reason for hiding this comment

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

Tested locally and it fixes the issue, lgtm.

@smithfarm smithfarm merged commit 9d8139a into master Feb 17, 2020
@smithfarm smithfarm deleted the wip-ses5-fixes branch February 17, 2020 16:39
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit to smithfarm/sesdev that referenced this pull request Apr 10, 2020
Even after SUSE#108 we were seeing
time synchronization issues in the ses5 deployment.

nautilus/ses6 deployments were also suffering from clock skews.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ses5 deployment fails due to NTP issue
3 participants