Web Console Problems

This section lists problems that you might encounter while using the Compute Classic web console.

Can’t access the web console

Description

When I try to log in to the web console, the following error message is displayed:

You are not authorized to access the Compute Classic (0706_043942.887).\
If the problem persists, contact Oracle Support.

Solution

This error indicates that you are not assigned any Compute Classic role. See About Compute Classic Roles.

Ask your service administrator to assign the appropriate roles to you in Oracle Cloud Infrastructure Classic Console. See Modifying User Roles in Managing and Monitoring Oracle Cloud.

Can’t create, update, or delete objects

Description

When I try to create, update, or delete any object, an error message similar to the following is displayed:

Unable to create security rule. [jack.jones@example.com_0706_045758.332] :
 User /Compute-acme/jack.jones@example.com is not permitted to perform "secrule.add" on
 secrule:/Compute-acme/jack.jones@example.com/mysecrule  

Unable to add IP reservation. [jack.jones@example.com_0706_050517.177] :
 User /Compute-acme/jack.jones@example.com is not permitted to perform "ipreservation.add" on
 ipreservation:/Compute-acme/jack.jones@example.com/myipres  

Unable to update SSH key "mykey". [jack.jones@example.com_0706_052418.475] :
 User /Compute-acme/jack.jones@example.com is not permitted to perform "sshkey.update" on
 sshkey:/Compute-acme/jack.jones@example.com/mykey  

Unable to delete SSH key "mykey". [jack.jones@example.com_0706_052437.025] -
 User /Compute-acme/jack.jones@example.com is not permitted to perform "sshkey.delete" on
 sshkey:/Compute-acme/jack.jones@example.com/mykey  

Unable to detach storage volume "myvol1" from this instance. [jack.jones@example.com_0706_052512.984] -
 User /Compute-acme/jack.jones@example.com is not permitted to perform "attachment.delete" on
 storage/attachment:/Compute-acme/jack.jones@example.com/vm-1/3b515fae.../...55a31eaee6b5

Solution

This error indicates that you’re not authorized to create, update, or delete resources in Compute Classic. Ask your service administrator to assign the Compute_Operations role to you in Oracle Cloud Infrastructure Classic Console. See Modifying User Roles in Managing and Monitoring Oracle Cloud.

Can’t upload an orchestration

Description

When I try to upload my orchestration file, I get the following error: “Unable to create an orchestration from the JSON file.”

Solution

This error indicates that there are errors in the syntax of your orchestration JSON file. Open the JSON file in a text editor to identify and fix the problems. You should also validate your JSON file. You can do this by using a third-party tool, such as JSONLint, or any other validation tool of your choice.

Note:

Oracle doesn’t support or endorse any third-party JSON-validation tool.

My orchestration hasn’t created any instances

Description

I’ve uploaded my orchestration file but I don’t see my instances. What should I do?

Solution

After uploading your orchestration, the status of your orchestration is automatically set to Stopped. To create the resources defined in your orchestration, start your orchestration. If you have created orchestration v2, see Starting an Orchestration v2. If you have created orchestration v1, see Starting an Orchestration v1.

Error while starting an orchestration: Specify imagelist or bootorder

Description

I’ve uploaded my orchestration, but when I start it, the following error occurs:

Specify either an ImageList or boot_order and StorageVolume.

Solution

This error indicates that your orchestration doesn’t specify either an image or a bootable storage volume for your instance.

To set up the instance to boot from a persistent disk, you must attach a bootable storage volume by using the storage_attachment instance attribute, and then specify the index number of the attached storage volume as the boot disk by using the boot_order instance attribute.

{
  "objects": [
    {
      "instances": [
        {
          "boot_order": [
            1
          ],
          "storage_attachments": [
            {
              "index": 1,
              "volume": "/Compute-acme/joe/bootable-vol1"
            }
          ]
        }
      ]
    }
  ]
}

To set up the instance to boot from a nonpersistent disk, specify the image that you want to use by using the imagelist attribute.

{
  "objects": [
    {
      "instances": [
        {
          "imagelist": "/oracle/public/OL_6.7_UEKR4_x86_64"
        }
      ]
    }
  ]
}

Note:

If you specify both boot_order and imagelist for an instance in an orchestration, the imagelist attribute is ignored and the instance is booted using the bootable storage volume specified by the boot_order attribute. See Orchestration v1 Attributes for instances.

Can’t attach a storage volume to an instance

Description

When I try to attach my storage volume to an instance, the following error occurs:

