oci compute capacity report is not correct in which ad has status AVAILABLE
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
When I run an availability report on my ADs I seem to be getting incorrect information.
It reports that US-CHICAGO-1-AD-3 is AVAILABLE and US-CHICAGO-1-AD-2 is OUT_OF_HOST_CAPACITY, but the reverse is actually true.
When creating instances of the same shape and shape-availabilities I can create instances in US-CHICAGO-1-AD-2 but not in US-CHICAGO-1-AD-3.
Below are the commands and results that show that the tool is reporting incorrect availability.
oci compute compute-capacity-report create --availability-domain QrSF:US-CHICAGO-1-AD-3 --compartment-id \
redacted \
--shape-availabilities '[{\"instanceShape\":\"VM.Standard.A1.Flex\",\"instanceShapeConfig\":{\"memoryInGBs\":6,\"ocpus\":1}}]'
{
"data": {
"availability-domain": "QrSF:US-CHICAGO-1-AD-3",
"compartment-id": "redacted",
"shape-availabilities": [
{
"availability-status": "AVAILABLE",
"available-count": null,
"fault-domain": null,
"instance-shape": "VM.Standard.A1.Flex",
"instance-shape-config": {
"memory-in-gbs": 6.0,
"nvmes": null,
"ocpus": 1.0
}
}
],
"time-created": "2024-02-05T20:38:50.116000+00:00"
}
oci compute compute-capacity-report create --availability-domain QrSF:US-CHICAGO-1-AD-2 \
--compartment-id redacted --shape-availabilities \'[{\"instanceShape\":\"VM.Standard.A1.Flex\",\"instanceShapeConfig\":{\"memoryInGBs\":6,\"ocpus\":1}}]'
{
"data": {
"availability-domain": "QrSF:US-CHICAGO-1-AD-2",
"compartment-id": "redacted",
"shape-availabilities": [
{
"availability-status": "OUT_OF_HOST_CAPACITY",
"available-count": null,
"fault-domain": null,
"instance-shape": "VM.Standard.A1.Flex",
"instance-shape-config": {
"memory-in-gbs": 6.0,
"nvmes": null,
"ocpus": 1.0
}
}
],
"time-created": "2024-02-05T20:39:12.799000+00:00"
}
}
Contributor guide
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
Start by rerunning the two oci compute compute-capacity-report create commands for US-CHICAGO-1-AD-2 and AD-3 with the reported shape configuration, then compare the results with actual instance-creation behavior. Done means the availability report consistently identifies which availability domain can host the requested VM.Standard.A1.Flex shape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100