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

RE: OpenShift Origin Error in ec2 using puppet script



Hi

 

Thanks a lot for the help.

 

By Node script up is still erroring out.

 

I have actually validated  these steps from comprehensive guide – All set up right.

 

9.1. Register a DNS entry for the Node Host

9.2. Configure SSH Key Authentication

9.3. Configure DNS Resolution on the Node

9.4. Configure the DHCP Client and Hostname

9.5. MCollective on the Node Host

 

 

So ideally after this mco ping on broker should be able to resolve to Node – but its shows no response recieved.

I have faced this when I was setting up OSE in aws ,but then adding up tcp 61613 to the security group did the job.

 

Here I am not sure whats going wrong here.Has anybody faced similar issue ??

 

 

Script fails due to node not able to communicate with broker

 

Notice: /Stage[main]/Openshift_origin::Node/Exec[node selinux booleans]/returns: executed successfully

Notice: /Stage[main]/Openshift_origin::Node/Firewall[node-https]/Exec[Open port 8443:tcp]/returns: executed successfully

Notice: /Stage[main]/Openshift_origin::Role/Firewall[ssh]/Exec[final iptables setup]/returns: executed successfully

Notice: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: ; Communication with 10.180.194.23#53 failed: timed out

Notice: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: could not talk to specified name server

Error: (

  echo server 10.180.194.23

  echo update delete node1.example.com A

  echo update add node1.example.com 180 A 10.182.148.152

  echo send

) | nsupdate -y example.com:tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==

returned 1 instead of one of [0]

Error: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: change from notrun to 0 failed: (

  echo server 10.180.194.23

  echo update delete node1.example.com A

  echo update add node1.example.com 180 A 10.182.148.152

  echo send

) | nsupdate -y example.com:tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==

returned 1 instead of one of [0]

 

Shabna

 

From: Andrew Lau [mailto:andrew andrewklau com]
Sent: Thursday, December 05, 2013 3:28 AM
To: Madathilthattantav, S.
Cc: users lists openshift redhat com
Subject: Re: OpenShift Origin Error in ec2 using puppet script

 

I did my install manually following the comprehensive guide, so I'll try my best..

 

On Thu, Dec 5, 2013 at 5:43 AM, <s madathilthattantav accenture com> wrote:

Hi ,

 

Now that we have the broker up and running, I am trying to set up node in a different aws instance – I have some doubts and I am running into issues as well.

Can you share pointers on the same-

 

The script config :

   class { 'openshift_origin' :

      # Components to install on this host:

      roles                                                => ['node'],

 

      # BIND / named config

      # This is the IP address for OpenShift BIND server - here, the broker.

      named_ip_addr              => '10.180.194.23', I assume is the Private Ip of the broker

Yes, if you have your dns server on the broker.

      # This is the key for updating the OpenShift BIND server

      bind_key                   => 'tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==',   I assume is the TSIG Key generated from the broker

Same as above.

      # The domain under which applications should be created.

      domain                     => 'example.com',

      # Apps would be named <app>-<namespace>.example.com

      # This also creates hostnames for local components under our domain

      register_host_with_named   => true,

 

      # The FQDNs of the OpenShift component hosts we will need

      broker_hostname            => 'broker.example.com',

      activemq_hostname          => 'broker.example.com',

      node_hostname              => 'node1.example.com',

 

 

      #Enable development mode for more verbose logs

      development_mode           => true,

 

    }

 

Also some queries regarding the installation steps.

1.       Is it mandatory for node in aws to have elastic ip ?

If you want to be able to access it externally then yes. I believe if you do use an elastic ip you'll need to modify /etc/openshift/node.conf and set the public_ip to the elastic ip address. Also make sure that the dns public_hostname in the same file resolves to that IP.

 

2.       I have enabled ssh with root in node host.

 

3.         on the broker: keyfile=/var/named/example.com.key

                 on the broker: oo-register-dns -h node -d ose.example.com -n <EXTERNAL IP FOR NODE> -k ${keyfile}

I assume Should this be done before running puppet script on node ?

I don't think it matters.

 

