RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 806627 - console colors over ssh should be painted red
Summary: console colors over ssh should be painted red
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-25 13:53 UTC by Mike Burns
Modified: 2016-04-26 14:19 UTC (History)
9 users (show)

Fixed In Version: ovirt-node-2.3.0-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-19 14:19:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
console color over ssh (42.02 KB, image/png)
2012-03-31 02:42 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

Description Mike Burns 2012-03-25 13:53:26 UTC
Description of problem:
Currently, colors on an alternate terminal (i.e. ssh) show up with the same colors as upstream.  We should re-paint these red as we did with the regular console

Version-Release number of selected component (if applicable):
6.3

How reproducible:
always

Steps to Reproduce:
1.install
2.log into system over ssh as admin
3.
  
Actual results:
colors are blue

Expected results:
colors should be closer to default colors (red, not blue)

Additional info:

colors are still *much* better than the crazy colors previously on ssh

Comment 3 Guohua Ouyang 2012-03-31 02:42:17 UTC
Created attachment 574117 [details]
console color over ssh

tested on 6.3-20120330.0, which ovirt-node is ovirt-node-2.3.0-1.1.el6.noarch

the console color over ssh is not red yet, please see attachment.

QE will re-test when ovirt-node version is above ovirt-node-2.3.0-2.el6.

Comment 4 Mike Burns 2012-04-02 11:57:45 UTC
Failing this BZ -- needs debugging as to why it didn't work correctly

Comment 7 Guohua Ouyang 2012-04-17 02:56:33 UTC
verified on 6.3-20120411.1 build, the console color on the top is red.

Comment 8 Stephen Gordon 2012-05-28 17:40:53 UTC
Setting technical_note- as this is already covered in the note for another bug on the same errata.

Comment 10 errata-xmlrpc 2012-07-19 14:19:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0741.html


Note You need to log in before you can comment on or make changes to this bug.