Project

Profile

Help

Issue #4252

modules.yaml file is generated on repository with no modularity information

Added by jsherril@redhat.com almost 3 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.18.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix, Pulp 2
Sprint:
Sprint 47
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

Related to RPM Support - Issue #4268: Publishing a repo in-place multiple times creates multiple modules.yaml archivesCLOSED - NOTABUG<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Copied to RPM Support - Test #4350: modules.yaml file is generated on repository with no modularity informationCLOSED - COMPLETE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision a6a8e5de View on GitHub
Added by dalley almost 3 years ago

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

Revision 7835e11b View on GitHub
Added by dalley over 2 years ago

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

History

#1 Updated by CodeHeeler almost 3 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 46
  • Tags Easy Fix added

#2 Updated by dalley almost 3 years ago

  • Related to Issue #4268: Publishing a repo in-place multiple times creates multiple modules.yaml archives added

#3 Updated by rchan almost 3 years ago

  • Sprint changed from Sprint 46 to Sprint 47

#4 Updated by dalley almost 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dalley

#5 Updated by dalley almost 3 years ago

  • Status changed from ASSIGNED to POST

#6 Updated by dalley almost 3 years ago

  • Status changed from POST to MODIFIED
  • Platform Release set to 2.18.1

#7 Updated by dalley almost 3 years ago

#8 Updated by bherring over 2 years ago

  • Copied to Test #4350: modules.yaml file is generated on repository with no modularity information added

#9 Updated by dalley over 2 years ago

#10 Updated by jortel@redhat.com over 2 years ago

  • Status changed from MODIFIED to 5

#11 Updated by jortel@redhat.com over 2 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

#12 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF