Actions
Test #4350
closed
modules.yaml file is generated on repository with no modularity information
Version:
Platform Release:
Tags:
Easy Fix, Pulp 2
Sprint:
Quarter:
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 bherring over 5 years ago
- Copied from Issue #4252: modules.yaml file is generated on repository with no modularity information added
Added by ragabala about 5 years ago
Updated by Anonymous about 5 years ago
- Status changed from NEW to MODIFIED
Applied in changeset pulp:pulp-2-tests|583699e66f1d35173ce810ade3b932c22f42d86d.
Added by ragabala about 5 years ago
Revision 4e1e4461 | View on GitHub
Adding checks for non-modular files non containing modules.yaml
This commit takes care of syncing and publishing non modular content and checking whether the published content doesn't have modules.yaml. The following are tested
- Checking whether no modules element is present in the repomd.xml under repodata
- Checking whether no
modules.yaml.gzfile is present in the published folder
Closes #4350
Updated by Anonymous about 5 years ago
Applied in changeset pulp:pulp-2-tests|4e1e4461abe966fbab504591362c652ea32d8541.
Updated by ragbalak almost 5 years ago
- Status changed from MODIFIED to CLOSED - COMPLETE
Tested this with - https://github.com/PulpQE/Pulp-2-Tests/pull/154
Actions
.
Adding checks for non-modular files non containing modules.yaml
This commit takes care of syncing and publishing non modular content and checking whether the published content doesn't have modules.yaml. The following are tested
modules.yaml.gzfile is present in the published folderCloses #4350