Guest

Preview Tool

Cisco Bug: CSCvu54856 - AA ETSI VNF VimConnectionInfo updates do not replicate on follower nodes (instantiate will fail)

Last Modified

Aug 28, 2020

Products (1)

  • Cisco Elastic Services Controller

Known Affected Releases

5.3

Description (partial)

Symptom:
When ESC is deployed in an ETSI active-active configuration, if initial VNF VimConnectionInfo is modified those modifications are not replicated on follower node VIM connectors.   As a result any instantiation that is performed downstream of the VimConnectionInfo change that maps to the modified connector on a follower node will fail. 

A follower node receiving a deployment against VIM connector in this state will generate the following error log.  Example 

2020-06-05 05:55:10.970 INFO  ===== DEPLOY SERVICE REQUEST RECEIVED (UNDER TENANT) =====
2020-06-05 05:55:10.970 INFO  Tenant name: etsi_tenant
2020-06-05 05:55:10.970 INFO  Deployment name: jenkins-OSRESTTestETSIVimConnectorsGrantResponse-389979
2020-06-05 05:55:10.970 INFO  Deployment internal id 4404731a-c0bc-49d5-a478-9ddf1361e50c
2020-06-05 05:55:11.410 ERROR The VIM Connector [jenkins-test_a_grantCreateUnknownVimId-405801] referred in the deployment [jenkins-OSRESTTestETSIVimConnectorsGrantResponse-389979] is in NO_CREDENTIALS status. All VIM Connectors referred in this deployment should be in CONNECTION_SUCCESSFUL status to proceed.
com.cisco.esc.datamodel.exceptions.ESCException: The VIM Connector [jenkins-test_a_grantCreateUnknownVimId-405801] referred in the deployment [jenkins-OSRESTTestETSIVimConnectorsGrantResponse-389979] is in NO_CREDENTIALS status. All VIM Connectors referred in this deployment should be in CONNECTION_SUCCESSFUL status to proceed.
	at com.cisco.esc.confd.ConfdActionUtil.assertVimReady(ConfdActionUtil.java:224)
	at com.cisco.esc.confd.EscConfdAction.deployService(EscConfdAction.java:441)

Conditions:
VNF VIM connector VimConnectionInfo is modified in AA configuration and deployment is allocated to a follower node.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.