Issue #1879
Updated by bmbouter almost 8 years ago
<pre> ### For creating local motd module ### sudo mkdir /var/www/html/pub/puppet-modules sudo chmod a+rw /var/www/html/pub/puppet-modules git clone https://github.com/puppetlabs/puppetlabs-motd.git cd puppetlabs-motd sudo pulp-puppet-module-builder --output-dir /var/www/html/pub/puppet-modules . </pre> Sync this into Pulp with: <pre> pulp-admin puppet repo create --repo-id=motd --feed=file:///var/www/html/pub/puppet-modules pulp-admin puppet repo sync run --repo-id motd </pre> If you look at the name stored in the DB for that puppet module you'll see: <pre> "name" : "puppetlabs-motd", </pre> The module name is puppetlabs-motd in puppetlabs-motd. Syncing the metadata.json, but for 2 reasons the name is expected to be just 'motd'. 1. When this module is published with the puppet install distributor, the folder name will be 'puppet-motd' which causes puppet to error when repo into katello it runs. It expects the folder to be the same name shows up in foreman UI as the puppet class simply "motd" which is motd. 2. This is different from the name produced then cannot be found by this same module brought in via sync-from -puppet-forge or traditional upload. I recommend having the sync from file:// also use split_filename() as the others[0][1] do today. [0]: https://github.com/pulp/pulp_puppet/blob/c9598b39f21a366dd771b05f9c6e3831f33f78e2/pulp_puppet_plugins/pulp_puppet/plugins/importers/forge.py#L298 [1]: https://github.com/pulp/pulp_puppet/blob/c9598b39f21a366dd771b05f9c6e3831f33f78e2/pulp_puppet_plugins/pulp_puppet/plugins/importers/upload.py#L46 puppet.
.