Re: Untagged resources in AWS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Apr 01, 2024 at 09:45:18PM +0200, Miroslav Suchý wrote:
> This is without AMIs and Snapshots that still produce looong list.
> 
> Region: us-west-1
> Volumes - [id name (attached to instance, owner)]:
>  * vol-0d7702fbe7ab94c6f N/A (famna.fedorainfracloud.org, N/A)

Oops. Thiw was me. I thought it was all tagged. Fixed.

> Region: us-west-2
> Instances: (name, id, owner)
>  * openscanhub-test (i-0c32e3d4eff4bf1a4, N/A)
> Volumes - [id name (attached to instance, owner)]:
>  * vol-0e9ad438b3cf1e5b9 N/A (openscanhub-test, N/A)

This is the new openscanhub app.

...snip...

I think all the testing farm ones might be because they are able to do
spot images now and need to make sure those get tagged right? Not sure. 

kevin

Attachment: signature.asc
Description: PGP signature

--
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux