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 1190693 - publishing puppet modules places the modules in a randomly generated dir
Summary: publishing puppet modules places the modules in a randomly generated dir
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: Unspecified
Assignee: Jason Montleon
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On: 1047797 1186445
Blocks: 1193354
TreeView+ depends on / blocked
 
Reported: 2015-02-09 13:18 UTC by Kedar Bidarkar
Modified: 2017-02-23 20:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:24:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
required puppet class foreman_scap_client (32.00 KB, image/png)
2015-02-17 15:29 UTC, Kedar Bidarkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Kedar Bidarkar 2015-02-09 13:18:22 UTC 
Description of problem:

publishing of puppet modules places the modules in a randomly generated dir.


Library environment:
[root@yyyy modulesezp4tE]# ls
foreman_scap_client  openscap
[root@yyyy modulesezp4tE]# pwd
/etc/puppet/environments/KT_Default_Organization_Library_puppet_foreman_scap_cv_3/modulesezp4tE

Libary->prabhjeet environamnet:

[root@yyyy modulesQvTiys]# ls
foreman_scap_client  openscap
[root@yyyy modulesQvTiys]# pwd
/etc/puppet/environments/KT_Default_Organization_Prabhjeet_puppet_foreman_scap_cv_3/modulesQvTiys



NOTE: the random modules dir_Structure int he end.

Version-Release number of selected component (if applicable):
Beta-snap1-snap6

How reproducible:
always

Steps to Reproduce:
1. create a puppet repo and sync
2. publish the puppet repo
3. Note that the puppet_module gets generated in a randomly generated dir_structure.



Actual results:
randomly named directory.

Expected results:
puppet modules are deployed to /etc/puppet/environments/<environment>/module

Additional info:
Comment 1 Kedar Bidarkar 2015-02-09 13:19:33 UTC 
Version : Sat6.1-Beta-snap1-compose3
Comment 3 Brad Buckingham 2015-02-13 13:51:06 UTC 
Can you provide an example of the directory name that you see?

Is it something like?
   KT_Default_Organization_Library_OS_18

If so, it is based on logic which uses the following syntax:
   KT_[org label]_[lifecycle environment label]_[content view label]_[content view id]

It is possible that the algorithm could change; however, it is not really random.
Comment 4 Kedar Bidarkar 2015-02-16 15:08:16 UTC 
For example:

/etc/puppet/environments/KT_Default_Organization_Library_puppet_foreman_scap_cv_3/modulesezp4tE

/etc/puppet/environments/KT_Default_Organization_Prabhjeet_puppet_foreman_scap_cv_3/modulesQvTiys

Please note the end of the dir_structure which is : 
modulesezp4tE or 
modulesQvTiys
Comment 5 Šimon Lukašík 2015-02-17 13:07:52 UTC 
puppet-foreman_scap_client will be shipped as an RPM file.

I am not sure why would user want to create a puppet repo for puppet-foreman
_scap_client. What is the use-case?
Comment 7 Brad Buckingham 2015-02-17 14:26:49 UTC 
Moved to POST since the upstream pulp bug is now ON_QA and available.
Comment 8 Kedar Bidarkar 2015-02-17 14:30:43 UTC 
Looking at puppet-foreman_scap_client I was under the impression that we need to go by the puppet-modules/puppet-classes approach.

If we will be using it in RPM file format, can we get access to these RPMs.


@simon Lukasik: I think this is because I have no idea about the OpenScap workflow, atleast some rough documentation regarding it would help. :)
Comment 9 Kedar Bidarkar 2015-02-17 15:29:58 UTC 
Created attachment 992744 [details]
required puppet class foreman_scap_client

The use-case being the attached screenshot message from the UI while creating the OSCAP policy.

I had picked the "puppet-foreman_scap_client" puppet-module from forge.puppetlabs and was trying to publish it.

The message from the screen-shot made me feel we need to go the puppet-module/puppet-classes approach, but now really interested in knowing how to take it forward using the RPM approach and have puppet-classes visible.

Some steps would help.
Comment 10 Kedar Bidarkar 2015-02-17 15:50:53 UTC 
Update for comment 8:

I see the package rubygem-foreman_scap_client-0.1.0-1.el6_6sat.noarch

a) but not sure how do we get the puppet-classes from it.
b) May be I will try to create a repo, sync and publish it and check if puppet-classes will populate.


I think will take this discussion offline, here after.
Comment 13 Kedar Bidarkar 2015-02-23 13:16:08 UTC 
Now puppet-classes get populated once the puppet-modules are synced, published and promted.

VERIFIED with sat6.1 beta snap3
Comment 14 Bryan Kearney 2015-08-11 13:26:57 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 15 errata-xmlrpc 2015-08-12 05:24:11 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-2015:1592
Note You need to log in before you can comment on or make changes to this bug.