upgrading from 2.2.2.8 to 2.2.3.4 Getting 502: [object Object on gui

[dtwoods83]

I am Getting a 502: [object Object]. on DNA Gui and I am unable to login. After trying to upgrade from 2.2.2.8 to 2.2.3.4. I am able to log into the CLI. 

sudo maglev system_updater update_info

System updater is not available, please retry after some time

sudo journalctl -u maglev-node-updater -f

Mar 04 02:31:47 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 430494d61d10 35973e40b098 "/bin/sh -c '. /opt/…" 13 months ago Up 20 seconds maglev-web-install
Mar 04 02:31:47 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 1e7b547cce21 14d640cef89d "/usr/local/lib/node…" 13 months ago Up 20 seconds maglev-install-ui
Mar 04 02:31:47 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 2022-03-04 02:31:47 | /data/maglev/srv/system-updates/nodeupdater/exported-docker-images/archive-core-images.tgz not found
Mar 04 02:31:47 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 2022-03-04 02:31:47 | Waiting for ETCD to come up
Mar 04 02:31:53 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 2022-03-04 02:31:53 | Current update state (/maglev/system_updates/node_updates/nodes//state): UPDATED
Mar 04 02:31:53 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 2022-03-04 02:31:53 | Current update state (/maglev/system_updates/node_updates/nodes//state): UPDATED
Mar 04 02:32:23 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: NAME STATUS ROLES AGE VERSION
Mar 04 02:32:23 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: Ready master 400d v1.15.3-cisco
Mar 04 02:32:26 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 2022-03-04 02:32:26 | The node-reboot-in-progress:NoSchedule taint not present on , nothing to do
Mar 04 02:32:26 maglev-master-172-16-0-20 nodeupdater-service.sh[3081]: 2022-03-04 02:32:26 | Waiting for notification from system updater...

This is a one node environment. 

If anyone could help with this issue.

[Dan Rowe]

From the log snippet provided, it is hard to say what exactly the issue may be. I would suggest opening up a TAC case to get a DNA Center SSPT TAC engineer involved to take a look. Make sure to provide the log output from the snippet you provided along with the AURA pdf report to the TAC case.

How to generate AURA pdf report on Cisco DNA Center:

-- https://www.cisco.com/c/en/us/support/docs/cloud-systems-management/dna-center/215840-cisco-dna-center-aura-audit-and-upgrad.html

[dtwoods83]

Opened a case with Tac and then DNA just started to work by itself. No clue what the cause was or what the issue was. 

Just fixed itself