Cisco Bug: CSCvt25675 - Heal retry for individual VM fails when update is requested and vm name is overwritten
May 31, 2020
- Cisco Elastic Services Controller
Known Affected Releases
Symptom: When first heal request for individual VM which includes also day-0 update or sw-image update fails because of conditions in VIM (not enough resources for example) and then conditions are changed to meet expectation, the same heal request send second time also fails with error: "No resource found matching specified generated VM name." Conditions: Heal request for individual vm is send which includes also day-0 or sw-image update. It fails and failure is expected. Next the same heal request is send (or ETSI retry operation) and it is suppose to work (conditions on vim are changed).
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases