Bug 1568369 – Stop carrying over previous config on update/upgrade prepare commands

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1568369 - Stop carrying over previous config on update/upgrade prepare commands

Summary:	Stop carrying over previous config on update/upgrade prepare commands

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	python-tripleoclient (Show other bugs)
Sub Component:
Version:	13.0 (Queens)
Hardware:	All All

Priority	high Severity high
Target Milestone:	beta
Target Release:	13.0 (Queens)
Assigned To:	Jiri Stransky
QA Contact:	Marius Cornea
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-04-17 07:18 EDT by Jiri Stransky
Modified:	2018-06-27 09:51 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	python-tripleoclient-9.2.0-4.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-06-27 09:51:11 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
OpenStack gerrit	559753	None	stable/queens: MERGED	python-tripleoclient: Stop persisting previous configuration on update/upgrade prepare (I9db2c9256ed20d4d0b74bb467ee6ae0...	2018-04-19 10:29 EDT
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:51 EDT

Groups: None (edit)

Description Jiri Stransky 2018-04-17 07:18:23 EDT

Carrying over old configuration has proven troublesome, is directly related bug 1541024 on upgrades, but similar might happen on updates. It's not safe and we should disable it. In code it's isolated, so we just need to flip a boolean flag to switch it off.

Comment 4 errata-xmlrpc 2018-06-27 09:51:11 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/RHEA-2018:2086

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