Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-26493 Adding never synced repository in newly created Content View and publishing it shows "Updates available: Repositories and/or filters have changed."
  3. SAT-26628

[QE] Adding never synced repository in newly created Content View and publishing it shows "Updates available: Repositories and/or filters have changed."

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Content Views
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Phoenix - Content
    • Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141

      Description of problem:

      Adding never synced repository in newly created Content View and publishing it shows "Updates available: Repositories and/or filters have changed."

       

      How reproducible:

       

      Is this issue a regression from an earlier version:

       

      Steps to Reproduce:

      1. Create a new Content View

      2. Add never synced repository in the Content View

      3. Publish the Content View 

       

      Actual behavior:
      [Describe the issue in detail, including what is happening and where]

      Satellite WebUI --> Content --> Life Cycle --> Content View --> Select Content View --> Versions display "Updates available: Repositories and/or filters have changed."

       

      Expected behavior:
      [Describe what should be happening instead]

      Satellite WebUI --> Content --> Life Cycle --> Content View --> Select Content View --> Versions should not show any "Updates available: Repositories and/or filters have changed."

       

      Business Impact / Additional info:

      attached screenshots.

      QE Tracker for https://issues.redhat.com/browse/SAT-26493

              vsedmik@redhat.com Vladimír Sedmík
              satellite-jira-automation@redhat.com Satellite Jira-Automation
              Vladimír Sedmík Vladimír Sedmík
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: