nextcloud / nextcloud/server

[Bug]: automatic triggered app updates with errors can lead to an unexpected behave (Maint.Window/no login possible anymore)

Open
#55,297 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 30-feedback bug
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

see app bug rreport ==>

https://github.com/julien-nc/cospend-nc/issues/367

Steps to reproduce
  1. automatic trigger update through " occ app:update $app"
  2. if such an app gets error(s), the app sometime do not set the cloud maintenance to "OFF"
  3. an upgrade app window can/will appear - available for any user in the cloud !
  4. Any user can click upgrade this app, which should only be allowd through the Admin - not a normal user
  5. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.