Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1804473

Summary:	After undercloud deployment .config has ownership or root.root
Product:	Red Hat OpenStack	Reporter:	Joachim von Thadden <j.thadden>
Component:	python-tripleoclient	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.0 (Train)	CC:	emacchi, hbrock, jschluet, jslagle, mburns, mgarciac
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-12.3.2-0.20200226135426.27ace2c.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-14 12:16:10 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:

Description Joachim von Thadden 2020-02-18 22:44:25 UTC

Description of problem:
After any deployment of the undercloud the ownership of ~/.config directory changes to root.root. As I only tested on new and freshly created stack users is could well be that this does not happen if ~/.config is already there and has not to be created by the installer.


How reproducible:
Always

Steps to Reproduce:
1. create an new user stack
2. openstack undercloud install
3. after successful installation ~/config is created for ~/.config/openstack/clouds.yaml
4. this .config directory has ownership root.root

Actual results:
~/.config directory has ownership root.root

Expected results:
~/.config directory has ownership stack.stack or whatever user was used

Additional info:
This leads to failures with other software trying to create directories below ~/.config and failing.

Comment 8 errata-xmlrpc 2020-05-14 12:16:10 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/RHBA-2020:2114