Issue #4252
closedmodules.yaml file is generated on repository with no modularity information
Description
It seems that syncing and publishing a repository without any modularity info, still results in a modules.yaml being generated.
See: https://projects.theforeman.org/issues/25529 for more information
Related issues
Updated by CodeHeeler almost 6 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 46
- Tags Easy Fix added
Updated by dalley almost 6 years ago
- Related to Issue #4268: Publishing a repo in-place multiple times creates multiple modules.yaml archives added
Updated by dalley almost 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
Updated by dalley almost 6 years ago
- Status changed from ASSIGNED to POST
Added by dalley almost 6 years ago
Updated by dalley almost 6 years ago
- Status changed from POST to MODIFIED
- Platform Release set to 2.18.1
Updated by dalley almost 6 years ago
Applied in changeset a6a8e5dee38bb817e8f0dd9858e0117016f26fc2.
Added by dalley almost 6 years ago
Revision 7835e11b | View on GitHub
Fix bugs related to modularity
Ensure we don't publish module metadata files for repositories where the source repo had none.
Use the correct mechanism for determining the checksum used in the name of the modules.yaml.gz metadata file.
Additionally, refactor the module publish step to be more similar to the others.
closes #4252 https://pulp.plan.io/issues/4252 closes #4253 https://pulp.plan.io/issues/4253
Updated by bherring almost 6 years ago
- Copied to Test #4350: modules.yaml file is generated on repository with no modularity information added
Updated by dalley almost 6 years ago
Applied in changeset 7835e11b4710ed426f2471759c70e227c1128495.
Updated by jortel@redhat.com almost 6 years ago
- Status changed from MODIFIED to 5
Updated by jortel@redhat.com almost 6 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Fix bugs related to modularity
Ensure we don't publish module metadata files for repositories where the source repo had none.
Use the correct mechanism for determining the checksum used in the name of the modules.yaml.gz metadata file.
Additionally, refactor the module publish step to be more similar to the others.
closes #4252 https://pulp.plan.io/issues/4252 closes #4253 https://pulp.plan.io/issues/4253