• Describe the issue
  I am forwarding an issue reported to me by an IBM developer from OCP Virt team.

The background:
I am from the Openshift Virtualisation (OCP Virt) enablement team for s390x and we work with upstream Kubevirt (https://github.com/kubevirt) projects.
Under kubevirt (https://github.com/kubevirt), we have a synchronization tool called medius (https://github.com/kubevirt/containerdisks) that looks into metadata info of Fedora releases from https://fedoraproject.org/releases.json and creates & pushes the image for it in http://quay.io/kubevirt.

The issue:
recently, we stumbled upon a blocker where there is a mismatch in release information for Fedora s390x between

• The metadata in https://fedoraproject.org/releases.json (there is no s390x info) and what is available for download on Fedora website https://fedoraproject.org/server/download (there is s390x downloadable)
• This does not happen for x86 or aarch64

Since we have a tight dependency to get this resolved for feature freeze in OCP Virt, I would like to know from you the possible fix to this.
Please can you have a look into it?

With regards,
Lakshmi Ravichandran

• When do you need this? (YYYY/MM/DD)
  ASAP

• When is this no longer needed or useful? (YYYY/MM/DD)
  N/A

• If we cannot complete your request, what is the impact?
  blocked development of OCP Virt for s390x

• Additional information
  The JSON file looks incomplete/wrong to me, because it lists only a single artifact for ppc64le (and none for s390x).