When service level is set for content host, Satellite fails to assign new virutal subscription to it after vMotion

Solution Verified - Updated -

Issue

  • When there is conflict between service level set for content host and available virtual subscription's service level then content host does not get subscription. This happens mostly when virtual systems are migrated from one hypervisor to another, like using vMotion of VMware.

Environment

  • Red Hat Satellite 6.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.