Problem Description
When attempting to upgrade an AWS proxy directly from the Druva Cloud Platform console, the upgrade process fails to progress. The console continuously displays the status as Upgrade Scheduled, but the actual upgrade never initiates or completes.
Causes
Lack of Direct Internet/Network Access: The proxy cannot reach the Druva cloud repositories to download the necessary upgrade packages.
Missing or Inaccessible EC2 Key Pair: The original key pair associated with the proxy instance has been lost or deleted, preventing direct SSH access for local log verification and troubleshooting.
Resolution
Follow these sequential troubleshooting and resolution steps to address the stuck upgrade:
Step 1: Local Log Analysis (If Key Pair is Available)
If you still have access to the original EC2 key pair associated with the proxy instance:
Assign an Elastic IP (EIP) to the affected AWS proxy instance to allow temporary external connectivity.
Log into the proxy via SSH using your EC2 key pair.
Inspect the Druva proxy logs located in
/var/log/(or your specific Druva agent log directory) to identify exact network blockages, firewall rejections, or download failures. Fix the underlying network block to allow the upgrade to finish.
Step 2: Deploy a Replacement Proxy (If Key Pair is Lost)
If the original key pair is unavailable, blocking local log access, deploying a fresh proxy is the most efficient solution:
Log into your AWS Management Console and create a new EC2 key pair.
Deploy a brand-new Druva AWS proxy in the same AWS region, ensuring you select the newly created key pair during configuration.
Verify that the new proxy registers successfully and shows a connected status within the Druva console.
Decommission the old, stuck proxy instance once the new one is functional.