[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Some V4 oo-install issues



With regards to the first error about nodejs, it looks like either the Puppet class should install the nodejs package or that the openshift-origin-console RPM should require nodejs. Since the comprehensive deployment guide expects you to be able to run `rake assets:precompile` (<http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#verify-the-ruby-bundler>), my guess is that the RPM should require nodejs. Otherwise, it's straightforward to tell users to `yum install nodejs` in the guide and add another package declaration to `openshift_origin::console`.

With regards to the third error about /etc/openshift/env/OPENSHIFT_BROKER_HOST, see <https://github.com/openshift/puppet-openshift_origin/pull/255>.

The OpenShift Enterprise deployment guide tells you to set this value (<https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html/Deployment_Guide/Configuring_Node_Settings.html>), but the Origin deployment guide does not (<http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#configuring-node-settings-for-domain-name>).



On Mon, Jul 28, 2014 at 1:39 PM, Davidson, Mark <MDavidson websense com> wrote:

Here are a few issues from installing Openshift Origin V4 using oo-install:

 

I started with two servers brokerv4 and node01v4 and ran oo-install on the broker using the curl to sh method

 

Issues:

The broker fails a clean puppet run unless it has nodejs installed. The puppet error is:

 

err: /Stage[main]/Openshift_origin::Console/Exec[Console gem dependencies]: Failed to call refresh: /bin/rm -f Gemfile.lock &&     LD_LIBRARY_PATH=/opt/rh/ruby193/root/usr/lib64 GEM_PATH=/opt/rh/ruby193/root/usr/local/share/gems:/opt/rh/ruby193/root/usr/share/gems /opt/rh/ruby193/root/usr/bin/bundle show &&     /bin/chown apache:apache Gemfile.lock &&     /bin/rm -rf tmp/cache/* &&     LD_LIBRARY_PATH=/opt/rh/ruby193/root/usr/lib64 GEM_PATH=/opt/rh/ruby193/root/usr/local/share/gems:/opt/rh/ruby193/root/usr/share/gems /opt/rh/ruby193/root/usr/bin/rake assets:precompile &&     /bin/chown -R apache:apache /var/www/openshift/console returned 1 instead of one of [0] at /etc/puppet/modules/openshift_origin/manifests/console.pp:143

 

I fixed this by installing nodejs on the broker before running oo-install:

yum -y install https://mirror.openshift.com/pub/origin-server/release/4/rhel-6/dependencies/x86_64/nodejs-0.6.20-3.el6oso.x86_64.rpm

 

*****************

 

On the nodes the directory /opt/rh/ruby193/root/var/run does not exist, which is where mcollective wants to put its pid file (so service start/status think it is not running)

 

*****************

 

On the nodes /etc/openshift/env/OPENSHIFT_BROKER_HOST contains 'localhost', while /etc/openshift/node.conf:BROKER_HOST is correct

 

*****************

 

Every time I ran oo-install on clean servers it would get stuck waiting for the node to finish puppet, even though the log on the node said puppet had finished cleanly (and was not running)

 

brokerv4.srv.beta.myfqdn.com: Running Puppet deployment for host

node01v4.os.beta.myfqdn.com: Running Puppet deployment for host

node01v4.os.beta.myfqdn.com: Puppet module removal failed. This is expected if the module was not installed.

node01v4.os.beta.myfqdn.com: Attempting Puppet module installation (try #1)

brokerv4.srv.beta.myfqdn.com: Puppet module removal failed. This is expected if the module was not installed.

brokerv4.srv.beta.myfqdn.com: Attempting Puppet module installation (try #1)

node01v4.os.beta.myfqdn.com: Puppet module installation succeeded.

node01v4.os.beta.myfqdn.com: Cleaning yum repos.

brokerv4.srv.beta.myfqdn.com: Puppet module installation succeeded.

brokerv4.srv.beta.myfqdn.com: Cleaning yum repos.

node01v4.os.beta.myfqdn.com: Running the Puppet deployment. This step may take up to an hour.

brokerv4.srv.beta.myfqdn.com: Running the Puppet deployment. This step may take up to an hour.

brokerv4.srv.beta.myfqdn.com: Puppet deployment completed.

 

After stopping oo-install and rerunning it, everything would work

 

brokerv4.srv.beta.myfqdn.com: Running Puppet deployment for host

node01v4.os.beta.myfqdn.com: Running Puppet deployment for host

node01v4.os.beta.myfqdn.com: Existing puppet module removed.

node01v4.os.beta.myfqdn.com: Attempting Puppet module installation (try #1)

brokerv4.srv.beta.myfqdn.com: Existing puppet module removed.

brokerv4.srv.beta.myfqdn.com: Attempting Puppet module installation (try #1)

brokerv4.srv.beta.myfqdn.com: Puppet module installation succeeded.

brokerv4.srv.beta.myfqdn.com: Cleaning yum repos.

node01v4.os.beta.myfqdn.com: Puppet module installation succeeded.

node01v4.os.beta.myfqdn.com: Cleaning yum repos.

brokerv4.srv.beta.myfqdn.com: Running the Puppet deployment. This step may take up to an hour.

node01v4.os.beta.myfqdn.com: Running the Puppet deployment. This step may take up to an hour.

node01v4.os.beta.myfqdn.com: Puppet deployment completed.

node01v4.os.beta.myfqdn.com: Keeping /tmp/oo_install_configure_node01v4.os.beta.myfqdn.com.pp

brokerv4.srv.beta.myfqdn.com: Puppet deployment completed.

brokerv4.srv.beta.myfqdn.com: Keeping /tmp/oo_install_configure_brokerv4.srv.beta.myfqdn.com.pp

 

Host deployments completed succesfully.

 

Restarting services in dependency order.

brokerv4.srv.beta.myfqdn.com: service mongod restart succeeded.

node01v4.os.beta.myfqdn.com: service ruby193-mcollective stop succeeded.

brokerv4.srv.beta.myfqdn.com: service activemq restart succeeded.

node01v4.os.beta.myfqdn.com: service ruby193-mcollective start succeeded.

brokerv4.srv.beta.myfqdn.com: service openshift-broker restart succeeded.

brokerv4.srv.beta.myfqdn.com: service openshift-console restart succeeded.

 

Now performing post-installation tasks.

 

Successfully created district 'Default'.

Attempting to add compatible Nodes to Default district... succeeded.

 

Attempting to register available cartridge types with Broker(s).

Cartridge registrations succeeded.

 

*****************

 

I tried a Jenkins server and client. The server installs ok (version 1.574) and the client (on another app) installs a job on the server. But the job doesn't seem to work - no gear gets spun up when you run it , so nothing happens.

 

 






_______________________________________________
dev mailing list
dev lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]