MozillaSecurity / MozillaSecurity/FuzzManager
[EC2SpotManager] Spot requests can enter "failed" state based on capacity.
Open
Nobody has claimed this yet.
bug
ec2
spotmanager
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
The following error was seen in the server logs:
ec2spotmanager: [INFO] [laniakea]: Request sir-xxxxxxxx is capacity-not-available and failed.
ec2spotmanager: [ERROR] [ec2spotmanager]: Request sir-xxxxxxxx is capacity-not-available and failed.
ec2spotmanager: [ERROR] [ec2spotmanager]: Logging PoolStatusEntry(n): request failed (critical=True)
This results in a pool error, which prevents the pool from running.
Another capacity error which was returned as "cancelled" and correctly treated as a temporary problem.
ec2spotmanager: [INFO] [laniakea]: Request sir-xxxxxxxx is capacity-not-available and cancelled.
ec2spotmanager: [INFO] [ec2spotmanager]: Spot request sir-xxxxxxxx is cancelled
ec2spotmanager: [WARNING] [ec2spotmanager]: Blacklisted EC2Spot:blacklist:us-east-2:us-east-2c:c4.2xlarge for 12h
We should treat the first case like the second.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the EC2SpotManager handling for Spot requests that report capacity-not-available, then compare the failed and cancelled paths shown in the logs. Done means capacity-related failures are treated as temporary like cancellations, without producing a critical pool error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100