While the location is correct, the modules are named incorrectly…the
module folders should be just the "name" of the module. Instead, it's
being written as author-name.
So, if I write a module called me-ldap-1.0.0.tar.gz and upload it or sync
it to the puppet repository, when I use a view to access the content, the
view writes this module as:
me-ldap/
instead of:
ldap/
The result is:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find class ldap for [clienthost] on node [katelloserver]
This is killing my ability to distribute content. Any ideas?
> When I publish puppet modules to a lifecycle environment, they get
> written to the following location:
>
> /etc/puppet/environments/KT_ORG_QA_exampleview/modules/
>
> While the location is correct, the modules are named incorrectly…the
> module folders should be just the "name" of the module. Instead, it's
> being written as author-name.
>
> So, if I write a module called me-ldap-1.0.0.tar.gz and upload it or
> sync it to the puppet repository, when I use a view to access the
> content, the view writes this module as:
>
> me-ldap/
>
> instead of:
>
> ldap/
>
> The result is:
>
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find class ldap for [clienthost] on node [katelloserver]
>
> This is killing my ability to distribute content. Any ideas?
This was a bug in pulp filed here: https://bugzilla.redhat.com/show_bug.cgi?id=1123446
This was resolved in 2.4.1, whereas katello 2.0 ships with 2.4.0.
We are planning on a Katello 2.0.1 release and we could include pulp
2.4.3 as part of that as well. I think this is a good enough reason to
do that.
How are you getting your puppet modules into katello?
I believe the issue does not occur when:
syncing puppet forge (or your own hosted version of puppet forge)
using hammer to upload them
Using the UI to upload them
-Justin
···
On 10/30/2014 01:23 PM, Garrett DeMarco wrote:
> Thanks for the info. I hope 2.0.1 is released soon.
>
> Please do include a newer pulp. Has someone found a workaround for
> this issue in the mean time? I'd rather not introduce an untested
> version...
>
> Thanks.
> --
> 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 foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
I use a custom foreman puppet environment to develop the modules…called
development, and then run pulp-puppet-module-builder on it to generate all
the puppet modules and it puts them in the /modules directory. Then I
create a puppet repository in Katello and sync to file://modules.
Everything imports just fine with no errors.
Ahh yes, that is the one workflow that hits this error.
You might call pulp-puppet-module-builder and then use 'hammer
repository upload-content' to upload the puppet module to your
repository in the meantime.
-Justin
···
On 10/30/2014 01:39 PM, Garrett DeMarco wrote:
> I use a custom foreman puppet environment to develop the
> modules...called development, and then run pulp-puppet-module-builder
> on it to generate all the puppet modules and it puts them in the
> /modules directory. Then I create a puppet repository in Katello and
> sync to file://modules. Everything imports just fine with no errors.
>
> Thanks.
> --
> 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 foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
