fedora-infrastructure

#7127 Builder instances stuck in "deleting" phase in Copr tenant
Closed: Fixed Opened by clime.

Closed: Fixed
Reopen Issue
  • Describe what you need us to do:
    Remove the instances in the "Deleting" state in copr tenant. They are permanently stuck in that state and they are taking place for new builders, which means Copr is only able to run 10 builds at the same time
    because we are blocked on RAM limit and VCPU limit:

VCPUs
Used 194 of 200

RAM
Used 485.0GB of 488.3GB

  • When do you need this? (YYYY/MM/DD)
    Ideally today but any time soon will help

  • When is this no longer needed or useful? (YYYY/MM/DD)
    always useful

  • If we cannot complete your request, what is the impact?
    People will complain about Copr being slow.

You can see the problem here: https://copr.fedorainfracloud.org/status/stats/

ok. I have cleaned all this up...

currently it has 24 builders and is slowly spinning up more and current usage shows:

Instances
Used 24 of 150
VCPUs
Used 48 of 200

Let us know if you need anything further.

:cyclone:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.