AWS - strange error: volume in use, but is not attached
When cleaning the old volumes I find strange error This volume: https://ap-southeast-1.console.aws.amazon.com/ec2/home?region=ap-southeast-1#VolumeDetails:volumeId=vol-495d4a40 i.e. vol-495d4a40 in ap-southeast-1 cannot be deleted, because is "in-use". And I can only "detach" or "force detach", but there is no attached instances listed. In this region are 3 instances: proxy38.fedoraproject.org, proxy30.fedoraproject.org and mref1.apse1.stream.centos.org but none of them list this volume as attached. BTW, this volume is already snapshoted as snap-017a9145cd8099a06 so it can be safely deleted. Does somebody ever experienced this kind of error? Any ideas? If I get no suggestions by end of the week, I will try to detach it (not sure from where), and if it fails (I kind of expect it) I will raise a support ticket. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS - strange error: volume in use, but is not attached
On Wed, Sep 13, 2023 at 09:22:27AM +0200, Miroslav Suchý wrote: > When cleaning the old volumes I find strange error > > This volume: > > https://ap-southeast-1.console.aws.amazon.com/ec2/home?region=ap-southeast-1#VolumeDetails:volumeId=vol-495d4a40 > > i.e. vol-495d4a40 in ap-southeast-1 > > cannot be deleted, because is "in-use". And I can only "detach" or "force > detach", but there is no attached instances listed. > > In this region are 3 instances: proxy38.fedoraproject.org, > proxy30.fedoraproject.org and mref1.apse1.stream.centos.org but none of them > list this volume as attached. > > BTW, this volume is already snapshoted as snap-017a9145cd8099a06 so it can be > safely deleted. > > Does somebody ever experienced this kind of error? Any ideas? > > If I get no suggestions by end of the week, I will try to detach it (not > sure from where), and if it fails (I kind of expect it) I will raise a > support ticket. Yeah, I never have seen that before... very odd. I would try the detach and support ticket. kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: AWS - strange error: volume in use, but is not attached
Dne 13. 09. 23 v 20:39 Kevin Fenzi napsal(a): https://ap-southeast-1.console.aws.amazon.com/ec2/home?region=ap-southeast-1#VolumeDetails:volumeId=vol-495d4a40 i.e. vol-495d4a40 in ap-southeast-1 cannot be deleted, because is "in-use". And I can only "detach" or "force detach", but there is no attached instances listed. In this region are 3 instances: proxy38.fedoraproject.org, proxy30.fedoraproject.org and mref1.apse1.stream.centos.org but none of them list this volume as attached. BTW, this volume is already snapshoted as snap-017a9145cd8099a06 so it can be safely deleted. Does somebody ever experienced this kind of error? Any ideas? If I get no suggestions by end of the week, I will try to detach it (not sure from where), and if it fails (I kind of expect it) I will raise a support ticket. Yeah, I never have seen that before... very odd. I would try the detach and support ticket. I tried detach. It is working for hours. Canceled. Force detach. Has been working whole night. Nothing. I found similar issue in KBase. No solution. https://repost.aws/questions/QUS5_ZMbZUS7mQ7Zo0EzniGQ/an-ebs-volume-i-have-won-t-detach-or-force-detach-it-s-not-attached-to-anything I cannot open support ticket because our plan is Basic and it does not allow opening support case. Any idea? David (cc)? -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
