Oracle Cloud Infrastructure Documentation

'No Profile Available' When Enabling the OS Management Hub Plugin

When selecting a profile for registering an OCI instance, you might see 'No Profile Available' if no profiles in the selected compartment match the instance's OS version and architecture, or if OS Management Hub is unable to determine the OS version of the instance.

No matching profile in compartment

Within the selected compartment, there must be a profile that matches the OS version and architecture of the instance.

  1. Verify there's a profile that matches the OS version and architecture of the instance you're trying to register. If not, create a profile.
  2. When enabling the plugin, verify you've selected the correct compartment and select a matching profile.
  3. If you still see 'No Profile Available', OS Management Hub might be unable to identify the OS version and architecture of the instance. Proceed to the next section.

OS Management Hub can't identify the instance's OS version

OS Management Hub might be unable to determine the OS version and architecture when:

  • Using a custom image.
  • Using an instance that was previously upgraded with Leapp.

As a workaround, you can use an 'incompatible' profile to enable the plugin. This allows the instance to start communicating with OS Management Hub so that the service can determine the correct OS version and architecture. Then, within OS Management Hub, you can select the correct profile to register the instance.

Workaround:

  1. Identify or create a profile to temporarily use for registration.
    • For custom images, use an Oracle Linux 8 x86_64 profile. If OS Management Hub can't identify an instance, it defaults to Oracle Linux 8 and x86_64.
    • For Leapp upgraded images, use a profile with the OS version originally used to create the instance, not the upgraded OS version. For example, if you upgraded to Oracle Linux 9 from Oracle Linux 8, use an Oracle Linux 8 profile.
  2. Register the instance selecting the profile you just identified.
  3. Open the navigation menu and click Observability & Management. Under OS Management Hub, click Instances.

    After a few minutes, the instance appears in a 'Registration failed' state because the registration profile doesn't match the instance's OS version.

  4. Click the name of the instance.
  5. Click Set profile, and then select the compartment and profile to use for registration.

    Use a profile that matches the current OS version and architecture of the instance.

  6. Click Set.
    Note

    It can take up to 10 minutes for an instance to register with the service.