releng

Clone

#6975 pdc: map our releases to product versions
Closed: Fixed 5 years ago Opened 6 years ago by ralph.

Closed: Fixed
Reopen Issue

All of our product-versions say they are inactive.

According to upstream, this is because they are not mapped to any active releases.

We do have lots of active releases.. but they are not mapped to the product-versions.

See the API response here: https://pdc.fedoraproject.org/rest_api/v1/releases/ the product_version is null for all of them. If we set those to the appropriate product-version, the 'active' field on the products should flip.

Metadata Update from @ralph:
- Issue assigned to mohanboddu
6 years ago

I updated the releases to product-versions mapping. Following are observations/questions I discovered:

  1. https://pdc.fedoraproject.org/rest_api/v1/releases/facd-Rawhide/ - what is it tracking?
  2. Difference between https://pdc.fedoraproject.org/rest_api/v1/releases/epel-7-updates/ and https://pdc.fedoraproject.org/rest_api/v1/releases/fedora-epel7-updates/? And based on my observation https://pdc.fedoraproject.org/rest_api/v1/releases/fedora-epel7-updates/ is setup wrong.
  3. We didn't have any successful Fedora 26 Cloud composes(I am looking into it). I assume once we have a successful compose, it will be brought into PDC and once it is in PDC I will update its product version.

@mohanboddu reports this has been fixed. Closing but need this functionality in PDC replacement.

Metadata Update from @syeghiay:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
5 years ago

Login to comment on this ticket.

Metadata
None
None
None
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.