Bug 1134612

Summary:	update vsm credential correctly
Product:	Red Hat OpenStack	Reporter:	dontu
Component:	openstack-neutron	Assignee:	Steven Hillman <sthillma>
Status:	CLOSED ERRATA	QA Contact:	Ofer Blaut <oblaut>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0 (RHEL 7)	CC:	chrisw, ihrachys, jlibosva, lpeer, morazi, nyechiel, yeylon
Target Milestone:	z2	Keywords:	OtherQA, ZStream
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	n1kv
Fixed In Version:	openstack-neutron-2014.1.2-14.el6ost openstack-neutron-2014.1.2-12.el7ost	Doc Type:	Bug Fix
Doc Text:	Cause: Old VSM credentials are not removed from the db. Consequence: Config is sent to the old VSM even when a new VSM credential has been configured in the cisco_plugins.ini file and neturon has restarted. Fix: Remove VSM credentials from the db on neutron boot to ensure there is only the currently configured one. Result: New VSM credentials are the only ones present in the database and the new VSM is the only one getting new configuration.	Story Points:	---
Clone Of:
Clones:	1137029 (view as bug list)		Environment:
Last Closed:	2014-11-03 08:38:52 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:	1154145, 1154159

Description dontu 2014-08-27 23:25:02 UTC

Description of problem:

Today if we modify the n1kv VSM credential in the cisco_plugins.ini, the
older VSM ip address remains in the db, and all requests are sent to
the older VSM. This patch deletes all n1kv VSM credentials on neutron
start up before adding the newer VSM credentials. Hence making sure
that there is only one n1kv VSM IP address and credential in the db.

Comment 2 dontu 2014-08-28 22:20:19 UTC

Merged into Juno master on 7/25

Comment 5 errata-xmlrpc 2014-11-03 08:38:52 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://rhn.redhat.com/errata/RHSA-2014-1786.html