Bug 1406068
Summary: | Do not log the expected actions as errors in installer log | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> |
Component: | Upgrades | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.6 | CC: | bbuckingham, bkearney, inecas, mbacovsk, sthirugn |
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
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: | 2017-09-13 18:03:15 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1410795 |
Description
sthirugn@redhat.com
2016-12-19 16:00:10 UTC
Correction: The upgrade happened from 6.2.4 to 6.2.6 Update: Good news - Rerunning `satellite-installer --scenario satellite --upgrade` on the already updated 6.2.6 does not show this error. Hi Suresh, Are the following statements correct? - upgrading from 6.2.z (e.g. 6.2.[1|2|3|4|5) to a later 6.2.z (e.g. 6.2.6) shows the error mentioned - upgrading from 6.2.z (e.g. 6.2.6) to the same 6.2.z (e.g. 6.2.6) does not show the error mentioned (In reply to Brad Buckingham from comment #4) > Hi Suresh, > > Are the following statements correct? > > - upgrading from 6.2.z (e.g. 6.2.[1|2|3|4|5) to a later 6.2.z (e.g. 6.2.6) > shows the error mentioned > > - upgrading from 6.2.z (e.g. 6.2.6) to the same 6.2.z (e.g. 6.2.6) does not > show the error mentioned Yes you are right. Recently (not sure in which release) we added a check to see if an upgrade step is already ran, if yes, it will not be run again in future. Suresh, would this still be a valid bug then? If the step is skipped on subsequent runs, I assume the error would no longer exist. It looks like that change was introduced with bug 1264597 in 6.2.4. The error would still be shown when upgrading to 6.2.6 for the first time. But, since there are no customer tickets on this, I am okay with closing this. |