Bug 1382503 - Failed upgrade step doesn't prevent the following steps to proceed
Summary: Failed upgrade step doesn't prevent the following steps to proceed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 20:24 UTC by Ivan Necas
Modified: 2019-09-26 14:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17191 0 None None None 2016-11-02 23:06:35 UTC

Description Ivan Necas 2016-10-06 20:24:18 UTC
Description of problem:

If there is an issue with running a step in the pre-upgrade script,
the upgrade script continues with the execution. This might lead to more
serious issues later in the upgrade and complicates the debugging.

Steps to Reproduce:
1. run upgrade in which some migration steps fail

Actual results:

The upgrade continues with next steps

Expected results:

The upgrade fails immediately, providing enough information about the error.

Comment 2 Ivan Necas 2016-11-02 23:06:32 UTC
Created redmine issue http://projects.theforeman.org/issues/17191 from this bug

Comment 3 Ivan Necas 2017-01-24 23:27:21 UTC
Fix proposed at https://github.com/Katello/katello-installer/pull/471

Comment 4 Satellite Program 2017-01-25 01:15:29 UTC
Upstream bug assigned to inecas

Comment 5 Satellite Program 2017-01-25 01:15:32 UTC
Upstream bug assigned to inecas

Comment 6 Satellite Program 2017-01-26 19:15:51 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17191 has been resolved.

Comment 10 Satellite Program 2018-02-21 16:54:37 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.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336


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