Feature #17427
closed
OSTree Sync pulls only the latest version
Added by Brad Buckingham about 8 years ago.
Updated over 6 years ago.
Description
NOTE: this issue will require a pulp change.
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1369892
As of 6.2 OSTree sync only pulls the latest branch, it does not sync the full history. This affects customers wanting to deploy to a specific version of the host.
Steps:
1) Sat with ostree enabled
2) manifest with ostree + enable atomic repo or create product + repo with one of the upstream repos.
3) Sync
Actual
Notice only the latest version (7.2.6) as of now shows up.
Expected
All versions traversable via history,
- Tracker changed from Bug to Feature
- Subject changed from OSTree Sync pulls only the latest version
to OSTree Sync pulls only the latest version
- Translation missing: en.field_release set to 188
- Translation missing: en.field_release changed from 188 to 114
- Target version set to 154
- Blocked by Bug #18076: ostree 'Depth' parameter support needed in runcible added
- Target version changed from 154 to 163
- Target version changed from 163 to 161
- Status changed from New to Ready For Testing
- Translation missing: en.field_release deleted (
114)
- Pull request https://github.com/Katello/katello/pull/6637 added
- Priority changed from High to Normal
- Translation missing: en.field_release set to 211
- Blocked by Bug #18993: ostree 'Depth' parameter support For Distributor in runcible added
- Translation missing: en.field_release changed from 211 to 114
- Translation missing: en.field_release deleted (
114)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 211
Also available in: Atom
PDF