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

Re: AW: No nodes available

Ahhhh, right. oo-install does give the impression it can change things after the fact sometimes, but that's not really the case. It can only really change the definitions before something is installed, or add wholly new hosts to an existing install. Sorry about that!

Changing the profile on a node is unfortunately pretty involved, since you have to disable it in the district, remove it from the district (which is refused if it has any gears), then change the profile in resource_limits.conf, then finally add it to a new district. oo-install doesn't even attempt this.

----- Original Message -----
From: "Mike Michel" <mike michel mmbash de>
To: "Luke Meyer" <lmeyer redhat com>
Cc: users lists openshift redhat com
Sent: Friday, February 6, 2015 4:34:20 AM
Subject: AW: No nodes available

Meanwhile i found out that the output of oo-install-origin (see my mail before) is not the current status of OS. I had to use oo-admin-ctl-district to create profiles and districts. Then i edited every nodes /etc/openshift/resource_limits.conf to make it a medium node. Here i also thought oo-install-origin will handle it because it asked me when adding a new node which profile it should have but everything was still set to "small".

After changing it to medium i used again oo-admin-ctl-district to add the node to the district. Now i can start medium gears.

-----Ursprüngliche Nachricht-----
Von: Luke Meyer [mailto:lmeyer redhat com] 
Gesendet: Donnerstag, 5. Februar 2015 14:04
An: Mike Michel
Cc: users lists openshift redhat com
Betreff: Re: No nodes available

How did you "change the default district to medium"? There is no changing the profile for a district; you can only destroy and re-create them with the right profile. If you modify it in the DB, that will not work because all of the nodes will still have their original profile.

Here's what you need to have to use a new profile:
1. It must be listed in the set of profiles in broker.conf or broker-dev.conf (depending on mode)
  * Users must be given the capability to user the profile 2. There must be nodes that have said profile set in their /etc/openshift/resource_limits.conf
  * If nodes have already been districted with a different profile, need to remove them from district first 3. The nodes must be added to a district of the same profile.

Item 2 is rather important as, no matter what the DB says about districting, if an mcollective query looks for nodes of a certain profile and they don't have that profile or corresponding district in their mcollective facts, it won't be available for placing gears.

----- Original Message -----
From: "Mike Michel" <mike michel mmbash de>
To: users lists openshift redhat com
Sent: Sunday, February 1, 2015 6:34:55 AM
Subject: No nodes available


i just have setup a fresh install with 

Node Districts 


| District | Gear Size | Nodes |


| Default | medium | 
| node01.openshift.example.de,node02.openshift.example.de |

| medium_district | medium | node03.openshift.example.de |



oo-mco ping 

node03.openshift.example.de time=100.10 ms 

node01.openshift.example.de time=139.11 ms 

node02.openshift.example.de time=139.51 ms 

I can start „small“ apps but now i want medium gears. First i changed the defaul district to medium and after this throwed the error below when starting an medium app, i created a new district and installed a new node (node03) for it. I restarted the broker but still get the error when creating a medium app 

2015-02-01 12:19:46.395 [ERROR] Encountered error during execute 'No nodes available' (pid:6924) 

2015-02-01 12:19:46.480 [ERROR] Got Node Unavailable Exception (pid:6924) 

2015-02-01 12:19:46.480 [ERROR] Reference ID: 0ed19f33d80dd241ad3cd50032521656 - No nodes available 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective- `find_all_available_impl' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `find_available' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `reserve_uid' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `execute' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `block in execute' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `each' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `execute' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `run_jobs' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `block in add_cartridges' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `run_in_app_lock' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `add_cartridges' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `add_initial_cartridges' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `create' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/abstract_controller/base.rb:167:in `process_action' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/rendering.rb:10:in `process_action' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:18:in `block in process_action' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:481:in `block in _run__775245615909989276__process_action__517459920385376335__callbacks' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_518' 

/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-controller- `set_logged_request' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_518' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:403:in `_run__775245615909989276__process_action__517459920385376335__callbacks' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in `__run_callback' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in `_run_process_action_callbacks' 

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:17:in `process_action' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/rescue.rb:29:in `process_action' 

/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_controller/metal/instrumentation.rb:30:in `block in process_action' 


What is going wrong here? 



users mailing list
users lists openshift redhat com

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