Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1370641 - Upgrade from 3.1 to 3.2 overwrites AWS variables in /etc/sysconfig/atomic-openshift-master-*
Upgrade from 3.1 to 3.2 overwrites AWS variables in /etc/sysconfig/atomic-ope...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.2.1
Unspecified Unspecified
high Severity medium
: ---
: 3.2.1
Assigned To: Scott Dodson
Anping Li
: UpcomingRelease
Depends On: 1353354
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-26 16:49 EDT by Scott Dodson
Modified: 2016-11-25 03:05 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, AWS related environment variables were removed from /etc/sysconfig/atomic-openshift-master files during an upgrades if these values were not included in the advanced installer's inventory file. We now preserve these variables during upgrades.
Story Points: ---
Clone Of: 1353354
Environment:
Last Closed: 2016-09-12 13:36:33 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1853 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security update and bug fix update 2016-09-12 17:33:16 EDT

  None (edit)
Comment 1 Brenton Leanhardt 2016-08-29 08:28:32 EDT
There's another 3.2.1 PR we'd like to ship soon so my vote is to bundle this in to the same advisory.
Comment 4 Anping Li 2016-08-30 03:23:19 EDT
There are AWS variables after ugprade from v3.1 to v3.2, so move to verified.
Comment 6 errata-xmlrpc 2016-09-12 13:36:33 EDT
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-2016:1853

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