Bug 37713
| Summary: | updater.log is not loaded | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Tim Petersen <petersen> |
| Component: | UMC - Software update | Assignee: | Stefan Gohmann <gohmann> |
| Status: | CLOSED DUPLICATE | QA Contact: | Florian Best <best> |
| Severity: | critical | ||
| Priority: | P5 | CC: | best, gohmann, walkenhorst |
| Version: | UCS 4.0 | ||
| Target Milestone: | UCS 4.0-0-errata | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| What kind of report is it?: | --- | What type of bug is this?: | --- |
| Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
| User Pain: | Enterprise Customer affected?: | ||
| School Customer affected?: | ISV affected?: | ||
| Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
| Ticket number: | Bug group (optional): | ||
| Max CVSS v3 score: | |||
*** This bug has been marked as a duplicate of bug 37564 *** yes, duplicate. |
Since errata 66 we introduced a regression that leads to the situation that the updater.log is not loaded and nothing happens. This is critical as the customer: a) doesn't recognize that there is a running update (the update runs, indeed!) b) doesn't get any feedback if it started, when it started and more critical c) when its finished side note: The "back" button is also not usable, there the umc recognizes the update ("not possible because of running update...)