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

OpenshiftOrigin DNS Problem



Good Morning!

 

This is a long email…. I can’t get openshift to update DNS properly so apps create, but then you can’t reach them, and you can’t remove them easily.

 

I’m trying out this openshift origin and I used puppet to configure everything on a single host.  This including, dns, node, broker, etc…  When deploying an application I run into a problem, the web interface reports we are undergoing maintenance…  Looking at the broker/production.log:

 

2014-03-18 10:07:21.738 [INFO ] Started POST "/broker/rest/domain/jskarbek/applications.json" for 127.0.0.1 at 2014-03-18 10:07:21 -0400 (pid:2598)

2014-03-18 10:07:21.808 [INFO ] Processing by ApplicationsController#create as JSON (pid:2598)

2014-03-18 10:07:21.812 [INFO ] Parameters: {"cartridges"=>["nodejs-0.10"], "domain_id"=>"jskarbek", "gear_profile"=>"small", "initial_git_url"=>"", "name"=>"nodejs2", "scale"=>"false"} (pid:2598)

2014-03-18 10:07:29.429 [ERROR] Invlaid CNAME 'nodejs2-jskarbek.apps.domain.com' (pid:2598)

<SNIP>

2014-03-18 10:07:29.653 [ERROR] Reference ID: a0bb10a1f4d8aed5e83cf90313b8bc18 - Invlaid CNAME 'nodejs2-jskarbek.apps.nextcentury.com'

<SNIP>

  /usr/share/gems/gems/passenger-3.0.21/helper-scripts/passenger-spawn-server:102:in `<main>' (pid:2598)

2014-03-18 10:07:29.658 [INFO ] Completed 503 Service Unavailable in 8576.9ms (Views: 1.0ms) (pid:2598)

 

Which sucks, cuz the app will create, dns will fail as an entry is not added, and then you can’t delete the app using the web interface because it can’t resolve dns.  But here’s what’s in the messages file:

 

Mar 18 10:07:29 osb avahi-cname-manager[7118]: 192.168.1.1 - - [18/Mar/2014 10:07:29] "POST /add_alias HTTP/1.1" 400 53 0.0014

Mar 18 10:07:29 osb avahi-cname-manager[7118]: osb.domain.com - - [18/Mar/2014:10:07:29 EDT] "POST /add_alias HTTP/1.1" 400 53

Mar 18 10:07:29 osb avahi-cname-manager[7118]: - -> /add_alias

Mar 18 10:07:29 osb avahi-cname-manager[7118]: 192.168.1.1  - - [18/Mar/2014 10:07:29] "POST /remove_alias HTTP/1.1" 400 53 0.0009

Mar 18 10:07:29 osb avahi-cname-manager[7118]: osb.domain.com - - [18/Mar/2014:10:07:29 EDT] "POST /remove_alias HTTP/1.1" 400 53

Mar 18 10:07:29 osb avahi-cname-manager[7118]: - -> /remove_alias

 

Those 400 returns are probably the reason why, but I have no clue how to troubleshoot this because I don’t know how this DNS is all rolled together.

 

oo-diag reports a couple of things that are awkward:

 

[root osb ~]# oo-diagnostics

/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:98: warning: already initialized constant Psych::VERSION

/usr/share/ruby/vendor_ruby/psych.rb:98: warning: previous definition of VERSION was here

/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:101: warning: already initialized constant Psych::LIBYAML_VERSION

/usr/share/ruby/vendor_ruby/psych.rb:101: warning: previous definition of LIBYAML_VERSION was here

WARN: test_node_profiles_districts_from_broker

        No districts are defined. Districts should be used in any production installation.

        Please consult the Administration Guide.

 

FAIL: run_script

oo-accept-node had errors:

--BEGIN OUTPUT--

FAIL: Could not get SELinux context for mcollective

FAIL: Could not get SELinux context for oddjobd

FAIL: tc htb qdisc not configured

FAIL: directory 5328531986e5798ff3000002 doesn't have a cartridge directory

FAIL: directory 532851bf86e5791d6d000045 doesn't have a cartridge directory

FAIL: directory 5328518e86e5791d6d00002f doesn't have a cartridge directory

6 ERRORS

 

--END oo-accept-node OUTPUT--

sed: can't read /var/log/mcollective.log: No such file or directory

WARN: test_broker_certificate

Using a self-signed certificate for the broker

grep: /etc/httpd/conf.d/openshift: Is a directory

WARN: block (2 levels) in test_broker_certificate

            /etc/httpd/conf.d/000002_openshift_origin_broker_servername.conf

            defines ServerName as osb.apps.nextcentury.com.  This does not match the certificate common name of

            osb.hq.nextcentury.com.

            This can cause errors when client tools try to connect to the broker.

 

3 WARNINGS

1 ERRORS

 

And the below is my puppet config that deployed this single host:

 

class { 'openshift_origin':

  domain                     => 'apps.nextcentury.com',

  roles                      => [

    'broker',

    'node',

    'activemq',

    'datastore',

    'named',

  ],

  broker_hostname            => 'osb.apps.domain.com',

  node_hostname              => 'osb.apps.domain.com',

  named_hostname             => 'osb.apps.domain.com',

  activemq_hostname          => 'osb.apps.domain.com',

  datastore_hostname         => 'osb.apps.domain.com',

  named_ip_addr              => $ipaddress,

  broker_ip_addr             => $ipaddress,

  node_ip_addr               => $ipaddress,

  conf_named_upstream_dns    => [

    ‘192.168.1.2’,

    ‘192.168.1.3’,

    $ipaddress,

  ],

  node_unmanaged_users       => [ 'root', ],

  development_mode           => true,

  conf_node_external_eth_dev => 'eth0',

  install_method             => 'yum',

  install_login_shell        => true,

  register_host_with_named   => true,

  broker_auth_plugin         => 'htpasswd',

  broker_dns_plugin          => 'avahi',

  jenkins_repo_base          => 'http://pkg.jenkins-ci.org/redhat',

  bind_key                   => "Abagu+ub1SDFS9n5cig==",

  activemq_admin_password    => 'scrambled',

  install_cartridges         => [

    'cron',

    'jenkins',

    'nodejs',

    'jbossas',

  ],

}

 

Any advice is appreciated!

 

John Skarbek, System Administrator 

 


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