APIConflictError: Attachment index 1 is already in use on instance /Compute-acmecorp/acmeadmin/dev2/6073c806-f7da-47eb-9678-6e618931b29a

Solution

The index number that you’re trying to assign to this storage volume is already used for another storage volume. Select a different index number and try again.

Note:

The disk number that you specify here determines the device name. The disk attached at index 1 is named /dev/xvdb, the disk at index 2 is /dev/xvdc, the disk at index 3 is /dev/xvdd, and so on.

To view the set of index numbers that are already in use for an instance using CLI, use the opc compute storage-attachment list command.

For help with that command, run the command with the -h option. For the instructions to install the CLI client, see Preparing to Use the Compute Classic CLI in CLI Reference for Oracle Cloud Infrastructure Compute Classic.

Can't detach a storage volume from an instance

Description

I've attached three storage volumes to my instance. Now I want to delete the instance. So I started to detach the storage volumes. I detached two of the storage volumes, but can’t detach the third one.

Solution

You can detach storage volumes that were attached to an instance after the instance was created. You can’t detach storage volumes that were attached during instance creation.

Can't delete a storage volume

Description

I want to delete a storage volume that I no longer need, but the web console doesn’t show the delete option for the storage volume.

Solution

You can't delete a storage volume if it’s attached to an instance. To find out whether a storage volume is attached to an instance, view the storage volume information in the web console. Click the Storage tab, scroll down to the storage volume that you want to delete, and check the displayed details. If the storage volume that you want to delete is attached to an instance, then you must detach it first. See Detaching a Storage Volume from an Instance.

You can also use CLI commands to find out if a storage volumes is attached to an instance. Use the opc compute storage-attachment list CLI command with the --storage_volume_name option to view the details of storage attachments for a specified storage volume. Then use the opc compute storage-attachment delete CLI command to detach a storage volume from an instance.

For help with these commands, run each command with the -h option. For the instructions to install the CLI client, see Preparing to Use the Compute Classic CLI in CLI Reference for Oracle Cloud Infrastructure Compute Classic.

Also, you can’t delete a storage volume if you’ve created any colocated snapshots of the storage volume. See Backing Up and Restoring Storage Volumes Using Snapshots.

Can't delete a storage volume snapshot

Description

I want to delete a storage snapshot that I no longer need, but the Delete option for that snapshot is disabled in the web console.

Solution

You can't delete a colocated storage volume snapshot if you’ve created a clone from that snapshot. The Storage Snapshots page shows you information about each colocated storage snapshot including storage volumes cloned from a snapshot, if any. You can make a note of the clones and then view them on the Storage Volumes page. To delete a colocated snapshot, first delete all the clones created from the storage snapshot. See Deleting a Storage Volume.

Can’t remove an IP address from an instance

Description

I associated a temporary IP address with my instance while creating the instance using the Create Instance wizard. Now I want to remove the temporary IP address and use an IP address reservation instead. How can I remove the temporary IP address from my instance? The Remove Instance option in the web console is disabled.

Solution

You can’t remove a temporary IP address from an instance. You can only remove a persistent IP address. If you created an instance with an autogenerated IP address or if you changed the status of the IP address associated with an instance to temporary, then to remove that IP address from the instance, first update it to change its status to permanent. See Updating an IP Reservation.

Can’t delete a security application

Description

When I tried to delete the security application /oracle/public/snmp-trap-udp, the following error message was displayed:

APIUnauthorizedError: User /Compute-acmecorp/acmeadmin is not permitted to perform "secapplication.delete" on secapplication: /oracle/public/snmp-trap-udp

Solution

Compute Classic has a set of predefined security applications. The names of these security applications start with /oracle/public container. You can’t delete these predefined security applications.

Tip:

To view a list of predefined security applications from the web console, click the Network tab and then the Security Applications tab in the left pane. The list of available security applications is displayed. In the search field, enter /oracle/public, and click . A list of all the predefined security applications is displayed.

To get a list of all the predefined security applications from the CLI, use the opc compute sec-application list command and specify /oracle/public as the container. For help with that command, run the command with the -h option. For the instructions to install the CLI client, see Preparing to Use the Compute Classic CLI in CLI Reference for Oracle Cloud Infrastructure Compute Classic.

Can’t delete a private image

Description

How can I delete a private image listed on the Images page? The Delete option in the web console isn’t available.

Solution

You can’t delete a private image if it is used in an orchestration. To delete a private image, ensure that you’ve stopped and deleted any instance orchestrations that used that private image.