How to update OpenShift Cartridge with oo-admin-upgrade? -


i have application running in openshift origin. has been running time , have update cartridge uses.

when try update cartridge, script fails.

[root@broker ~]# oo-admin-upgrade --upgrade-node node1 --login admin --app-name app1 --version 1.0 --upgrade-gear 52231466a6577a242f00015d /usr/sbin/oo-admin-upgrade:76:in `rescue in upgrade_gear': can supply discovery data if direct_addressing enabled (runtimeerror) ["/opt/rh/ruby193/root/usr/share/ruby/mcollective/rpc/client.rb:438:in `discover'", "/opt/rh/ruby193/root/usr/share/gems/gems/openshift-origin-msg-broker-mcollective-1.13.0.1/lib/openshift/mcollective_application_container_proxy.rb:2173:in `rpc_exec'", "/usr/sbin/oo-admin-upgrade:49:in `block in upgrade_gear'", "/opt/rh/ruby193/root/usr/share/ruby/timeout.rb:69:in `timeout'", "/usr/sbin/oo-admin-upgrade:41:in `upgrade_gear'", "/usr/sbin/oo-admin-upgrade:611:in `<main>'"] output: migrating gear on node with: /usr/sbin/oo-admin-upgrade --login 'admin' --upgrade-gear '52231466a6577a242f00015d' --app-name 'app1' --version '1.0'  upgrading on node...     /usr/sbin/oo-admin-upgrade:24:in `upgrade_gear'     /usr/sbin/oo-admin-upgrade:611:in `<main>' 

do wrong or bug in script?

i believe you're 1 of first people attempting use oo-admin-upgrade in origin installation. looks mcollective command node upgrade gear timed out. please make sure mcollective correctly configured running 'mco ping' - should see responses nodes in cluster.

that said, upgrade-node option not designed used end-users. please use:

oo-admin-upgrade --version 1.0 

this should apply upgrades apps in cluster.


Comments

Popular posts from this blog

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

html - How to style widget with post count different than without post count -

url rewriting - How to redirect a http POST with urlrewritefilter -