Bug 1375734

Summary: when upgrading form 6.2.z (now on CDN) to 6.2.2, two red rows are printed mentioning elasticsearch and gutterball
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: UpgradesAssignee: Chris Roberts <chrobert>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.2.0CC: bbuckingham, chrobert
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-22 19:25:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jan Hutař 2016-09-13 20:57:18 UTC
Description of problem:
When upgrading form 6.2.z (now on CDN) to 6.2.2, two red rows are printed mentioning elasticsearch and gutterball. These are harmless, but should not be printed in red colour.


Version-Release number of selected component (if applicable):
upgrading form 6.2.z (now on CDN) to 6.2.2


How reproducible:
always


Steps to Reproduce:
1. Install 6.2.z from CDN and setup 6.2.2 repo
2. # yum upgrade
3. # satellite-installer --upgrade


Actual results:
[root@ibm-x3650-03 ~]# yum upgrade
[...]
---> Package satellite.noarch 0:6.2.1-1.3.el7sat will be updated
---> Package satellite.noarch 0:6.2.2-1.1.el7sat will be an update
[...]
---> Package tfm-rubygem-katello.noarch 0:3.0.0.73-1.el7sat will be updated
---> Package tfm-rubygem-katello.noarch 0:3.0.0.78-1.el7sat will be an update
[...]
Complete!
[root@ibm-x3650-03 ~]# satellite-installer --upgrade
[...]
Upgrade Step: elasticsearch_message...
package elasticsearch is not installed   # <--- this line is red
[...]
Upgrade Step: remove_gutterball...
package gutterball is not installed   # <--- red as well
[...]


Expected results:
These lines should be in normal colour so they do not alert whoever is doing upgrade

Comment 3 Brad Buckingham 2016-09-22 19:25:01 UTC

*** This bug has been marked as a duplicate of bug 1357472 ***