4.       On the broker: scp /etc/openshift/rsync_id_rsa.pub <node.fqdn>:.ssh  (It should ask for the password)

on the node: cd /root/.ssh;cat rsync_is_rsa.pub >> authorized_keys

. on the broker test ssh:  ssh -i /root/.ssh/rsync_id_rsa <node.fqdn>  (Ignore warnings about breakin)

 

There is no such file rsync_id_rsa.pub !!note sure why..Am I missing anything here ?

You should generate your own on the broker host, and then copy it to all your nodes.

 

The script hangs in Node with the following error : I think this expected as it is not able to contact broker

 

Error: (

  echo server 10.180.194.23

  echo update delete node1.example.com A

  echo update add node1.example.com 180 A 10.182.148.152

  echo send

) | nsupdate -y example.com:tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==

returned 1 instead of one of [0]

Error: /Stage[main]/Openshift_origin::Role::Node/Register_dns[register node dns]/Exec[Register node1.example.com]/returns: change from notrun to 0 failed: (

  echo server 10.180.194.23

  echo update delete node1.example.com A

  echo update add node1.example.com 180 A 10.182.148.152

  echo send

) | nsupdate -y example.com:tsGD77RCMf7LqLuI9CMMdTat3aHQ0A==

returned 1 instead of one of [0]

 

Appreciate you help.

 

Thanks

Shabna

 

 

 

 

From: Andrew Lau [mailto:andrew andrewklau com]

Sent: Wednesday, December 04, 2013 5:09 PM
To: Madathilthattantav, S.
Cc: dev lists openshift redhat com; users lists openshift redhat com; mlamouri redhat com; kraman redhat com

Subject: Re: OpenShift Origin Error in ec2 using puppet script

 

I recall running into something similar. Check to make sure:

     - httpd

      - openshift-broker

      - openshift-console

 

Are running and not blocked by iptables.

 

On Wed, Dec 4, 2013 at 6:30 PM, <s madathilthattantav accenture com> wrote:

Oops..Apologize ..missed the attachments.

 

Shabna

 

From: Madathilthattantav, S.
Sent: Wednesday, December 04, 2013 12:54 PM
To: 'dev lists openshift redhat com'; users lists openshift redhat com
Cc: 'hripps redhat com'; 'kraman redhat com'; 'mlamouri redhat com'
Subject: OpenShift Origin Error in ec2 using puppet script

 

Hi

 

I am trying to setup OpenShift Origin in Fedora –ec2 instance.But stuck with some errors.These are the steps  I am following :

 

1.launch a Fedor ami (ami-b22e5cdb )instance in ec2 (medium ,volume 20gb ) and associated the right security group

2.Associate an elastic address.

3.Enabled ssh access using root.

4.Following step by step instruction on http://openshift.github.io/documentation/oo_deployment_guide_puppet.html#configuring-separate-hosts-for-broker-node [Onebroker +One Node ]

 

a.       yum install -y puppet facter tar

b.      mkdir -p /etc/puppet/modules

c.       cd /etc/puppet/modules

d.      yum install -y bind

#Using example.com as the cloud domain

e.      /usr/sbin/dnssec-keygen -a HMAC-MD5 -b 512 -n USER -r /dev/urandom -K /var/named example.com

f.        cat /var/named/Kexample.com.*.key  | awk '{print $8}'

g.       echo "broker.example.com" > /etc/hostname

hostname broker.example.com

#Configure the configure_origin.pp (attached)

h.      puppet apply --verbose configure_origin.pp

i.         oo-register-dns --domain example.com --with-node-hostname broker --with-node-ip <broker IP public ip>

j.        reboot

 

 

Not Sure what I am missing here-Please share some pointers .I am sure this would have been tried and tested

oo-accept-broker fails with the following error:

 

FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/api

FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/cartridges

FAIL: Did not get expected HTTP 401 response from https://localhost/broker/rest/user

FAIL: Did not get expected HTTP 401 response from https://localhost/broker/rest/domains

 

 

I was able to get OSE in aws using the bash script without much hassle.Have a critical requirement to try some deployment in Origin but this is acting a showstopper

Thanks for the support.

 

 

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

 

 


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