If someone has been using an OS with unattended upgrades enabled and has been perfectly happy with it why throw warnings? TBF as long as the system is kept up to date, I’m not worried about who or what updates it, to that point I have webmin automatically add all updates, which I have had switched on for maybe 10 years and to date I can’t remember a failure from it. So in my instance I never need to look at this section of webmin
Because the GUI gives you an option to do something else, so clicking that button does nothing even though you expect it to.
but i do use VMs from all sorts of providers that claim to be vanila images of various OS.
I am already well enough informed to avoid those who claim to pre-install Virtualmin. so an additional warning of unattended-upgrades would help. ignoring such a warning is entirely down to me
I didnt received any updates.
Please don’t hijack threads and change the subject. Open a new topic if you have questions about repositories or updates or whatever it is you’re having a problem with. And, provide the information we would need to help.
Thanks for pointing this out! The issue is fixed.
See the GitHub ticket below for details:
1 Like
This is not fixed for me.
My OS is still installing updates when it is configured in Webmin/Virtualmin not too (I say this as if I had applied the patch), a message on one of the options changes nothing.
This is being re-looked at.
Well, okay, yeah! That’s expected because unattended-upgrades or dnf-automatic can handle the job on their own.
We could add a checkbox in the “Software Package Updates” module to disable all programs that install updates.
@Jamie, do you think this might be a better solution?
I did post a suggestion to the GitHub. the checkbox would be better in the configuration not on the front.
Why in the module config, though, and not on the page?
this setting does not fit into the functionality of the page, it is a configuration option.
I think it’s best to keep it simple and just show a notice for Webmin users, and for Virtualmin users, we’ll just disable automatic updates during Virtualmin install time.
And, nothing stops you from uninstalling the unattended-upgrades or dnf-automatic package and being done with it.
Except I don’t know what I am doing, and I will not be the only one.
my solution is best, a message (like the reboot warning message) with a disable and ignore button. Which just trigger the right code/operation and then in config an option to change the check/ignore flag if the user decided ignoring this was a bad thing.
My solution give consistence, does not automatically alter the OS and fits all circumstances. Notifies the user.
The message should only be display on the scheduler tab, not globally.
Better, instead, in the UI, we will show a clearer conditional message if background daemons are performing upgrades outside Webmin, and provide a checkbox to disable it.
1 Like
That’s too broad. unattended-upgrades isn’t simply a matter of turning it on or off; it offers much finer-grained control.
I just want the GUI to show me the state of what is happening. If I click the button, that’s what my choice is. No more complicated than that.
1 Like
So if unattended upgrades are enabled, you want to see a message saying so and have an easy option to disable it, right?
3 Likes
Please don’t just try to squash it with one general switch. Either you create a switch for every upgrade option (incl. ESM!):
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}:${distro_codename}-updates";
//"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
…or you leave it be and only offer to disable it during an initial Virtualmin deployment.
well just let your OS provider handle it as it sees fit. Are you not just ‘nit picking’ as you quite rightly say in the quote .. I would guess most users would not worry about it and to be fair this is the first thread that has bought up this non issue in the last decade or more that I can remember
Well, we should keep it simple. We’ll just suggest to stop the unattended-upgrades or dnf-automatic daemon. I don’t think we need to micromanage the config.