create-instance-export-task expired and automatically canceled

prnr commented 6 months ago

Describe the bug

I used the ec2 create-instance-export-task command to export one instance with a single 8GB volume, and waited for over 100 hours. And today, I checked the progress with the describe-export-task command and found the following results. The other instance I have has been exported normally, and only one is not being exported.

This instance is an instance where CentOS volume is connected to Amazon Linux 2023, so I'm wondering if CentOS is a problem. However, if that's a problem, I don't understand issuing an export command and displaying the state as active for 100 hours. I registered this question on Discussion, but I haven't answered in more than 2 weeks, so I re-register on Bugs.

Is there any way to check why it's not progressing?

Expected Behavior

Expect export to be completed within 3-10 hours

Current Behavior

aws ec2 describe-export-tasks --export-task-ids export-i-095dc8b13d450a9c0 { "ExportTasks": [ { "ExportTaskId": "export-i-095dc8b13d450a9c0", "ExportToS3Task": { "ContainerFormat": "ova", "DiskImageFormat": "vmdk", "S3Bucket": "backup-greon", "S3Key": "vms/export-i-095dc8b13d450a9c0.ova" }, "InstanceExportDetails": {}, "State": "cancelled", "StatusMessage": "Task expired and automatically canceled" } ] }

Reproduction Steps

aws ec2 create-instance-export-task --instance-id i-0ef25ad9e25c7e932 --target-environment vmware --export-to-s3-task file://config.json

in config.json

{ "ContainerFormat": "ova", "DiskImageFormat": "VMDK", "S3Bucket": "backup-greon", "S3Prefix": "vms/" }

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.15.2

Environment details (OS name and version, etc.)

Python/3.11.6 Windows/11 22h2 23606.1000 exe/AMD64 prompt/off

RyanFitzSimmonsAK commented 6 months ago

Hi @prnr, thanks for reaching out. Could you provide debug logs of your create-instance-export-task operation being cancelled? You can get debug logs by adding --debug to your command, and redacting any sensitive information. Thanks!

prnr commented 5 months ago

Hi @prnr, thanks for reaching out. Could you provide debug logs of your create-instance-export-task operation being cancelled? You can get debug logs by adding --debug to your command, and redacting any sensitive information. Thanks!

At the time of starting the creation, it is not immediately canceled, but only 100 hours after the creation is executed is canceled. The 'describe' of the export task that has been in progress for 80 hours, the 'describe' of the canceled task, and the log in the case of a new 'create' are attached as txt files, respectively.

create_export.txt describe_canceled.txt describe.txt

RyanFitzSimmonsAK commented 5 months ago

Thanks for following up. As far as I can tell, the debug logs don't indicate any issue with the CLI, leading me to believe this is a service team issue. I've reached out to the EC2 team about what could be the issue here. In the meantime, as this is a service team issue, I'm going to transfer this to our cross-SDK repository (https://github.com/aws/aws-sdk/). I'll leave any updates in this issue. Thanks!

Ticket # for internal use : P112677642

prnr commented 5 months ago

Thanks for following up. As far as I can tell, the debug logs don't indicate any issue with the CLI, leading me to believe this is a service team issue. I've reached out to the EC2 team about what could be the issue here. In the meantime, as this is a service team issue, I'm going to transfer this to our cross-SDK repository (https://github.com/aws/aws-sdk/). I'll leave any updates in this issue. Thanks!

Ticket # for internal use : P112677642

How can I check the progress related to this? Due to the maintenance cost issue, we have to delete the instance as soon as possible (originally, January 10 was the deadline for deletion). And can I ask the customer center with this ticket using the basic plan? If possible, how can I proceed with the inquiry?

RyanFitzSimmonsAK commented 5 months ago

The export task failed because the volume was originally created from an AMI which contains a Marketplace Code. From the EC2 documentation,

You can't export an instance if it contains third-party software provided by AWS. For example, VM Export cannot export Windows or SQL Server instances, or any instance created from an image in the AWS Marketplace.

You can use the DescribeImages to determine if an image is from the AWS Marketplace. Please let me know if you have any other questions.

github-actions[bot] commented 4 months ago

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

aws / aws-sdk