Project

Profile

Help

Issue #7834

closed

Updated deprecation status is not included in sync

Added by awcrosby over 3 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
3. High
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 86
Quarter:
Q4-2020

Description

This was seen on testing with galaxy_ng: In 4.2.0 GA, updated deprecation status is not sync’d from cloud to on-prem hub

Steps to recreate:

  1. Ensure the synctest repo in ci.cloud.redhat.com has some collections deprecated, others not
  2. For the first time, sync the repo from cloud to on-prem hub
  3. Confirm deprecation status is as expected on each collection in on-prem hub
  4. Change deprecation status on one of the synced collections on cloud
  5. Sync again
  6. Observe that the collection on-prem does not have the deprecation status changed as expected

Also available in: Atom PDF