Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1488515 - pulp_manifest_builder.rb needs to be available via repo
Summary: pulp_manifest_builder.rb needs to be available via repo
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks: 1505387
TreeView+ depends on / blocked
 
Reported: 2017-09-05 14:53 UTC by Stephen Wadeley
Modified: 2021-04-06 17:50 UTC (History)
12 users (show)

Fixed In Version: python-pulp-manifest-2.13.4.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 3091 0 Normal CLOSED - CURRENTRELEASE As a user, I can create a manifest for the files in a directory 2018-04-03 21:36:30 UTC

Description Stephen Wadeley 2017-09-05 14:53:18 UTC 
Description of problem:

The code in pulp_manifest_builder.rb needs to be available in a safe form, such as an RPM, via Satellite repo.
Comment 1 Stephen Wadeley 2017-09-05 14:54:24 UTC 
Bug 1453052 - [RFE] [6.3] Describe how to configure and work with arbitrary files in content views
Comment 9 pulp-infra@redhat.com 2018-01-03 16:33:01 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2018-01-03 16:33:05 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 12 pulp-infra@redhat.com 2018-01-18 14:31:58 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 14 pulp-infra@redhat.com 2018-01-18 17:32:01 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 15 pulp-infra@redhat.com 2018-01-18 18:01:54 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 16 Peter Ondrejka 2018-01-24 16:27:03 UTC 
Verified on Sat 6.3 snap 33, the python-pulp-manifest package is provided in satellite tools
Comment 18 Satellite Program 2018-02-21 16:54:17 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> 
> For information on the advisory, and where to find the updated files, follow the link below.
> 
> If the solution does not work for you, open a new bug report.
> 
> https://access.redhat.com/errata/RHSA-2018:0336
Comment 19 pulp-infra@redhat.com 2018-03-20 15:32:04 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 20 pulp-infra@redhat.com 2018-04-03 21:36:31 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Note You need to log in before you can comment on or make changes to this bug.