Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-3023

Implement Logic for Contract/Subscription Change Between Orgs

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • swatch-contracts
    • 5
    • False
    • Hide

      None

      Show
      None
    • False

      Description:  
      After discussions with the IT partner gateway team, we gathered the following information:

      • Subscription 15563275 was moved from org 18479847 to org 4364786.
      • Splunk logs confirm the transfer in IT gateway
         host=*gateway*-prod* index=rh_middleware "action=entitlement-transferred" 

        Logs:
        {{Publishing message: UmbMessage(body=EntitlementTransferredMessage
        Unknown macro: {cloudIdentifiers=AwsIdentifiersUnknown macro}
        , redHatSubscriptionNumber=null, action=entitlement-transferred, sourceRhAccountId=18479847, destinationRhAccountId=4364786}, headers={}, destination=VirtualTopic.services.partner-entitlement-gateway)

       

      • SWATCH side transfer logs were found using the query:  
         
         index=rh_rhsm namespace=rhsm-prod source="swatch-contracts" "ContractUMBMessageConsumer" | rex  field=message "sourceRhAccountId\":\"(?<sourceRhAccountId>\d+).*destinationRhAccountId\":\"(?<destinationRhAccountId>\d+)"| search "entitlement-transferred" | table _time _raw sourceRhAccountId destinationRhAccountId 

      Done:  
      1. Implement logic in swatch-contract to handle contract/subscription changes between organizations.
      2. Add IQE swatch-contract component test to cover this use case.

      3. Sync the orgs that had issues in prod

       

              Unassigned Unassigned
              karshah@redhat.com Kartik Shah
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: