Forgot to include that I'm running Katello 3.1rc2 w/ TFM 1.12.2 and that I 
included the following options when running foreman-installer:

    --enable-foreman-plugin-openscap
    --enable-foreman-proxy-plugin-openscap
    --foreman-plugin-openscap-configure-openscap-repo true

My [CentOS 7] server has the following OpenSCAP packages installed:

    openscap-1.2.9-5.el7_2.x86_64
    openscap-scanner-1.2.9-5.el7_2.x86_64
    rubygem-openscap-0.4.3-1.el7.noarch
    rubygem-smart_proxy_openscap-0.5.4-1.el7.noarch
    tfm-rubygem-foreman_openscap-0.5.4-1.fm1_12.el7.noarch

I'm guessing that I'm running into http://projects.theforeman.org/issues/10906, 
or something similar.  The lack of separation between production and other 
environments seems awfully serious, but that issue has been open for around a 
year.  What am I missing here?

j



----- Original Message -----
From: "'Jason B. Nance' via Foreman users" <[email protected]>
To: [email protected]
Sent: Thursday, August 25, 2016 7:33:19 PM
Subject: [foreman-users] Puppet Module Conflict

Hello,

As part of setting up OpenSCAP using the instructions at:

    https://www.theforeman.org/plugins/foreman_openscap/0.5/

...I ran:

    puppet module install isimluk-foreman_scap_client

...which installed the module into:

    /etc/puppet/environments/production/modules/

...as well as its dependency, stdlib.

The problem I'm running into now is that I can't publish a version of any 
content view that includes stdlib as I get the following error:

    Validation failed: Name has already been taken

The strange thing is that prior to running the "puppet module install" command 
I attempted to add the foreman_scap_client to my product and content view, but 
I would get the error above even then (when the module *wasn't* part of 
"production" or any other environment), and I couldn't assign my proxy as the 
"Openscap Proxy" when configuring my host group as I would get the following 
error:

    Puppet class 'foreman_scap_client' not found, make sure it is imported from 
Puppet master

My custom modules depend on stdlib and I'd like to version control it and 
publish throughout the lifecycles as I do other content.

Is there something special about the production environment?  Can someone help 
me sort this out?

Thanks,

j

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to