[Bug]: automatic triggered app updates with errors can lead to an unexpected behave (Maint.Window/no login possible anymore)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
see app bug rreport ==>
https://github.com/julien-nc/cospend-nc/issues/367
Steps to reproduce
- automatic trigger update through " occ app:update $app"
- if such an app gets error(s), the app sometime do not set the cloud maintenance to "OFF"
- an upgrade app window can/will appear - available for any user in the cloud !
- Any user can click upgrade this app, which should only be allowd through the Admin - not a normal user
- After any user clicks upgrade, the upgrade can be successful or not, but the Maintenance page will not switch to: OFF
Expected behavior
In every case, users should NOT BE ABLE TO UPGRADE APPS !
In every case apps should not have the POWER to make users login impossible
(there should be central cloud mechanism in place, which control the proper update operations from app;
if the disturb the cloud operation at all, there should be a repair/control routine)
Nextcloud Server version
30
Operating system
RHEL/CentOS
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
No errors have been found.
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked app issue and reproduce the reported flow using occ app:update $app, including an update that returns errors. Trace how maintenance mode and the app-upgrade window behave afterward; done means failed updates cannot leave maintenance enabled or allow non-admin users to trigger app upgrades.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100