We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
AVAILABLE
OUT_OF_HOST_CAPACITY
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" } }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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 isOUT_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.
The text was updated successfully, but these errors were encountered: