Guest

Preview Tool

Cisco Bug: CSCvu15218 - Cisco DNA Center upgrade to 1.3.3.5 is failing at 41% due to 2/3 rabbitmq instances in crashloop

Last Modified

Sep 19, 2020

Products (1)

  • Cisco DNA Center

Known Affected Releases

DNAC1.3.1.6

Description (partial)

Symptom:
On rabbitmq-2, rabbitmq server was running, but the mnesia was stopped due to the "pause minority" policy during the upgrade. Because of this, the other two rabbitmq instances could reach rabbitmq-0 but could not join the cluster

 

root@rabbitmq-2:/
=INFO REPORT==== 5-May-2020::23:23:49 ===
rabbit on node 'rabbit@rabbitmq-0.rabbitmq.maglev-system.svc.cluster.local' down

=INFO REPORT==== 5-May-2020::23:23:49 ===
node 'rabbit@rabbitmq-0.rabbitmq.maglev-system.svc.cluster.local' down: connection_closed

=WARNING REPORT==== 5-May-2020::23:23:49 ===
Cluster minority/secondary status detected - awaiting recovery

=INFO REPORT==== 5-May-2020::23:23:49 ===
RabbitMQ is asked to stop...

Conditions:
The problem is observed with 3-node cluster
- This has been seen when upgrading to 1.3.3.5, where the upgrade stalls at 41%
- Also it was noticed on 1.3.1.5 > 1.3.1.6 upgrade

Related Community Discussions

<key>CSCvu15218</key> - Upgrade from dnac 1.3.1.6 to 1.3.3.5 is failing at 41 percent due to 2/3 rabbitmq instances in crashloop
Seen also when upgrading a 3-node cluster from 1.3.3.4 to 1.3.3.5. TAC resolved the issue within a couple of hours after diagnosing the issue and relating to this bug.
Latest activity: Jun 10, 2020
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.