Environment

• Yugabyte Platform

Issue

Yugabyte universe upgrade is stuck at the "Downloading Software" phase when the universe is deployed on AWS.

Resolution

Overview

While preparing the AWS cloud environment as a cloud provider, We have to change below metadata options:

1.  --http-put-response-hop-limit to 3

The desired HTTP PUT response hop limit for instance metadata requests. This meta-data option key
limits the number of hops that metadata requests can travel across a network. The larger the number, the further instance metadata requests can travel.

2. --http-endpoint to enabled

This parameter enables or disables the HTTP metadata endpoint on your instances. If it is disabled, you will not be able to access your instance metadata.

3. --region to <ec2 instance region> (Ex: us-west-2)

Steps

1. Run the below command to change the metadata options as described above:

aws ec2 modify-instance-metadata-options --instance-id i-NNNNNNN --http-put-response-hop-limit 3 --http-endpoint enabled --region REGION

Where:

• NNNNNNN is your EC2 instance ID
• REGION is your EC2 instance's region

Once you run the above command, You should get an output like below:

{
   "InstanceId": "i-0a1977f2ced158d94",
   "InstanceMetadataOptions": {
      "State": "pending",
      "HttpEndpoint": "enabled",
      "HttpTokens": "optional",
      "HttpPutResponseHopLimit": 3
   }
}

Notice that State is still "pending" and it will become "applied" in some time.

2. Verify

You can verify it using the below command:

aws ec2 describe-instances --instance-id i-NNNNNNN

You can look for "MetadataOptions" which will look like below:

"MetadataOptions": {
   "State": "applied",
   "HttpEndpoint": "enabled",
   "HttpTokens": "optional",
   "HttpPutResponseHopLimit": 3
},

Additional Information

Prepare the Amazon Web Services (AWS) cloud environment | YugabyteDB Docs