Openstack 14.04 JUJU服务升级后大多失败
Openstack 14.04 JUJU服务升级后大多失败
提问于 2016-10-14 12:15:31
从我最初构建openstack云到现在已经有几个月了，尽管我的判断更好，我还是在节点上运行了sudo apt-get update ; sudo apt-get upgrade。馊主意。
nagios报告说，在重新启动时，一切看起来都很正常，但是当我启动我的实例时，没有一个实例能够获得IP。所以当我开始研究中子的时候，我看到了巨巨数吨的错误。我甚至不知道该从哪里开始。
当节点升级时，他们问我一些配置更改，我选择了(N)进行任何修改。我猜这就是问题所在吧？
landscape@juju-machine-0-lxc-1:~$ juju status --format=tabular
[Services]
NAME STATUS EXPOSED CHARM
base-machine error false cs:trusty/ubuntu-6
ceilometer active false cs:trusty/ceilometer-171
ceilometer-agent false cs:trusty/ceilometer-agent-167
ceph-mon active false cs:~openstack-charmers-next/trusty/ceph-mon-137
ceph-osd active false cs:trusty/ceph-osd-169
ceph-radosgw active false cs:trusty/ceph-radosgw-173
cinder error false cs:trusty/cinder-188
glance active false cs:trusty/glance-185
keystone active false cs:trusty/keystone-253
landscape-client false cs:trusty/landscape-client-12
mongodb unknown false cs:trusty/mongodb-35
mysql active false cs:trusty/percona-cluster-178
nagios unknown false cs:trusty/nagios-10
neutron-api active false cs:trusty/neutron-api-177
neutron-gateway error false cs:trusty/neutron-gateway-163
neutron-openvswitch false cs:trusty/neutron-openvswitch-169
nova-cloud-controller active false cs:trusty/nova-cloud-controller-220
nova-compute error false cs:trusty/nova-compute-190
nrpe false cs:trusty/nrpe-7
ntp false cs:trusty/ntp-15
ntpmaster unknown false cs:trusty/ntpmaster-2
openstack-dashboard active false cs:trusty/openstack-dashboard-175
rabbitmq-server error false cs:trusty/rabbitmq-server-43
[Units]
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
base-machine/0 error idle 1.25.6 0 node01.maas hook failed: "leader-elected"
landscape-client/0 unknown idle 1.25.6 node01.maas
ntp/0 unknown idle 1.25.6 node01.maas
base-machine/1 unknown idle 1.25.6 2 node02.maas
landscape-client/9 unknown idle 1.25.6 node02.maas
ntp/1 error idle 1.25.6 node02.maas hook failed: "leader-elected"
base-machine/2 unknown idle 1.25.6 1 node03.maas
landscape-client/10 unknown idle 1.25.6 node03.maas
ntp/2 unknown idle 1.25.6 node03.maas
ceilometer/0 active idle 1.25.6 0/lxc/2 8777/tcp 10.14.0.47 Unit is ready
landscape-client/5 unknown idle 1.25.6 10.14.0.47
nrpe/4 unknown idle 1.25.6 10.14.0.47
ceph-mon/0 active idle 1.25.6 0/lxc/4 10.14.0.53 Unit is ready and clustered
landscape-client/2 unknown idle 1.25.6 10.14.0.53
nrpe/1 unknown idle 1.25.6 10.14.0.53
ceph-mon/1 active idle 1.25.6 2/lxc/4 10.14.0.60 Unit is ready and clustered
landscape-client/14 unknown idle 1.25.6 10.14.0.60
nrpe/10 unknown idle 1.25.6 10.14.0.60
ceph-mon/2 active idle 1.25.6 1/lxc/0 10.14.0.62 Unit is ready and clustered
landscape-client/19 unknown idle 1.25.6 10.14.0.62
nrpe/13 unknown idle 1.25.6 10.14.0.62
ceph-osd/0 active idle 1.25.6 0 node01.maas Unit is ready (2 OSD)
landscape-client/1 unknown idle 1.25.6 node01.maas
nrpe/0 unknown idle 1.25.6 node01.maas
ceph-osd/1 active idle 1.25.6 2 node02.maas Unit is ready (5 OSD)
landscape-client/11 unknown idle 1.25.6 node02.maas
nrpe/8 unknown idle 1.25.6 node02.maas
ceph-osd/2 active idle 1.25.6 1 node03.maas Unit is ready (5 OSD)
landscape-client/12 unknown idle 1.25.6 node03.maas
nrpe/9 error idle 1.25.6 node03.maas hook failed: "config-changed"
ceph-radosgw/0 active idle 1.25.6 2/lxc/0 80/tcp 10.14.0.56 Unit is ready
landscape-client/16 unknown idle 1.25.6 10.14.0.56
cinder/0 error idle 1.25.6 1/lxc/2 10.14.0.64 hook failed: "update-status"
landscape-client/22 unknown idle 1.25.6 10.14.0.64
nrpe/16 unknown idle 1.25.6 10.14.0.64
glance/0 active idle 1.25.6 0/lxc/5 9292/tcp 10.14.0.54 Unit is ready
landscape-client/4 unknown idle 1.25.6 10.14.0.54
nrpe/3 unknown idle 1.25.6 10.14.0.54
keystone/0 active idle 1.25.6 2/lxc/2 10.14.0.58 Unit is ready
landscape-client/18 unknown idle 1.25.6 10.14.0.58
nrpe/12 unknown idle 1.25.6 10.14.0.58
mongodb/0 unknown idle 1.25.6 1/lxc/3 27017/tcp,27019/tcp,27021/tcp,28017/tcp 10.14.0.65
landscape-client/20 unknown idle 1.25.6 10.14.0.65
nrpe/14 unknown idle 1.25.6 10.14.0.65
mysql/0 active idle 1.25.6 0/lxc/1 10.14.0.50 Unit is ready
landscape-client/7 unknown idle 1.25.6 10.14.0.50
nrpe/6 unknown idle 1.25.6 10.14.0.50
nagios/0 unknown idle 1.25.6 2/lxc/3 80/tcp 10.14.0.59
landscape-client/15 unknown idle 1.25.6 10.14.0.59
neutron-api/0 active idle 1.25.6 1/lxc/4 9696/tcp 10.14.0.66 Unit is ready
landscape-client/23 unknown idle 1.25.6 10.14.0.66
nrpe/17 unknown idle 1.25.6 10.14.0.66
neutron-gateway/0 error idle 1.25.6 0 node01.maas hook failed: "config-changed"
landscape-client/6 unknown idle 1.25.6 node01.maas
nrpe/5 unknown idle 1.25.6 node01.maas
nova-cloud-controller/0 active idle 1.25.6 0/lxc/0 3333/tcp,8773/tcp,8774/tcp,9696/tcp 10.14.0.49 Unit is ready
landscape-client/8 unknown idle 1.25.6 10.14.0.49
nrpe/7 unknown idle 1.25.6 10.14.0.49
nova-compute/0 error idle 1.25.6 2 node02.maas hook failed: "update-status"
ceilometer-agent/0 active idle 1.25.6 node02.maas Unit is ready
landscape-client/17 unknown idle 1.25.6 node02.maas
neutron-openvswitch/0 active idle 1.25.6 node02.maas Unit is ready
nrpe/11 unknown idle 1.25.6 node02.maas
nova-compute/1 error idle 1.25.6 1 node03.maas hook failed: "update-status"
ceilometer-agent/1 active idle 1.25.6 node03.maas Unit is ready
landscape-client/21 unknown idle 1.25.6 node03.maas
neutron-openvswitch/1 active idle 1.25.6 node03.maas Unit is ready
nrpe/15 unknown idle 1.25.6 node03.maas
ntpmaster/0 unknown idle 1.25.6 2/lxc/1 123/udp 10.14.0.57
landscape-client/13 unknown idle 1.25.6 10.14.0.57
openstack-dashboard/0 active idle 1.25.6 1/lxc/1 80/tcp,443/tcp 10.14.0.63 Unit is ready
landscape-client/24 unknown idle 1.25.6 10.14.0.63
nrpe/18 unknown idle 1.25.6 10.14.0.63
rabbitmq-server/0 error idle 1.25.6 0/lxc/3 5672/tcp 10.14.0.52 hook failed: "update-status"
landscape-client/3 unknown idle 1.25.6 10.14.0.52
nrpe/2 unknown idle 1.25.6 10.14.0.52
[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.25.6 node01.maas /MAAS/api/1.0/nodes/node-be8673ca-1d31-11e6-a83b-0015c5efa6ff/ trusty arch=amd64 cpu-cores=8 mem=32768M
1 started 1.25.6 node03.maas /MAAS/api/1.0/nodes/node-b672c22e-1d31-11e6-82b6-0015c5efa6ff/ trusty arch=amd64 cpu-cores=8 mem=32768M
2 started 1.25.6 node02.maas /MAAS/api/1.0/nodes/node-ba12aac0-1d31-11e6-89e9-0015c5efa6ff/ trusty arch=amd64 cpu-cores=8 mem=32768M 回答 1
Ask Ubuntu用户
发布于 2016-10-14 21:10:32
如果OpenStack群集处于关闭状态，并且在错误或阻塞状态中显示多个魅力单元，请运行以下步骤将群集恢复。
- 确保节点与互联网之间的连接。
- 互联网连接是需要的，因为钩子将重新运行时，单位将得到解决。大多数魅力挂钩运行命令，如apt-get更新，这需要互联网连接。
- 如果juju命令被卡住，那么重新启动juju控制器/引导节点，或者重新启动该节点上的juju-*服务。
- 如果您面临任何“代理丢失”错误，那么在这些节点/容器中重新启动jujud单元魅力名称单元服务。
- 解析处于错误状态的魅力单元。
- $ juju解决了-重试符咒名称/单位，这将重新运行钩子，最初失败。按以下顺序解析魅力单元：
- mysql
- 要点
- rabbitmq-服务器
- 卡夫
- 斯威夫特
- 新星云控制器
- 煤渣
- 一瞥
- 中子api
- 中子网关
- 新计算
- openstack-仪表板
- $ juju解决了-重试符咒名称/单位，这将重新运行钩子，最初失败。按以下顺序解析魅力单元：
- In case resolving the units does not help then look into the juju logs to see what the error is and try resolving it manually. Make sure you have all units in an active state. - 确认集群已备份
- 登录到地平线并检查所有服务都处于活动状态。
- 启动所有OpenStack实例，并确保卷和网络配置正确。
页面原文内容由Ask Ubuntu提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://askubuntu.com/questions/836974
复制相关文章
相似问题
腾讯云开发者
Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有
深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 
粤公网安备44030502008569号
腾讯云计算（北京）有限责任公司 京ICP证150476号 | 京ICP备11018762号