Bug 53148 - Package based App Upgrade sets new App version after pre-invoke scripts checking the repository fails
Package based App Upgrade sets new App version after pre-invoke scripts check...
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-04-23 14:44 CEST by Christina Scheinig
Modified: 2022-05-12 11:04 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2021041521000332
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2021-04-23 14:44:31 CEST
Updating to the ucs@school version 4.4.v9 the customer experienced just this following little error message in a debugging session, because the new diagnostic script was missing, otherwise it would not have been noticed at all.

In the appcenter.log 

14.04.21 21:13:30.072  MODULE      ( PROCESS ) : Paketlisten werden gelesen...
14.04.21 21:13:30.075  MODULE      ( PROCESS ) : E: Problem executing scripts APT::Update::Pre-Invoke 'grep -Fqs '# An error occurred during the repository check.' /etc/apt/sources.list.d/15_ucs-online-version.list && ucr commit /etc/apt/sources.list.d/15_ucs-online-version.list ; ! grep -F '# An error occurred during the repository check.' /etc/apt/sources.list.d/15_ucs-online-version.list'
14.04.21 21:13:30.075  MODULE      ( PROCESS ) : E: Sub-process returned an error code

In the /var/log/apt/history.log were no package upgrade scheduled.

In the session, it was possible to upgrade the newer packages version.

The expected behaviour would be, to get noticed, that something went wrong and the upgrade was not successful. The new version was set, before the package upgrade took place.