Failed to execute concurrent subscription-manager register commands

Solution In Progress - Updated -

Issue

Deploying or upgrading multiple servers can lead to a situation where concurrent subscription-manager register actions are executed.

This is breaks two scenarios:
- upgrading RHEL6.5 hosts to the latest build, because the clients need a subscription-manager re-register to make sure that the latest repository configuration from Satellite 6 is retrieved. Doing concurrent upgrades on multiple hosts will give timeout errors on many hosts. A sequential action will take a lot of time much time.
- unattended automated testing from a CI environment where test servers are kickstarted and re-registered without human intervention.

Environment

  • Red Hat Satellite or Proxy 6.0

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.