kong status is pending in DNA Center

[mono noor]

hi. 

in DNA Cisco Center:

I connected to web interface in previous month, but a few day I Unable to connect web interface.

An error occurred during a connection to x.x.x.x.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

in CLI run this:

$ maglev package status

Error: httpsConnectionPool (host='kong-forntend.maglev-system.svc.cluster.local', port=443): Max retries exceeded with url: /api/system/vl/catalog/package?allVersions=false&repo ............................

I run this:

$ magctl appstack status -f

this answer:

maglev-system kong-6466c9f78d-2szdh 0/2 pending

$ magctl service restart --hard kong

Performing hard restart of maglev-system/kong-6466c9f78d-2szdh

"kong-6466c9f78d-2szdh" deleted

$ magctl appstack status | grep kong

maglev-system kong-1677107563-56cg7 0/2 Pending 0 20s

and I wait but not start it

maglev-system kong-1677107563-56cg7 0/2 Pending 0 13h

[tpoulose]

If a pod is not in the running state run the command ' magctl service status <pod name> ' and check the events section at the bottom to see why. The below CL session has some other troubleshooting commands you can use however I would suggest opening a TAC case.

https://www.ciscolive.com/c/dam/r/ciscolive/us/docs/2019/pdf/5eU6DfQV/TECARC-2100.pdf

[Benjamin-A]

Is your version 2.2.3.5 or lower?

My guess is TAC will have to renew the certs.

You can check it with:

sudo maglev-config certs info

[mono noor]

how to find my version from cli?

$ sudo maglev-config certs info

--------------------------------------------------------------------------------
certificate start date end date
--------------------------------------------------------------------------------
credentialmanager.pem Jun 26 02:06:31 2022 GMT Jun 26 02:06:31 2023 GMT
kong.pem Jun 26 02:06:31 2022 GMT Jun 26 02:06:31 2023 GMT
kube-worker-1.pem Jun 26 02:06:31 2022 GMT Jun 26 02:06:31 2023 GMT
maglev-registry.pem Jun 26 02:06:31 2022 GMT Jun 26 02:06:31 2023 GMT
apiserver.crt Jan 7 10:07:08 2021 GMT Jun 26 02:03:26 2023 GMT
apiserver-kubelet-client.crt Jan 7 10:07:08 2021 GMT Jun 26 02:03:26 2023 GMT
front-proxy-ca.crt Jan 7 10:18:12 2021 GMT Jan 5 10:18:12 2031 GMT
front-proxy-client.crt Jan 7 10:18:12 2021 GMT Jun 26 02:03:27 2023 GMT
admin.conf Jan 7 10:07:08 2021 GMT Jun 26 02:03:28 2023 GMT
scheduler.conf Jan 7 10:07:08 2021 GMT Jun 26 02:03:28 2023 GMT
controller-manager.conf Jan 7 10:07:08 2021 GMT Jun 26 02:03:28 2023 GMT
--------------------------------------------------------------------------------

$magctl appstack status maglev-system
kong-6466c9f78d-59ht5 0/2 Pending 0 17h <none> <none> <none> <none>

$maglev system_updater update_info
System updater is not available, please retry after some time

$maglev catalog settings display
and
$maglev catalog release_channel display -V

ERROR: HTTPSConnectionPool(host='kong-frontend.maglev-system.svc.cluster.local', port=443): Max retries exceeded with url: /api/system/v1/catalog/settings?repository=main (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f69839ea110>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

$maglev catalog settings validate
Validating catalog server settings...
ERROR: HTTPSConnectionPool(host='kong-frontend.maglev-system.svc.cluster.local', port=443): Max retries exceeded with url: /api/system/v1/catalog/settings/status?repository=main (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f1446039190>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))