| Summary: | [UI] 2 dashboard icons after upgrade | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Liran Rotenberg <lrotenbe> | ||||
| Component: | ovirt-engine-ui-extensions | Assignee: | Greg Sheremeta <gshereme> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukas Svaty <lsvaty> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.3.0 | CC: | gshereme, hunter86_bg, info, mgoldboi, pkubica, ratamir, Rhev-m-bugs, sbonazzo, serg | ||||
| Target Milestone: | ovirt-4.3.0 | Keywords: | Regression | ||||
| Target Release: | 4.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-02-05 13:10:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Liran Rotenberg
2018-12-25 15:04:51 UTC
This should have been removed on upgrade. ovirt-engine-dashboard.noarch 1.2.4-1.el7ev installed @Sandro, any idea? [This was also previously reported as 1616318 – 2 dashboard icons exist https://bugzilla.redhat.com/show_bug.cgi?id=1616318 but not sure if this is something new, i.e. a genuine upgrade issue vs. a developer environment issue] not blocking oVirt 4.3.0 workaround is simply uninstall ovirt-engine-dashboard (In reply to Greg Sheremeta from comment #3) > This should have been removed on upgrade. > > ovirt-engine-dashboard.noarch > 1.2.4-1.el7ev installed > > @Sandro, any idea? Looking at the code: Obsoletes: ovirt-engine-dashboard <= 1.2 Provides: ovirt-engine-dashboard while here 1.2.4 is installed and 1.2.4 is > than 1.2 I would change above with: Obsoletes: ovirt-engine-dashboard < 1.3 Provides: ovirt-engine-dashboard = 1.3 ovirt-engine-dashboard 1.3 doesn't exist -- confirming that that's ok? (Do we even need the Provides?) (In reply to Greg Sheremeta from comment #9) > ovirt-engine-dashboard 1.3 doesn't exist -- confirming that that's ok? > (Do we even need the Provides?) We need the provides if the package provide same functionalities, if not it's ok to just use obsoletes. In this case: Obsoletes: ovirt-engine-dashboard should be enough. same behavior when upgrading from 4.2.8 to 4.3.0 GA on our test environment. removing ovirt-engine-dashboard helps. (In reply to Sergey from comment #11) > same behavior when upgrading from 4.2.8 to 4.3.0 GA on our test environment. > removing ovirt-engine-dashboard helps. Indeed, simply removing ovirt-engine-dashboard is the workaround until I fix the spec. Haven't noticed, that it was delayed until 4.3.1 maybe this should be mentioned in "Known Issues" section of Release Notes? Looks like every update before 4.3.1 announcement will hit this bug. (In reply to Sergey from comment #13) > Haven't noticed, that it was delayed until 4.3.1 > maybe this should be mentioned in "Known Issues" section of Release Notes? > Looks like every update before 4.3.1 announcement will hit this bug. It'll be async'd out, probably today. Thanks! *** Bug 1672254 has been marked as a duplicate of this bug. *** *** Bug 1665430 has been marked as a duplicate of this bug. *** ovirt-engine-ui-extensions 1.0.3 is now in the repo. New upgrades of standalone engine are fixed. Hosted engine upgrades require a yum update. (In reply to Greg Sheremeta from comment #17) > ovirt-engine-ui-extensions 1.0.3 is now in the repo. New upgrades of > standalone engine are fixed. Hosted engine upgrades require a yum update. Actually, that was incorrect. New standalone engine upgrades will catch the fix. New hosted engine upgrades will catch the fix. If you updated to either to 4.3.0 on day 1, 'yum update' and 'engine-setup' to get the fix. *** Bug 1677266 has been marked as a duplicate of this bug. *** |