Univention Bugzilla – Full Text Bug Listing |
Summary: | Docker-Apps may fail to upgrade behind a proxy | ||
---|---|---|---|
Product: | UCS | Reporter: | Nico Stöckigt <stoeckigt> |
Component: | UMC - App-Center | Assignee: | Felix Botner <botner> |
Status: | CLOSED FIXED | QA Contact: | Dirk Wiesenthal <wiesenthal> |
Severity: | normal | ||
Priority: | P5 | CC: | botner, brodersen, wiesenthal |
Version: | UCS 4.3 | ||
Target Milestone: | UCS 4.3-2-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 2: Improvement: Would be a product improvement |
Who will be affected by this bug?: | 2: Will only affect a few installed domains | How will those affected feel about the bug?: | 2: A Pain – users won’t like this once they notice it |
User Pain: | 0.046 | Enterprise Customer affected?: | Yes |
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | 2018073021000368 | Bug group (optional): | |
Max CVSS v3 score: |
Description
Nico Stöckigt
2018-08-02 11:47:24 CEST
univention-appcenter: 3dd9fbe0d70f779e4c0d9aae89142e3d87b6ba09 yaml: f79af25cd8a4a21c507e4808f12b8fa3742ba5ed Proxy settings are now updated in the container before the upgrade. Additionally, pull now raises an Abort exception. I had the problem that after setting up my proxy i forgot to restart the docker daemon. Then i wanted to upgrade a docker app. The pull failed (because the docker daemon couldn't connect to the registry) but the upgrade did continue up to the step of starting the container. This failed and then the whole abort, remove, reinstall broke my app. So better stop after the pull fails Works for me during upgrade (upgrade stops but does not touch the old app) and install (removes the app) Ok, works during App updates. This bug affects those apps that need an internet connection. (Mainly appbox) Note that this is not a "live adaption" of changed proxy settings on the host. The new proxy settings are applied when an App update is installed, which may or may not be possible at this time. While no App update is available (or installed), the container does not have a working internet connection and thus cannot install errata updates. I still think this is okay for now. At least works better. |