Bug 1766404

Summary: ostree not integrated - ostree transport not working
Product: [Fedora] Fedora Reporter: Mohan R <mohan43u>
Component: skopeoAssignee: Giuseppe Scrivano <gscrivan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: amurdaca, bbaude, dwalsh, gscrivan, jnovy, lsm5
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 15:09:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mohan R 2019-10-28 23:23:47 UTC
Description of problem:
skopeo says it supports ostree transport, but when tried, it failed with not supported message


Version-Release number of selected component (if applicable):
0.1.40-dev

How reproducible:
always

Steps to Reproduce:
1. run the following command to get the error message
   $ skopeo copy ostree:ostree.fedoraproject.org/fedora/rawhide/x86_64/silverblue dir:fedora

Actual results:
FATA[0000] Invalid source name ostree:ostree.fedoraproject.org/fedora/rawhide/x86_64/silverblue: The transport "ostree:" is not supported in this build 


Expected results:
skopeo should pull the remote ostree repo into dir:fedora

Additional info:
skopeo.spec uses "%gobuild" but ostree only gets integrated only through Makefile

Comment 1 Daniel Walsh 2019-10-29 12:52:53 UTC
I think we are dropping ostree support, and should update the documentation.  Is that correct Giuseppe?

Comment 2 Giuseppe Scrivano 2019-10-29 13:17:51 UTC
Skopeo may still need support for ostree, as it is used by system containers.  Are we ever going to update Skopeo on RHELAH?

If not, I can proceed to drop support for ostree both in Skopeo and containers/image.

Comment 3 Daniel Walsh 2019-10-29 13:30:24 UTC
No, skopeo will never be updated again in RHEL, other then CVE fixes.

Comment 4 Giuseppe Scrivano 2019-10-29 14:12:05 UTC
opened a PR here: https://github.com/containers/skopeo/pull/751

I've also opened one for containers/image: https://github.com/containers/image/pull/736

Comment 5 Ben Cotton 2020-02-11 17:50:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 6 Fedora Program Management 2021-04-29 15:59:22 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2021-05-25 15:09:45 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.