Skip to main content

Oracle Cloud Troubleshooting

This guide lists common symptoms, likely causes, and actions you can take before escalating to Cloudaware Support.

Authentication or Key Errors​

Symptoms

  • Tenancy status is red in Cloudaware.
  • Error messages reference invalid API keys, fingerprint mismatch, or authentication failures.

Checks

  • In OCI:
    • Confirm that the user still exists and the API key corresponding to the Cloudaware public key is present.
    • Verify that the fingerprint shown in OCI matches the fingerprint configured in Cloudaware.
  • In Cloudaware:
    • Confirm that the selected key pair, tenancy OCID, user OCID, fingerprint, and region match the OCI configuration.

If you rotate keys, regenerate the key pair in Cloudaware (or upload a new key in OCI) and update the tenancy configuration accordingly.

Policy or Permission Issues​

Symptoms

  • Tenancy may authenticate successfully, but few or no resources appear in CMDB.
  • Error messages or logs indicate access denied for specific OCI services or compartments.

Checks

  • Review the read‑only policies for the Cloudaware group:
    • Ensure read all-resources and read compartments (or equivalent compartment‑specific statements) are present.
    • Confirm that the group includes the Cloudaware user.
  • If you scoped policies to compartments:
    • Verify that those compartments actually contain the resources you expect to see.

Adjust policies and allow time for the next discovery cycle.

Region or Tenancy Coverage Issues​

Symptoms

  • Only some regions or compartments show resources, even though policies should allow more.

Checks

  • Verify region subscriptions for the tenancy and ensure Cloudaware is configured for the appropriate default region.
  • Confirm that policies are written at the correct scope (tenancy vs. compartment) and apply across the targeted regions.

Still Stuck?​

If issues persist after these checks, collect the following details:

  • Screenshots of the OCI user, API key, and policies.
  • Tenancy OCID, user OCID, and example resource identifiers that are missing.
  • Error text or screenshots from Cloudaware.

Contact Cloudaware Support at support@cloudaware.com. Providing precise details greatly shortens time‑to‑resolution.