quantum native types prefetch the quantum conf before it exists
Bug #1197588 reported by
Michael Chapman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-neutron |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
when creating networks, subnets and routers using the native types, the quantum.conf values are prefetched at the start of the puppet run, at which point it may contain no data. This is never re-read and can cause issues when using those types.
affects: | puppet-openstack → puppet-neutron |
Changed in puppet-neutron: | |
milestone: | none → 2.1.1 |
Changed in puppet-neutron: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/35582 github. com/stackforge/ puppet- quantum/ commit/ 894e1871e69b009 85688b536667e12 907cbaa035
Committed: http://
Submitter: Jenkins
Branch: master
commit 894e1871e69b009 85688b536667e12 907cbaa035
Author: Michael Chapman <email address hidden>
Date: Thu Jul 4 11:03:51 2013 +1000
Remove native type prefetches
The network, router, subnet and router interface
providers attempt to prefetch the configuration,
which can result in empty or stale values being
loaded as quantum configuration. The former will
result in errors stating the quantum.conf file
is incomplete, while the latter will often
result in authentication errors.
This patch removes the prefetching in the child
classes and explicitly sets the conf to nil in
the parent quantum provider so that it will be
loaded at the correct time.
Change-Id: Ia2dbc8b687498b e96d09c9286fb3f 07e0c5b8f96
bug 1197588