Project

General

Profile

Actions

Bug #25937

closed

Subscription allocation on customer portal changes back to 6.3 from 6.4 after a manifest refresh from upgraded server

Added by Jonathon Turel almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1657719

Description of problem:

Upgraded satellite from 6.3 to 6.4 and then changed the type of the manifest allocation on the customer portal from the 6.3 to 6.4.
after the refresh of the manifest from the customer portal, type changes back to 6.3 again.

Version-Release number of selected component (if applicable):

Red Hat Satellite 6.4

How reproducible:

100%

Steps to Reproduce:

Same as mentioned in the description.

Actual results:

Type of allocation on portal gets changed to 6.3 after refresh of manifest from WebUI.

Expected results:

Type should remain 6.4

Additional info:

The suspected reason for such behavior might be that in 6.3 the communication with the customer portal was one way i.e we can only update and add the subscription from the portal and then refresh the manifest from the WEBUI to reflect the changes, but in satellite 6.4 we can add and update the manifest from the satellite webui Itself without accessing the customer portal.

Actions #1

Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7948 added
Actions #2

Updated by Jonathon Turel almost 6 years ago

  • Subject changed from Subscription allocation on customer portal changes back to 6.3 from 6.4 after a manifest refresh from upgraded server to Subscription allocation on customer portal changes back to 6.3 from 6.4 after a manifest refresh from upgraded server
  • Target version set to Katello 3.12.0
Actions #3

Updated by Jonathon Turel almost 6 years ago

  • Triaged changed from No to Yes
Actions #4

Updated by Anonymous almost 6 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF