Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Cannot recover from failed bastion instance #187

Open
dippynark opened this issue Apr 20, 2018 · 0 comments · May be fixed by #396
Open

Cannot recover from failed bastion instance #187

dippynark opened this issue Apr 20, 2018 · 0 comments · May be fixed by #396
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@dippynark
Copy link
Contributor

dippynark commented Apr 20, 2018 •
edited

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

What happened: The bastion instance went down (accidentally deleted the public route) and running tarmak clusters apply hangs checking whether the bastion is up.

What you expected to happen: For tarmak clusters apply to bring the bastion back up

How to reproduce it (as minimally and precisely as possible): Create a hub and delete the bastion
@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 20, 2018
@dippynark dippynark linked a pull request Aug 1, 2018 that will close this issue
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WIP: Recover properly when bastion goes down dippynark/tarmak
2 participants
@dippynark @jetstack-bot