Why the Defender Version may not update on the Prisma Cloud Console after an Upgrade?
770
Created On 01/26/24 09:40 AM - Last Modified 04/30/24 09:54 AM
Question
Why the Defender Version may not update on the Prisma Cloud Console after an Upgrade?
Environment
- Prisma Cloud Compute Edition
- Prisma Cloud Enterprise Edition
Answer
- The Defender updates its attributes and state including its version during Defender Startup
- If there is any web socket connection issue between the Defender and Console, then the Defender may not be able to report itself to the Console
- As a result, the older Defender version may remain in the Console db and the Console UI will reflect the same
- You may see a successful connection entry in the Defender Log (below), however, this flow only handles a reconnection of the Defender(s) and won't update the actual defender version in the console db:
DEBU 2023-12-12T04:18:44.725 pubsub_defender.go:540 Received new connection: defenderConn={hostname:aks-agentpool1-12345678-vmss000001 localAddr:10.10.10.230:8084 remoteAddr:10.10.11.110:47486} defenderType=cri defenderVersion=22.12.699 lastConnected=0001-01-01 00:00:00 +0000 UTC totalConnections=500
Additional Information
- Since there were Connectivity issues during the Defender startup, you can restart the Defender in concern