Bug 1598404 - branding: oVirt Node cockpit and oVirt Engine have different coloring
Summary: branding: oVirt Node cockpit and oVirt Engine have different coloring
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-release
Classification: oVirt
Component: ovirt-release-host-node
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.0
: ---
Assignee: Sandro Bonazzola
QA Contact: shiyi lei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-05 10:59 UTC by Sandro Bonazzola
Modified: 2020-05-20 20:02 UTC (History)
8 users (show)

Fixed In Version: ovirt-release44-4.4.0_alpha_2
Clone Of:
Environment:
Last Closed: 2020-05-20 20:02:52 UTC
oVirt Team: Node
Embargoed:
sbonazzo: ovirt-4.4?
sbonazzo: planning_ack?
sbonazzo: devel_ack+
cshao: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 104447 0 'None' 'MERGED' 'branding: align with ovirt-engine branding' 2019-11-25 09:41:13 UTC

Description Sandro Bonazzola 2018-07-05 10:59:48 UTC 
Just noticed that cockpit-ovirt login screen has the green based patternfly theme while the engine has a blue based one.
We should probably align.
Comment 1 Sandro Bonazzola 2019-01-21 08:28:32 UTC 
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0.
If you think this bug should block 4.3.0 please re-target and set blocker flag.
Comment 2 Sandro Bonazzola 2019-02-18 07:54:50 UTC 
Moving to 4.3.2 not being identified as blocker for 4.3.1.
Comment 5 Wei Wang 2019-12-17 05:55:13 UTC 
Test Version:
ovirt-node-ng-installer-4.4.0-2019121507.el8.iso
CentOS-7-x86_64-Minimal-1908.iso

Test Steps:
1. Install iso
2. Yum install ovirt 4.4 repos
3. Yum update
4. Yum install ovirt-engine
5. engine-setup

Result:
cockpit-ovirt and engine has the same blue based patternfly theme


Bug is fixed, move it to "VERIFIED"
Comment 6 Sandro Bonazzola 2020-05-20 20:02:52 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.