Bug 1597284
Summary: | Synced OSTREE version shows incorrect order on Red Hat Satellite server. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | sandeep mutkule <smutkule> |
Component: | Repositories | Assignee: | Michael Johnson <micjohns> |
Status: | CLOSED WONTFIX | QA Contact: | Peter Ondrejka <pondrejk> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.3.1 | CC: | micjohns, pcreech |
Target Milestone: | Released | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-12-18 21:25:40 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
sandeep mutkule
2018-07-02 13:23:42 UTC
I assume the following will give what you are looking for: ostree-branch list --order 'version' A couple of other sort examples: ostree-branch list --order 'version ASC' ostree-branch list --order 'name' Hello Brad, It works fine to sort the OSTREE versions in order, but we expect that this command should list all versions in order by default. There should not be any need to run "ostree-branch list --order 'version'" separately to get the sorted order all the versions. Created redmine issue https://projects.theforeman.org/issues/24275 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24275 has been resolved. Checked on Satellite 6.5 snap 1, verification using rh atomic repos is currently blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1645017 When using custom Fedora ostree repo (with a bit different numbering scheme), it seems that the ordering does not expect minor version numbers with more than one digit, therefore the ordering looks like: 1353 | fedora/27/x86_64/atomic-host | 27.120 1228 | fedora/27/x86_64/testing/atomic-host | 27.120 1050 | fedora/27/x86_64/updates/atomic-host | 27.120 2038 | fedora/27/x86_64/updates/atomic-host | 27.12 294 | fedora/27/x86_64/atomic-host | 27.12 94 | fedora/27/x86_64/testing/atomic-host | 27.12 2356 | fedora/27/aarch64/testing/atomic-host | 27.119 2317 | fedora/27/x86_64/atomic-host | 27.119 2223 | fedora/27/ppc64le/atomic-host | 27.119 This applies to both the default output and with ostree-branch list --order 'version' Upstream bug assigned to micjohns After further research with the Atomic and Pulp teams, it has been determined that neither version or version_dates are logical ways to sort the OSTree branches. Versions are an arbitrary string and version_date is the date that the OSTree branch was created in Pulp. OSTree branches are more like git repositories and rely on a parent -> child relationship that we do not currently have access to from Pulp. There are further discussions on an RFE from pulp to pull in the information from libostree for the date of the commit. We will revisit this bug at a later date, but will not be fixing in this capacity. |