Project

Profile

Help

Issue #3353

Missing docs on importing RPM repository module metadata

Added by ttereshc about 1 year ago. Updated about 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Severity:
2. Medium
Version:
Platform Release:
2.15.3
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 33

Description

Example of the repo with module metadata.
http://dl.fedoraproject.org/pub/fedora/linux/modular/updates/testing/27/Server/x86_64/

This is a yaml file which should be treated by Pulp as non-specific metadata file - yum_repo_metadata_file.

More advanced support for this metadata type is a part of the story #3206.

modularity_test_client28.log (114 KB) Fedora28 client log milan, 02/22/2018 02:21 PM modularity_test_client28.log
modularity_test_journalctl.log (828 KB) Pulp journalctl log milan, 02/22/2018 02:22 PM modularity_test_journalctl.log
modularity_test.log (180 KB) Pulp admin screen log milan, 02/22/2018 02:22 PM modularity_test.log
modularity_on_demand_journalctl.log (12.8 KB) milan, 02/23/2018 03:02 PM modularity_on_demand_journalctl.log
modularity_on_demand_client.log (786 KB) milan, 02/23/2018 03:02 PM modularity_on_demand_client.log
modularity_on_demand.log (29.9 KB) milan, 02/23/2018 03:02 PM modularity_on_demand.log

Checklist


Related issues

Related to RPM Support - Story #3206: Support for module metadata in pulp_rpm CLOSED - CURRENTRELEASE Actions

Associated revisions

Revision 9c27b2e0 View on GitHub
Added by milan about 1 year ago

Document modularity support

Pulp_rpm supports the modularity content to the repo mirroring extent.

Fixes: #3353
https://pulp.plan.io/issues/3353

Revision a00515d2 View on GitHub
Added by milan about 1 year ago

Document modularity support

Pulp_rpm supports the modularity content to the repo mirroring extent.

Fixes: #3353
https://pulp.plan.io/issues/3353
(cherry picked from commit 9c27b2e02faf2dde881162bf35e216823a4506d7)

History

#1 Updated by ttereshc about 1 year ago

  • Description updated (diff)

#2 Updated by ttereshc about 1 year ago

  • Related to Story #3206: Support for module metadata in pulp_rpm added

#4 Updated by ttereshc about 1 year ago

  • Subject changed from As a user, I can import RHEL 8 module metadata to As a user, I can import RPM repository module metadata

#5 Updated by ttereshc about 1 year ago

  • Description updated (diff)

#6 Updated by dkliban@redhat.com about 1 year ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#7 Updated by rchan about 1 year ago

  • Sprint/Milestone set to 56

#8 Updated by ttereshc about 1 year ago

Please, implement/merge it during sprint 33 so it will go into 2.16.0 release (aka by mid-March)

#9 Updated by milan about 1 year ago

  • Assignee set to milan

#10 Updated by ttereshc about 1 year ago

  • Status changed from NEW to ASSIGNED

#11 Updated by milan about 1 year ago

Findings

I conducted manual testing of Modularity contnet.
My set up was as follows:
  • Fedora26 hosting a development deployment of Pulp 2.15.1 & Pulp_rpm 2.15
  • Fedora28 consumer node, SSL validation switched off
  • a Fedora27 modularity repository (by accident)
    Both the systems were running inside Docker.

Syncing

Pulp is able to sync modularity content, triggering manually.
I was able to create a rpm repository, feeding on the Fedora27 modularity repository manually.

Copying

I was able to copy a repository containing modularity content to a custom repository.
The modularity metadata gets copied automatically, in case of no filter applied (the all directive).
The modularity metadata gets copied in case of filtering, if the filter specified includes the yum_repo_metadata_file (REST API case) or the metafile in case of the Pulp admin CLI.

Consuming

I was able to successfully install a nodejs:6 module from the custom copied repository, on the Fedora28 client, following the dnf usecase instructions

On demand Sync

The on-demand sync worked; the modularity metadata is downloaded immediately, as expected, and gets published OK.
I was able to install content from a module of an on_demand repo too.

Notes

The upstream has decided to remove the F27 modularity tree so our testing data is gone. I've exported the repo I got for testing purposes, but it's a bit big (2.1G). I can share though.
They've got a rel-eng ticket tracking the modularity content handling progress.
The tool to create modularity content repos seems to be Pungi so we might still be able to create our own testing content later for Fixtures.

Due to the fact the modularity metadata isn't processed by Pulp yet (just copied) a consumer can observe discrepancies between modules available and content missing; this happened having copied just the metadata without any actual content:

sh-4.3# dnf module list --repo pulp2.dev_pulp_repos_mod_broken
Last metadata expiration check: 0:00:26 ago on Fri Feb 23 15:52:11 2018.
created by dnf config-manager from https://pulp2.dev/pulp/repos/mod_broken
Name                                                          Stream                                            Version                                                   Profiles
fonts                                                         f27                                               20171027091706                                            default, everything
freeipa                                                       master                                            20171030164651                                            default
installer                                                     f27                                               20171030201659                                            default
nodejs                                                        6                                                 20171107132706                                            default, development, ...
perl                                                          5.26                                              20171027072720                                            default, minimal
platform                                                      f27                                               20171028113024                                            buildroot, srpm-buildroot
python2-ecosystem                                             master                                            20171030225722

Hint: [d]efault, [e]nabled, [i]nstalled, [l]ocked
sh-4.3# dnf module enable --repo pulp2.dev_pulp_repos_mod_broken nodejs:6
Last metadata expiration check: 0:01:08 ago on Fri Feb 23 15:52:11 2018.
'nodejs:6' is enabled
sh-4.3# dnf --disablerepo='*' --enablerepo=pulp2.dev_pulp_repos_mod_broken install nodejs
Last metadata expiration check: 0:01:47 ago on Fri Feb 23 15:52:11 2018.
No match for argument: nodejs
Error: Unable to find a match
sh-4.3#

#13 Updated by milan about 1 year ago

  • File modularity_delayed_admin.log added
  • File modularity_delayed_journalctl.log added

#14 Updated by milan about 1 year ago

  • File deleted (modularity_delayed_admin.log)

#15 Updated by milan about 1 year ago

  • File deleted (modularity_delayed_journalctl.log)

#17 Updated by milan about 1 year ago

  • Status changed from ASSIGNED to POST

#18 Updated by milan about 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#19 Updated by milan about 1 year ago

  • Platform Release set to 2.15.3

#20 Updated by bmbouter about 1 year ago

  • Tracker changed from Story to Issue
  • Subject changed from As a user, I can import RPM repository module metadata to Missing docs on importing RPM repository module metadata
  • Severity set to 2. Medium
  • Triaged set to No

Switching to issue since code wasn't added and only issues can go into a z-stream release.

#21 Updated by bmbouter about 1 year ago

  • Sprint set to Sprint 33

#22 Updated by bmbouter about 1 year ago

  • Sprint/Milestone deleted (56)

#23 Updated by milan about 1 year ago

#24 Updated by bmbouter about 1 year ago

  • Status changed from MODIFIED to ON_QA

#25 Updated by bmbouter about 1 year ago

  • Status changed from ON_QA to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF