You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GraalVM is probably fixed but the setup errors out with: @paulparkinson FYI
andy_tael@cloudshell:txeventq-kafka (us-ashburn-1)$ source $LAB_HOME/cloud-setup/setup.sh
Please enter your OCI user's OCID: ocid1.user.oc1..aaaaaaaalxt3txplik4yybwijfixdc4cym4sgy5c4ysenrtnbjan3kfkfs5a
Resources will be created in a new compartment named txeventqlab
Waiting for the compartment to become ACTIVE
Do you want to use Always Free Autonomous Database Instance? (y/N) N
ATP_LIMIT_CHECK completed
Executing terraform.sh in the background
ServiceError:
{
"client_version": "Oracle-PythonSDK/2.126.1, Oracle-PythonCLI/3.40.1",
"code": "CompartmentIdNotFound",
"logging_tips": "Please run the OCI CLI command using --debug flag to find more debug information.",
"message": "Either the Tenant with TenantID 'ocid1.compartment.oc1..aaaaaaaayq55l2rsmlzps3w4bz6qycf4jg3l4tuwqsiudlleeawgz5gmhn6q' does not exist or you are not authorized to access it",
"opc-request-id": "iad-1:83YWGVsFHXMTiVAvRSivgFubemnnUF_MNfxUUMl9VdQBCWXx06Amc60a81tEVhOh",
"operation_name": "get_namespace",
"request_endpoint": "GET https://objectstorage.us-ashburn-1.oraclecloud.com/n",
"status": 404,
"target_service": "object_storage",
"timestamp": "2024-05-10T18:42:55.994450+00:00",
"troubleshooting_tips": "See [https://docs.oracle.com/iaas/Content/API/References/apierrors.htm] for more information about resolving this error. If you are unable to resolve this issue, run this CLI command with --debug option and contact Oracle support and provide them the full error message."
}
Turns out Cloud Shell now does default to ARM chips, which the graalvm-install.sh assumes as AMD.
It goes into infinite loop, unable to execute gu.
LL is https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/run-workshop?p210_wid=993&p210_wec=&session=112162987880028
The text was updated successfully, but these errors were encountered: