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

Old "bootstrap" pods not get properly cleaned after bootstrap restore #2561

Closed
TeddyAndrieux opened this issue May 19, 2020 · 0 comments · Fixed by #2562
Closed

Old "bootstrap" pods not get properly cleaned after bootstrap restore #2561

TeddyAndrieux opened this issue May 19, 2020 · 0 comments · Fixed by #2562
Labels
complexity:medium Something that requires one or few days to fix kind:bug Something isn't working priority:medium Medium priority issues, should only be postponed if no other option topic:docs Documentation

Comments

@TeddyAndrieux
Copy link
Collaborator

TeddyAndrieux commented May 19, 2020

Component:

'lifecycle', 'bootstrap'

What happened:

After a bootstrap restoration old bootstrap pod still exists (salt-master and repositories, ...) so endpoint still use the old bootstrap IP for these and then restoration do not work properly as use this endpoint to configure the minion.

What was expected:

Old bootstrap pods no longer exists after a restoration

Steps to reproduce

Follow the bootstrap restore procedure

Resolution proposal (optional):

Add documentation to remove old bootstrap node before launching restoration

@TeddyAndrieux TeddyAndrieux added kind:bug Something isn't working complexity:medium Something that requires one or few days to fix priority:medium Medium priority issues, should only be postponed if no other option topic:docs Documentation labels May 19, 2020
TeddyAndrieux added a commit that referenced this issue May 19, 2020
When restoring bootstrap, as we do not support multi-bootstrap right now
we need to remove the old one before performing the restoration, it's a
bit dangerous to remove this automaticaly from the restore script so
just add documentation to do it

Fixes: #2561
bert-e added a commit that referenced this issue May 19, 2020
…nto tmp/octopus/w/2.6/bugfix/GH-2561-clean-bootstrap-pods-in-restore
bert-e added a commit that referenced this issue May 19, 2020
…nto tmp/octopus/w/2.6/bugfix/GH-2561-clean-bootstrap-pods-in-restore
bert-e added a commit that referenced this issue May 20, 2020
…p/octopus/w/2.5/bugfix/GH-2561-clean-bootstrap-pods-in-restore
bert-e added a commit that referenced this issue May 20, 2020
… and 'q/2562/2.4/bugfix/GH-2561-clean-bootstrap-pods-in-restore' into tmp/octopus/q/2.5
bert-e added a commit that referenced this issue May 20, 2020
… and 'q/2562/2.5/bugfix/GH-2561-clean-bootstrap-pods-in-restore' into tmp/octopus/q/2.6
@bert-e bert-e closed this as completed in ab89db6 May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:medium Something that requires one or few days to fix kind:bug Something isn't working priority:medium Medium priority issues, should only be postponed if no other option topic:docs Documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant