Bug 1275439 – rhel-osp-director [RFE]: Need to have a way to re-apply configuration done during the installation on the overcloud nodes.

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

Bug 1275439 - rhel-osp-director [RFE]: Need to have a way to re-apply configuration done during the installation on the overcloud nodes.

Summary:	rhel-osp-director [RFE]: Need to have a way to re-apply configuration done du...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	rhosp-director (Show other bugs)
Sub Component:
Version:	7.0 (Kilo)
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	y2
Target Release:	7.0 (Kilo)
Assigned To:	Jiri Stransky
QA Contact:	Alexander Chuzhoy
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:	1290949
Blocks:
	Show dependency tree / graph

Reported:	2015-10-26 18:30 EDT by Alexander Chuzhoy
Modified:	2015-12-21 11:57 EST (History)
CC List:	9 users (show)

See Also:
Fixed In Version:	python-rdomanager-oscplugin-0.0.10-21.el7ost openstack-tripleo-heat-templates-0.8.6-88.el7ost
Doc Type:	Enhancement
Doc Text:	This feature allows the reapplication of Puppet manifests on a deployed Overcloud. This ensures the overcloud has the desired configuration or can recover accidentally amended or deleted configuration files. To have Puppet run again on the Overcloud nodes, omit the "--templates" option but include the following two environments files at the beginning of your deployment: * /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml * /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml For example: $ openstack overcloud deploy -e ~/templates/overcloud-resource-registry-puppet.yaml -e ~/templates/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml [additional arguments from initial deployment]
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-12-21 11:57:23 EST
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
Launchpad	1505430	None	None	None	Never
Red Hat Product Errata	RHBA-2015:2651	normal	SHIPPED_LIVE	Red Hat Enterprise Linux OSP 7 director Bug Fix Advisory	2015-12-21 16:50:26 EST

Groups: None (edit)

Description Alexander Chuzhoy 2015-10-26 18:30:33 EDT

rhel-osp-director [RFE]: Need to have a way to re-apply configuration done during the installation on the overcloud nodes.

Environment:
openstack-heat-common-2015.1.1-5.el7ost.noarch
openstack-heat-engine-2015.1.1-5.el7ost.noarch
python-heatclient-0.6.0-1.el7ost.noarch
openstack-heat-api-cfn-2015.1.1-5.el7ost.noarch
openstack-heat-api-2015.1.1-5.el7ost.noarch
openstack-heat-api-cloudwatch-2015.1.1-5.el7ost.noarch



Scenario:
Ran "os-apply-config" as root, which did the following:
[2015/10/26 06:28:38 PM] [INFO] writing /etc/os-net-config/config.json
[2015/10/26 06:28:38 PM] [INFO] writing /etc/ntp.conf
[2015/10/26 06:28:38 PM] [INFO] writing /var/run/heat-config/heat-config
[2015/10/26 06:28:38 PM] [INFO] writing /etc/puppet/hiera.yaml
[2015/10/26 06:28:38 PM] [INFO] writing /etc/os-collect-config.conf
[2015/10/26 06:28:38 PM] [INFO] success



Need to have a way to "revert the change", basically to apply the configuration done during the installation in case some configuration file is overwritten.

Comment 2 Hugh Brock 2015-12-03 08:09:33 EST

https://review.openstack.org/#/c/244346/ fixes this and has been merged upstream. I'm asking for blocker for y2 and 8.0.

Comment 3 Jaromir Coufal 2015-12-03 08:56:46 EST

Acked, targeted for 7.2 blocker.

Comment 4 Jiri Stransky 2015-12-03 09:43:14 EST

The verification process would be to re-run openstack overcloud deploy command with the same arguments, and see in os-collect-config journal on a controller node that configuration (Puppet) is getting applied again.

Comment 7 Dan Yocum 2015-12-10 15:05:46 EST

Also see bug https://bugzilla.redhat.com/show_bug.cgi?id=1290042

The tl;dr synopsis is: add '-e ~/templates/pre-and-post-hooks-environment.yaml' as the last argument to ensure the systems maintain their RHSM Portal registration.

Comment 8 Jiri Stransky 2015-12-11 05:53:06 EST

Thanks Dan! I think we want rhel-registration-resource-registry.yaml, rather than pre-and-post-hooks-environment.yaml, right? See James' comment here:

https://bugzilla.redhat.com/show_bug.cgi?id=1290042#c10

I updated the doc text, please let me know if you think there's an issue still.

Comment 9 Steve Baker 2015-12-14 15:41:00 EST

bug 1290949 has some workarounds documented in it.

Comment 10 Alexander Chuzhoy 2015-12-16 10:39:36 EST

Verified:
Environment:
python-rdomanager-oscplugin-0.0.10-22.el7ost.noarch  
openstack-tripleo-heat-templates-0.8.6-94.el7ost.noarch

Changed files:
/etc/puppet/hiera.yaml
/etc/glance/glance-api.conf


Re-ran the deployment command.

Verified the files reverted to their original version.

Comment 12 errata-xmlrpc 2015-12-21 11:57:23 EST

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-2015:2651

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