Red Hat Compliance

Poojaganguly
Kilo Explorer

6 hours ago

I am getting missing cloud license type for red hat linux server and its showing non compliant no matter what i do.

Any idea how to resolve it to improve the compliance?

0 Helpfuls
  • 46 Views
1 REPLY 1

Matthew_13
Mega Sage

51m ago

Hi Buddy,

This usually isn’t anything wrong with the Red Hat server itself. It happens because ServiceNow can’t tell how the RHEL license is provided in the cloud, so it automatically marks the server as non-compliant.

When you see “Missing cloud license type”, it means the Cloud license type field on the Linux server CI is empty or not set correctly. Until that’s populated, SAM will always show the server as non-compliant, no matter what else you configure.

What I say to check:

  • Open the Linux Server CI and set Cloud license type to the correct value (for example BYOS or Cloud provider / Pay-as-you-go).

  • Make sure the server is correctly linked to its cloud account (AWS, Azure, or GCP). If the cloud details are missing, SAM can’t determine licensing.

  • If the server was imported or discovered generically, re-run Discovery or manually fix the missing cloud metadata.

  • If you’re using BYOS, confirm your Red Hat subscriptions are modeled correctly in SAM. If it’s marketplace licensing, the cloud license type must reflect that.

Once the Cloud license type is set and matches how the server is actually licensed, compliance usually flips to green after the next reconciliation.

 

@Poojaganguly - Please mark Accepted Solution and Thumbs Up if you found helpful

0 Helpfuls