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 1439927 - UUID is not set on a ContentViewPuppetModule
Summary: UUID is not set on a ContentViewPuppetModule
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Andrew Kofink
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-06 21:27 UTC by Andrew Kofink
Modified: 2017-04-25 16:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-19 13:54:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19211 0 None None None 2017-04-06 21:29:14 UTC

Description Andrew Kofink 2017-04-06 21:27:44 UTC
Description of problem:
UUID is used to link a ContentViewPuppetModule to a PuppetModule in the database, but it is not set when you add a puppet module to a content view.

Version-Release number of selected component (if applicable):
6.2.8 and nightly

How reproducible:
Always

Steps to Reproduce:
1. Create a product
2. Create a puppet module repo
3. Upload a puppet module to the new repo (i.e. https://forge.puppet.com/v3/files/puppetlabs-stdlib-4.16.0.tar.gz)
4. Create a content view
5. Add your puppet module to the content view

Actual results:
The ContentViewPuppetModule object has a nil uuid

Expected results:
The ContentViewPuppetModule object has the uuid set to the PuppetModule's uuid

Additional info:
The UUID is on the ContentViewPuppetModule to enable access to the PuppetModule. i.e. content_view_puppet_module.puppet_module will give you the PuppetModule object. Otherwise, it will return nil.

Comment 1 Andrew Kofink 2017-04-06 21:29:13 UTC
Created redmine issue http://projects.theforeman.org/issues/19211 from this bug

Comment 4 Andrew Kofink 2017-04-19 13:54:05 UTC
This is not a bug. This happens when you add the latest version of a puppet module to a content view. The UUID is set if you add a specific version of the puppet module to the content view.

Regardless, when the content view is published the UUID of the version specified (specific or latest at the time) is added to the content view version.


Note You need to log in before you can comment on or make changes to this bug.