When the set doesn't exist osbuildapi-update-nft.sh give nice errors, and a big comment. #2538
No reviewers
Labels
No labels
freeze-break-request
post-freeze
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/ansible#2538
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nftables"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/259ff02ee55f4d2b8da6324fade961b9
Hum, so it's actually not occasional. It's 100% of the time, we just have a nag-once 1d in there, so it only emails once a day.
This is the buildvm-a64 and buildvm-ppc64le in stg. I'm not sure whats different about them from the rest of the builders.
Any ideas?
Huh, so it's all the non-x86_64 builders? And the firewall looks the same on all the arches?
The patch here won't hurt, but the comment is def. wrong and I doubt it fixes anything.
Feel free to ping me today on matrix, when you have some spare minutes ... I've no idea why arch would matter (but only tested on local x86).
rebased onto
b7c82cbb47
Note that this is now just a cleanup, and comment patch. The real fix for the cron errors is in: https://pagure.io/fedora-infra/ansible/pull-request/2550
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/152a0d8c8bde437ea7dec7cee9e490af
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/a0f795ecf3954ec99c265fd709a0ef2e
rebased onto
b9553f3378
rebased onto
b9553f3378
This only should affect the staging builders (we haven't switched prod to nftables yet). So merging.
Pull-Request has been merged by kevin
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/5e196079e68748e69e36a07526294019