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.

Sign up for GitHub

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

Jump to bottom

Zarf v0.14.0 gets into a broken state after zarf destroy #347

Closed
RothAndrew opened this issue Feb 23, 2022 · 1 comment
Closed

Zarf v0.14.0 gets into a broken state after zarf destroy #347

RothAndrew opened this issue Feb 23, 2022 · 1 comment
Labels
bug 🐞 Something isn't working wontfix This will not be worked on

Comments

@RothAndrew
Copy link
Contributor

RothAndrew commented Feb 23, 2022 •
edited
Loading

Sometimes, usually after a zarf destroy, the .zarf-state.yaml and $HOME/.git-credentials files will get into a bad state, where the IP address / hostname is not present in the configuration, and zarf package deploy fails because it doesn't know where to push the docker images. This issue is resolved in v0.15.0 and can be mitigated on v0.14.0 by deleting .zarf-state.yaml and $HOME/.git-credentials (assuming there isn't other non-zarf stuff in it) after running zarf destroy.
@RothAndrew RothAndrew added the bug 🐞 Something isn't working label Feb 23, 2022
@RothAndrew RothAndrew moved this to New Requests in Zarf Project Board Feb 23, 2022
@RothAndrew RothAndrew added the wontfix This will not be worked on label Feb 23, 2022
@RothAndrew
Copy link
Contributor Author

Since Zarf is still changing quite rapidly while it is in beta, signified by its version being v0.x, we aren't ready to start doing support branches to patch previously released versions. Users experiencing this issue are encouraged to upgrade to a later version of Zarf that isn't affected.

Repository owner moved this from New Requests to Done in Zarf Project Board Feb 23, 2022
@RothAndrew RothAndrew changed the title Zarf v0.14.0 gets into a weird state after zarf destroy Zarf v0.14.0 gets into a broken state after zarf destroy Feb 23, 2022
@RothAndrew RothAndrew mentioned this issue Feb 23, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐞 Something isn't working wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RothAndrew