Issue #4665
closed
Field base_version set as none even when repo has multiple versions
Description
Once a repository has more than one version, the second one is expected to have the field `base_version` linked to the first version.
See docs: https://docs.pulpproject.org/en/3.0/nightly/restapi.html#operation/repositories_versions_read
[{'_created': '2018-12-21T01:42:00.315279Z',
'_href': '/pulp/api/v3/repositories/3861f724-072f-4cff-8b49-eded158a34c6/versions/2/',
'base_version': None,
'content_summary': {'added': {},
'present': {'file.file': {'count': 3,
'href': '/pulp/api/v3/content/file/files/?repository_version=/pulp/api/v3/repositories/3861f724-072f-4cff-8b49-eded158a34c6/versions/2/'}},
'removed': {}},
'number': 2},
{'_created': '2018-12-21T01:39:58.340692Z',
'_href': '/pulp/api/v3/repositories/3861f724-072f-4cff-8b49-eded158a34c6/versions/1/',
'base_version': None,
'content_summary': {'added': {'file.file': {'count': 3,
'href': '/pulp/api/v3/content/file/files/?repository_version_added=/pulp/api/v3/repositories/3861f724-072f-4cff-8b49-eded158a34c6/versions/1/'}},
'present': {'file.file': {'count': 3,
'href': '/pulp/api/v3/content/file/files/?repository_version=/pulp/api/v3/repositories/3861f724-072f-4cff-8b49-eded158a34c6/versions/1/'}},
'removed': {}},
'number': 1}]
repo versions were created using 2 syncs. first a lazy sync, and second a immediate sync.
Pulp 3 installation from source. April/09
Related issues
Updated by kersom about 5 years ago
- Subject changed from Field base_version set as none even when repo has multipe versions to Field base_version set as none even when repo has multiple versions
Updated by bmbouter about 5 years ago
I think I agree with you. It would be sweet if base_version was always set if it's version > 1
Updated by amacdona@redhat.com about 5 years ago
- Sprint/Milestone set to 3.0.0
- Triaged changed from No to Yes
Updated by kersom about 5 years ago
- Related to Story #4680: As a user I have lifecycle docs in pulpcore workflows added
Updated by daviddavis over 4 years ago
Currently, the field base_version is only set if it's explicitly set in the creation of the new repo version. If we always set it, then we lose the historical information about whether the base_version was specified or not when the repo version was created.
Updated by daviddavis over 4 years ago
- Status changed from NEW to CLOSED - WONTFIX
Discussed with bmbouter and bmbouter who agree that the field is for historic purposes.
.