Guest

Preview Tool

Cisco Bug: CSCvv52442 - vSmart Upgrade From 20.1.12 to 20.3.1 Failing With Error "Failed to install: "

Last Modified

Sep 18, 2020

Products (1)

  • Cisco vEdge Router

Known Affected Releases

20.1.2

Description (partial)

Symptom:
When upgrading vSmart from 20.1.12 to 20.3.1 the upgrade fails with error "Failed to install: "

Error seen in vmanager-server.log

INFO  [] [DefaultInstallMonitor] (Install Monitor thread - xxxxxxxxxxxxx) || For software_install Processing Notification -> <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
	  <eventTime>2020-08-26T14:19:45.000308+00:00</eventTime>
	  <system-software-install-status xmlns="http://viptela.com/actions">
		<severity-level>minor</severity-level>
		<host-name>hostname</host-name>
		<system-ip>xxxxxxxxxxxxx</system-ip>
		<status>install-fail</status>
		<install-id>3ec25ec3-8b1e-4491-b294-f15633bac717</install-id>
		<message>Failed to install: </message>
	  </system-software-install-status>
	</notification>


Error seen in vManage UI

Installing and activating software image
Current active partition: 20.1.12
Configuring upgrade confirm timer to 15 minutes
Software image: viptela-20.3.1-x86_64.tar.gz
Software image download may take upto 60 minutes
Connection Instance: 0, Color: default
Downloading http://xxxxxxxxxxxxx:8080/software/package/viptela-20.3.1-x86_64.tar.gz?deviceId=xxxxxxxxxxxxx
Downloaded http://xxxxxxxxxxxxx:8080/software/package/viptela-20.3.1-x86_64.tar.gz?deviceId=xxxxxxxxxxxxx
Failed to install: 
Failed to process device request -  
	Error type : application 
	Error tag : operation-failed 
	Error info : <error-info>
	  <bad-element>install</bad-element>
	</error-info>

Conditions:
1. vManage and vBond are already upgraded to 20.3.1.
2. vSmart is running on 20.1.12.
3. Attempt is made to upgrade the vSmart to 20.3.1 with or without checking "Activate and Reboot"
4. Upgrade fails with error "Failed to install: "
5. "show reboot history" on the vSmart shows reboot reason "Software initiated - Kernel Panic"
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.