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

Github CI action, fix pot destroy leftovers #236

Merged
merged 1 commit into from Oct 23, 2022

Conversation

grembo
Copy link
Collaborator

@grembo grembo commented Oct 21, 2022

Slightly improve CI script (e.g., detect IPv6 missing), add github CI action (triggers on push to the branch and should be able to be run manually once it lands in master). As running it is quite expensive, I wouldn't run it automatically at the moment. The idea is to have the CI workflow in github actions, so we can run it before cutting a release.

Pot destroy left directories behind on destroy (side-effect of the previous partially reverted commit, but could also happen in other ways, hence the explicit fix by removing those directores).

Slightly improve CI script (e.g., detect IPv6 missing), add github
CI action (triggers on push to the branch and should be able to
be run manually once it lands in master).

Pot destroy left directories behind on destroy (side-effect of
the previous partially reverted commit, but could also happen
in other ways, hence the explicit fix).
@grembo
Copy link
Collaborator Author

grembo commented Oct 21, 2022

See here for an example run (on push for the special branch), I hope you can see it:

https://github.com/grembo/pot/actions/runs/3295824125/jobs/5434775436

@@ -61,6 +61,10 @@ _pot_zfs_destroy()
_error "zfs failed to destroy the dataset $_jdset"
return 1 # false
fi
if [ -d "${POT_FS_ROOT}/jails/$_pname" ]; then
Copy link
Collaborator

Choose a reason for hiding this comment

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

While probably it's a good idea to have those kind of robust clean-up features, we should aim to not depend on them for "normal" use cases.
I started a patch to fix the cases we introduced that broke destroy, I'll submit it later.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, basically rolling back the commit that introduced the mkdir wrapper, that was a good example of failing in a team 😁

I'll start working on the real solution to the permission issue like discussed soonish (essentially chmod 750 /opt/pot; chown root:pot /opt/pot)

@grembo grembo merged commit 4dd28f9 into bsdpot:master Oct 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants