-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add pkg_upgrade #3
Conversation
bumbed versionnumber
Hey @crpb
yes, that is what the version number is intended for
Well I think the 5 minutes are safe ...
this would mean mixing scopes of roles, I think this is not desirable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 thank you
Hello @crpb |
@zerwes ahh great. nevertheless i will try out some things in a vm with no uplink and such and maybe i can take the script apart and only use the needed features which might make it a bit faster 🙊 |
Uplink down - Cache cleared
Uplink up
Uplink up - same again
Uplink up - started and immediately disconnected the uplink
These 30 seconds are basically this So for now i would assume it should behave. 🤞🏼 |
Thank you for the tests. |
And we probably are disconnected anyway in such cases *jbol* |
get data generated by /usr/local/opnsense/scripts/firmware/check.sh for Rosa-Luxemburgstiftung-Berlin/ansible-opnsense-update/issues/6
Bumbed versionnumber
The 5 minutes to not always trigger the script might be a bit too long for minor upgrades now that i think about it
¯\_(ツ)_/¯
.Or maybe the upgrade-job from ansible-opnsense-update should just delete it for such cases?