Bug 964975 - The puppet module install openshift/openshift_origin command fails on Fedora 18
Summary: The puppet module install openshift/openshift_origin command fails on Fedora 18
Keywords:
Status: CLOSED EOL
Alias: None
Product: OKD
Classification: Red Hat
Component: Documentation
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: mfisher
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-20 08:44 UTC by Jan Pazdziora
Modified: 2017-01-25 06:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-25 06:38:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Pazdziora 2013-05-20 08:44:25 UTC
Document URL: 

http://openshift.github.io/origin/file.install_origin_using_puppet.html

Section Number and Name: 

Installing Puppet

Describe the issue: 

# rpm -q puppet
puppet-2.7.18-1.fc18.noarch
# puppet module install openshift/openshift_origin
/usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead.
Preparing to install into /etc/puppet/modules ...
Error: Could not install module 'openshift-openshift_origin' (latest)
  Directory /etc/puppet/modules does not exist
#

Suggestions for improvement: 

Maybe the documentation should tell the user to create the directory?

Additional information: 

If bugzilla is not the proper way of reporting this kind of issues, please point me to better place/process.

Comment 1 Bilhar 2013-05-22 05:46:36 UTC
The document you're referring to is maintained by the developer team. Therefore, I'm reassigning this BZ to kraman to investigate.

Comment 3 Jan Pazdziora 2013-12-19 06:52:15 UTC
(In reply to Krishna Raman from comment #2)
> Fixed.
> http://openshift.github.io/documentation/oo_deployment_guide_puppet.html

Confirming, on Fedora 19, the steps described on that page make the installation pass.


Note You need to log in before you can comment on or make changes to this bug.