Subscription validity is not updated in Ansible Automation Platform after applying future-dated subscription

Solution Verified - Updated -

Issue

  • According to the document below, starting in Ansible Tower 3.8.1(AAP 1.2), we can apply multiple subscriptions to a single installation by adding multiple subscriptions of the same type to a manifest file and uploading them.

    However, when this occurs, the Automation Controller GUI does not update the future dated Expiry Date on the license and only shows the Expiry Date of the current subscription and it looks like the updated manifest file has not been applied.

Environment

Ansible Tower >= 3.8.1
Ansible Automation Platform > = 1.2
Ansible Automation Platform > = 2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content