Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-29947

Unable to add future dated subscriptions from the Satellite WebUI

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • rubygem-katello-4.14.0.5-1
    • 0
    • Phoenix - Subscriptions
    • Sprint 143
    • Important
    • To Do
    • Yes

      Description of problem:

      While navigating to "Satellite WebUI -> Content -> Subscriptions -> Add Subscriptions" button, the Future Dated Subscriptions are not populated and cannot be added. 

      The list of the available subscriptions to be added only shows the ACTIVE subscriptions, and not the future-dated subscriptions

       

      Behavior:

      The management of subscriptions has been deprecated in the old RHN portal and should now be done through console.redhat.com and the Satellite GUI directly. However, it appears that the Satellite GUI is not fully functional at the moment, particularly when adding subscriptions from an existing manifest.

      Currently, the Satellite interface only displays active subscriptions and does not show future-dated ones. While Satellite user can see the subscriptions that are expiring soon, but the new ones that will take effect after that do not appear.

      It's not possible to modify a manifest directly from console.redhat.com to add future subscriptions—this must be done through the Satellite GUI.

      Luckily, the old portal still works for adding future-dated subscriptions to an existing manifest. After doing so and refreshing in Satellite, the future subscriptions do appear. However, even after this process, those subscriptions still don't show up on the /subscriptions/add page.

       

      IMPACT : As per customer " As for back to the Future Dated subs cannot be assigned to Hosts  but not being able to assign them to an Organization puts the Organization in bad shape when the "old" active subs expires: Red Hat content is then unaccessible because the new subs are not yet added. Same goes when being in a "non-SCA" mode: the AK cannot yet have the new subs assigned, so when the old subs expires, the AK is voided of all Subs, making the host unable to get any content.

              rhn-engineering-jlenz Jeremy Lenz
              rhn-support-amiagarw Amit Agarwal
              Vijaykumar Sawant Vijaykumar Sawant
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: