Bug 1426439

Summary:	puppet-nova idempotency issue causes nova api restarts during updates
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	puppet-nova	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Alex Schultz <aschultz>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	emacchi, jjoyce, jschluet, ohochman, slinaber, srevivo, tvignaud, vaggarwa
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-nova-9.5.0-5.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-28 14:44:12 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:
Bug Depends On:
Bug Blocks:	1421883

Description Alex Schultz 2017-02-23 22:28:22 UTC

Description of problem:
When nova::scheduler::filter::scheduler_available_filters is set to [], puppet thinks something needs to be written out to the config file but it doesn't actually write anything out. This can cause rerunning of nova db syncs and nova-api restarts everytime it's run.

Version-Release number of selected component (if applicable):
openstack-puppet-modules-9.3.0-1.el7ost.noarch.rpm

How reproducible:
Update the stack after deploying, nova-api will restart in multiple steps because puppet thinks it needs to set scheduler_available_filters.

Steps to Reproduce:
1.
2.
3.

Actual results:
Puppet tries to configure scheduler_available_filters and causes a nova-api restart.

Expected results:
Puppet shouldn't attempt to configure scheduler_available_filters every time.

Additional info:
Related BZ 1421883

Comment 2 Alex Schultz 2017-03-21 22:35:38 UTC

Verified that nova::scheduler::filter::scheduler_available_filters  is no longer showing as being created on stack update

Comment 5 errata-xmlrpc 2017-06-28 14:44:12 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-2017:1585