티스토리 뷰
TripleO를 통한 overcloud deploy시 에러현상
2017-03-21 08:45:07 [ControllerOvercloudServicesDeployment_Step6]: UPDATE_IN_PROGRESS state changed
2017-03-21 08:45:07 [overcloud-ControllerNodesPostDeployment-cdoooh2h6xpk-ControllerOvercloudServicesDeployment_Step6-gikl7tsipgjw]: UPDATE_IN_PROGRESS Stack UPDATE started
2017-03-21 08:45:07 [2]: UPDATE_IN_PROGRESS state changed
2017-03-21 08:45:08 [1]: UPDATE_IN_PROGRESS state changed
2017-03-21 08:45:08 [0]: UPDATE_IN_PROGRESS state changed
2017-03-21 08:46:05 [2]: SIGNAL_IN_PROGRESS Signal: deployment succeeded
2017-03-21 08:46:06 [2]: UPDATE_COMPLETE state changed
2017-03-21 08:46:30 [1]: SIGNAL_IN_PROGRESS Signal: deployment succeeded
2017-03-21 08:46:30 [1]: UPDATE_COMPLETE state changed
2017-03-21 08:46:41 [0]: SIGNAL_IN_PROGRESS Signal: deployment succeeded
2017-03-21 08:46:42 [0]: UPDATE_COMPLETE state changed
2017-03-21 08:46:43 [ControllerOvercloudServicesDeployment_Step6]: UPDATE_COMPLETE state changed
2017-03-21 08:46:43 [overcloud-ControllerNodesPostDeployment-cdoooh2h6xpk-ControllerOvercloudServicesDeployment_Step6-gikl7tsipgjw]: UPDATE_COMPLETE Stack UPDATE completed successfully
2017-03-21 08:46:44 [ControllerPostPuppet]: UPDATE_IN_PROGRESS state changed
2017-03-21 08:46:44 [overcloud-ControllerNodesPostDeployment-cdoooh2h6xpk-ControllerPostPuppet-fvjqh6eqmany]: UPDATE_IN_PROGRESS Stack UPDATE started
2017-03-21 08:46:46 [ControllerPostPuppetMaintenanceModeDeployment]: UPDATE_IN_PROGRESS state changed
2017-03-21 08:47:32 [ControllerPostPuppetMaintenanceModeDeployment]: UPDATE_COMPLETE state changed
2017-03-21 08:47:32 [ControllerPostPuppetRestartDeployment]: UPDATE_IN_PROGRESS state changed
2017-03-21 09:18:12 [ControllerPostPuppetRestartDeployment]: UPDATE_FAILED resources.ControllerPostPuppetRestartDeployment: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1
2017-03-21 09:18:13 [overcloud-ControllerNodesPostDeployment-cdoooh2h6xpk-ControllerPostPuppet-fvjqh6eqmany]: UPDATE_FAILED resources.ControllerPostPuppetRestartDeployment: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1
2017-03-21 09:18:15 [ControllerPostPuppet]: UPDATE_FAILED resources.ControllerPostPuppet: resources.ControllerPostPuppetRestartDeployment: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1
2017-03-21 09:18:16 [overcloud-ControllerNodesPostDeployment-cdoooh2h6xpk]: UPDATE_FAILED resources.ControllerPostPuppet: resources.ControllerPostPuppetRestartDeployment: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1
Stack overcloud UPDATE_FAILED
Deployment failed: Heat Stack update failed.
pcs resource op defaults timeout=60s
이후 정상적으로 배포되었다.
실제 아래의 pacemaker_resource_restart.sh 스크립트가 수행되면서 발생되는 문제로 보여졌으며
원인은 좀더 확인해보아야할것같다.
'Cloud > Private Cloud' 카테고리의 다른 글
blk_update_request I/O error (0) | 2017.04.14 |
---|---|
install vlc player on redhat linux (0) | 2017.04.06 |
occur QEMU error when volume attach (0) | 2017.03.14 |
openstack undercloud install error (0) | 2017.03.06 |
problem for hanging VM when it is started (0) | 2017.01.08 |
- Total
- Today
- Yesterday
- openstack backup
- ansible
- mattermost
- aquasecurity
- azure policy
- minio
- openstacksdk
- kubernetes install
- vmware openstack
- OpenStack
- nginx-ingress
- GateKeeper
- Jenkinsfile
- macvlan
- DevSecOps
- crashloopbackoff
- kata container
- hashicorp boundary
- kubernetes
- metallb
- socket
- K3S
- Terraform
- jenkins
- Helm Chart
- wsl2
- open policy agent
- boundary ssh
- minikube
- ceph
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |