Project

Profile

Help

Test #4930

closed

Pulp - Test #4942: [EPIC] - Pulp2 - 2.20

NaUse RPMTAG_MODULARITYLABEL to determine modular RPM

Added by bherring almost 5 years ago. Updated over 4 years ago.

Status:
CLOSED - COMPLETE
Priority:
High
Assignee:
Sprint/Milestone:
Version:
Platform Release:
2.20.0
Tags:
Pulp 2
Sprint:
Quarter:

Description

Original Dev Text

According to information from modularity folks RPMTAG_DISTTAG is no longer in use for modularity purposes.
RPMTAG_MODULARITYLABEL should be used instead.

This affects applicability calculations which rely on the correct identification of modular RPMs.
The problem should not be huge or broad, most modular RPMs are identified as such at sync time using metadata.

This tag is supported in old versions of rpm, just the name is not exposed and numeric key should be used:
The constant rpm. RPMTAG_MODULARITYLABEL is not available on Centos7 and < F30, instead the id if the header 5096 can be used directly: headers[5096].

QE Text

Talked with Tanya, and it it looks like we need test coverage for rpm upload checking for is_modular.

The following test can be used as a baseline logic for the test, replacing a sync action with an upload action:

Also, need to ensure that the relevant RPM_WITH_MODULES_FEED_URL 's RPMs are being built correctly (F30 base image now) to ensure the fixture contains what we expect for test.


Related issues

Copied from RPM Support - Issue #4869: Use RPMTAG_MODULARITYLABEL to determine modular RPMCLOSED - CURRENTRELEASEttereshcActions

Also available in: Atom PDF