Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create-instance-export-task expired and automatically canceled #674

Closed
prnr opened this issue Jan 2, 2024 · 6 comments
Closed

create-instance-export-task expired and automatically canceled #674

prnr opened this issue Jan 2, 2024 · 6 comments
Assignees
Labels
bug Something isn't working closed-for-staleness This issue was closed because it didn't receive updates ec2 response-requested This issue requires a response to continue

Comments

@prnr
Copy link

prnr commented Jan 2, 2024

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

@prnr prnr added bug Something isn't working needs-triage labels Jan 2, 2024
@RyanFitzSimmonsAK
Copy link

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!

@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this Jan 4, 2024
@RyanFitzSimmonsAK RyanFitzSimmonsAK added ec2 response-requested This issue requires a response to continue and removed needs-triage labels Jan 4, 2024
@prnr
Copy link
Author

prnr commented Jan 5, 2024

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 RyanFitzSimmonsAK added investigating and removed response-requested This issue requires a response to continue labels Jan 5, 2024
@RyanFitzSimmonsAK
Copy link

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

@RyanFitzSimmonsAK RyanFitzSimmonsAK transferred this issue from aws/aws-cli Jan 10, 2024
@prnr
Copy link
Author

prnr commented Jan 11, 2024

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
Copy link

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.

@RyanFitzSimmonsAK RyanFitzSimmonsAK added the response-requested This issue requires a response to continue label Jan 18, 2024
Copy link

github-actions bot commented Mar 1, 2024

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.

@github-actions github-actions bot added closing-soon This issue will be closed soon closed-for-staleness This issue was closed because it didn't receive updates and removed closing-soon This issue will be closed soon labels Mar 1, 2024
@github-actions github-actions bot closed this as completed Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working closed-for-staleness This issue was closed because it didn't receive updates ec2 response-requested This issue requires a response to continue
Projects
None yet
Development

No branches or pull requests

2 participants