Article number
Affected Versions
Source Hypervisor
Target Hypervisor

Failover To AWS Fails And VPG Is In Error Status

Viewed 283 times

Root Cause

Prior to kicking off said Failover, a Private IP was assigned to a VM to spin up with on the AWS site.

The Failover actually fails due to the following error found in the ZVM logs for the task which states the Private IP being assigned is already in use:

20-02-19 20:47:29.72,E,179,AWSImage,LaunchInstanceFromAmi,Failed to create instance type t2.medium id ami-0432b177e9423a8c2 in AZ <Availability_Zone>: Address <IP Address> is in use.,"Amazon.EC2.AmazonEC2Exception Boolean HandleException(Amazon.Runtime.IExecutionContext, Amazon.Runtime.Internal.HttpErrorResponseException) Amazon.EC2.AmazonEC2Exception: Address <IP Address> is in use. ---> Amazon.Runtime.Internal.HttpErrorResponseException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.


A Failover reportedly fails to AWS and a VPG enters an "Error" status.



1] If the VPG is in the "Error" status, you will need to recreate the VPG manually (which may require a Force Delete). At this time, preseed is not supported into AWS, thus an initial sync will be seen.

2] Prior to next attempt, either remove the Private IP address entirely from the VPG Configuration or pick a Private IP address that is not in use within the VPC in AWS. The easier option is to just remove the Private IP entirely and then check what Private IP is assigned to the EC2 instance on the AWS Dashboard.