On Tue, Jan 22, 2013 at 6:59 AM, <[email protected]> wrote: > That was a bug and fixed partially. Now installation happens but puppet > commands are broken and I see no manifests files in the new module > directories. > > # puppet module install puppetlabs/node_openstack > Preparing to install into /etc/puppetlabs/puppet/modules ... > Downloading from http://forge.puppetlabs.com ... > Installing -- do not interrupt ... > /etc/puppetlabs/puppet/modules > ââ⬠puppetlabs-node_openstack (v0.0.4) > âââ puppetlabs-cloud_provisioner (v1.0.5) > > # puppet module list > /etc/puppetlabs/puppet/modules > âââ puppetlabs-cloud_provisioner (v1.0.5) > âââ puppetlabs-node_openstack (v0.0.4) > /opt/puppet/share/puppet/modules > âââ puppetlabs-auth_conf (v0.0.5) > âââ puppetlabs-pe_accounts (v1.1.0) > âââ puppetlabs-pe_compliance (v0.0.8) > âââ puppetlabs-pe_mcollective (v0.0.57) > âââ puppetlabs-request_manager (v0.0.5) > âââ puppetlabs-stdlib (v2.5.1) > âââ ripienaar-concat (v0.2.0) > > # ls /etc/puppetlabs/puppet/modules/ > cloud_provisioner node_openstack > > # puppet node_openstack > Error: Unknown Puppet subcommand 'node_openstack' > See 'puppet help' for help on available puppet subcommands > > # puppet help > err: no such file to load -- puppet/face/node/install > err: Try 'puppet help help help' for usage > > You can try exporting RUBYLIB with the modules lib dir to use the face. This is related to http://projects.puppetlabs.com/issues/7316.
HTH, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
