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

RE: oo-install for Origin version 3



If it's not an AIO:

  • Make sure all of your hosts are pointing to the same NTP time-source (the broker is a good starting point).
  • SSH to each node (you installed) and check that oo-accept-node works.
    • Often times you'll need to fix /etc/resolv.conf so that that you have fwd/reverse look-up working
    • If needed add a search and domain entry inside of /etc/resolv.conf since it's not there by default on some fresh builds.
    • Cycle mcollective.
    • Retry oo-accept-node.  You'll probably need to add some sysctl settings, it'll tell you what needs fixed.
      • On FC19 I've had to add "kernel.sem = 250  32000 32  4096", and reload it.  (sysctl -p)
  • Cycle activemq on the broker, then retry oo-diagnostics -vv


Good luck,



Michael J. McConachie

NOTE: The information included and/or attached in this electronic mail transmission may contain confidential or privileged information and is intended solely for the addressee(s). Any unauthorized disclosure, reproduction, distribution or the taking of action in reliance on the contents of the information are strictly prohibited. If you have received the message in error, please notify the sender by reply transmission and delete the message without copying, disclosing or forwarding.


> From: s madathilthattantav accenture com
> To: hripps redhat com
> Subject: RE: oo-install for Origin version 3
> Date: Tue, 14 Jan 2014 20:39:23 +0000
> CC: users lists openshift redhat com; dev lists openshift redhat com
>
> Hi Harrison
>
> Thanks -that was resolved -but install script seems to not work -while running the script there are no errors -
>
> After rebooting the broker - I don't see anything working
> [root ip-10-182-206-230 etc]# cd openshift/
> [root ip-10-182-206-230 openshift]# ls
> htpasswd
> [root ip-10-182-206-230 openshift]# ls -lrt
> total 0
> -rw-r--r--. 1 root root 0 Jan 14 15:12 htpasswd
> [root ip-10-182-206-230 openshift]# oo-accept-broker -v
> bash: oo-accept-broker: command not found
> [root ip-10-182-206-230 openshift]# mco ping
> bash: mco: command not found
> [root ip-10-182-206-230 openshift]# service named status
> rndc: connect failed: 127.0.0.1#953: connection refused
> named is stopped
>
> Can you suggest how to debug the issues --
>
> the script logs are
>
>
> Preflight check: verifying system and resource availability.
>
> Checking broker.cloudshift.com:
> * Target host is running Red Hat Enterprise Linux
> * Located getenforce
> * SELinux is running in enforcing mode
> * Located yum
> * Located puppet
> * Located dnssec-keygen
> * Located htpasswd
> * Located scl
> * The ruby193 software collection is installed.
> * epel repository is present and enabled
>
> Checking node1.cloudshift.com:
> * SSH connection succeeded
> * Target host is running Red Hat Enterprise Linux
> * Located getenforce
> * SELinux is running in enforcing mode
> * Located yum
> * Located puppet
> * Located scl
> * The ruby193 software collection is installed.
> * epel repository is present and enabled
>
> Deploying workflow 'origin_deploy'.
> Setting up htpasswd for default user account.
>
> Preparing to install OpenShift Origin on the following hosts:
> * localhost: msgserver, dbserver, broker
> * 10.235.28.236: node
> Deploying host 'broker.cloudshift.com'
>
> Checking for DNS key on localhost...
> ...found at /var/named/Kcloudshift.com*.key
> bash: systemctl: command not found
> Command 'systemctl' didn't work; trying older style...
> Older style system command succeeded.
>
> Running Puppet deployment
> Deploying host 'node1.cloudshift.com'
>
> Running "bash -l -c 'scl enable ruby193 "puppet module list --render-as yaml"'"...
> Copying Puppet configuration script to target 10.235.28.236.
> Error: Unknown command module.
> Usage: puppet command <space separated arguments>
> Available commands are: agent, apply, cert, describe, doc, filebucket, inspect, kick, master, queue, resource
> /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:480: undefined method `keys' for false:FalseClass (NoMethodError)
> from /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:449:in `each'
> from /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:449
> from /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:446:in `fork'
> from /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:446
> from /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:288:in `each'
> from /tmp/oo-install-20140103-1839/workflows/origin_deploy/originator.rb:288
>
> Running Puppet deployment
>
> Running "ssh -t -q root 10 235 28 236 -C "scl enable ruby193 \"puppet module list --render-as yaml\"""...
> Command completed.
>
> Running "ssh -t -q root 10 235 28 236 -C "scl enable ruby193 \"puppet module install -v 3.0.1 openshift/openshift_origin\"""...
> Command completed.
>
> Running "ssh -t -q root 10 235 28 236 -C "yum clean all""...
> Command completed.
>
> Running "ssh -t -q root 10 235 28 236 -C "scl enable ruby193 \"puppet apply --verbose /tmp/oo_install_configure_node1.cloudshift.com.pp\"""...
>
> Running "ssh -t -q root 10 235 28 236 -C "yum clean all""...
> Command completed.
>
> Running "ssh -t -q root 10 235 28 236 -C "scl enable ruby193 \"puppet apply --verbose /tmp/oo_install_configure_node1.cloudshift.com.pp\"""...
> Command completed.
>
> Running "ssh -t -q root 10 235 28 236 -C "rm /tmp/oo_install_configure_node1.cloudshift.com.pp""...
> Command completed.
> OpenShift Origin deployment completed.
> You chould manually reboot these hosts in the indicated order to complete the process:
> 1. broker.cloudshift.com
> 2. node1.cloudshift.com
>
>
>
>
> -----Original Message-----
> From: N. Harrison Ripps [mailto:hripps redhat com]
> Sent: Wednesday, January 15, 2014 12:38 AM
> To: Madathilthattantav, S.
> Cc: dev lists openshift redhat com; users lists openshift redhat com
> Subject: Re: oo-install for Origin version 3
>
> Hey Shabna--
>
> On Jan 14, 2014, at 13:55 , s madathilthattantav accenture com wrote:
>
> > Hi Harrison
> >
> > Thanks for the pointers. I am following this guide
> > http://openshift.github.io/documentation/oo_install_users_guide.html
> > To install origin v3 in aws -rhel .I am hitting this error :Am I missing something obvious?
> >
> > Checking broker.cloudshift.com:
> > * Target host is running Red Hat Enterprise Linux
> > * Located getenforce
> > * SELinux is running in enforcing mode
> > * Located yum
> > * Located puppet
> > * Located dnssec-keygen
> > * Located htpasswd
> > * Located scl
> > * The ruby193 software collection is installed.
> > * epel repository is present and enabled
> >
> > Checking node1.cloudshift.com:
> > * SSH connection succeeded
> > * Target host is running Red Hat Enterprise Linux
> > * Located getenforce
> > * SELinux is running in enforcing mode
> > * Located yum
> > * Located puppet
> > * Located scl
> > * The ruby193 software collection is installed.
> > * ERROR: Could not perform repo check for epel. Try running `yum
> > repolist` manually to troubleshoot.
>
> oo-install attempted to run `yum repolist` on node1.cloudshift.com and got a non-zero result.
> Please manually run that command on that host as root and let me know if it succeeds.
>
> >
> > My configuration looks like this :
> > Role Assignments
> > +--------+-----------------------+
> > | Broker | broker.cloudshift.com |
> > | Node | node1.cloudshift.com |
> > +--------+-----------------------+
> >
> > Host Information
> > +----------------+-----------------------+
> > | Host | broker.cloudshift.com |
> > | Roles | Broker |
> > | SSH Host | localhost |
> > | User | root |
> > | IP Addr | 10.182.206.230 |
> > | IP Interface | eth0 |
> > | Install Status | new |
> > +----------------+-----------------------+
> > +----------------+----------------------+
> > | Host | node1.cloudshift.com |
> > | Roles | Node |
> > | SSH Host | 10.183.142.148 |
> > | User | root |
> > | IP Addr | 10.183.142.148 |
> > | IP Interface | eth0 |
> > | Install Status | new |
> > +----------------+----------------------+
> >
> > Here is the subscription configuration that the installer will use for
> > this deployment.
> > +-------------------+----------------------------------------------------------------+
> > | Setting | Value |
> > +-------------------+----------------------------------------------------------------+
> > | type | yum |
> > | repos_base | http://mirror.openshift.com/pub/origin-server/release/3/rhel-6 |
> > | jboss_repo_base | - |
> > | jenkins_repo_base | http://pkg.jenkins-ci.org/redhat |
> > | os_repo | - |
> > | os_optional_repo | - |
> > +-------------------+----------------------------------------------------------------+
> >
> >
> > Let me know if I am missing something.I was able to install origin in aws using puppet.
> >
> > Thanks
> > Shabna
> >
> >
> > From: Harrison Ripps [mailto:hripps redhat com]
> > Sent: Tuesday, January 14, 2014 6:50 PM
> > To: Madathilthattantav, S.
> > Cc: dev lists openshift redhat com; users lists openshift redhat com
> > Subject: Re: oo-install for Origin version 3
> >
> > Hi Shabna--
> > We've tested the Origin-3-on-RHEL scenario an it does work. Check the oo-install guide on openshift.github.io for some prerequisites (like Puppet) that you will need to set up on your target host(s). Let me know if you run into any problems.
> >
> > Cheers,
> > Harrison
> >
> > On Jan 14, 2014, at 6:36, <s madathilthattantav accenture com> wrote:
> >
> > Hi All
> >
> > Has anyone tried out Origin v3 install using oo-install utility in AWS
> > ?(RHEL)
> >
> > Thanks
> > Shabna
> >
> >
> > This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. .
> > ______________________________________________________________________
> > ________________
> >
> > www.accenture.com
> > _______________________________________________
> > users mailing list
> > users lists openshift redhat com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>
>
> _______________________________________________
> users mailing list
> users lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

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