ceph-mon failed going disabled. Which failed the swact. No logs were found to tell what went wrong with ceph-mon.
A separated issue, dbmon was running fine after stx-openstack was applied around 08:10, then it started failing after reapplying stx-openstack, the reapply apparently was not successful and sysinv reported that the stx-openstack as "not applied".
This result does not match what was expected as a failed reapply would not change the fact that the application is applied and running with latest successful apply. The dbmon continue running but it lose access to the mariadb pod and other resources, so it report failure since the reapply.
2019-07-10 08:10:05.824 110608 INFO sysinv.conductor.kube_app [-] Application stx-openstack (1.0-17-centos-stable-versioned) apply completed.
...
2019-07-10 11:01:21.802 110608 INFO sysinv.conductor.kube_app [-] Application stx-openstack (1.0-17-centos-stable-versioned) apply started.
2019-07-10 11:08:37.690 110608 ERROR sysinv.conductor.kube_app [-] Failed to apply application manifest /manifests/stx-openstack/1.0-17-centos-stable-versioned/stx-openstack-stx-openstack.yaml. See /var/log/armada stx-openstack-apply.log for details.
2019-07-10 11:08:37.696 110608 INFO sysinv.conductor.kube_app [-] Exiting progress monitoring thread for app stx-openstack
2019-07-10 12:17:52.178 228896 INFO sysinv.api.controllers.v1.host [-] stx-openstack system app is present but not applied, skipping re-apply
| 2019-07- 10T11:24: 29.997 | 312 | node-scn | controller-0 | | swact | issued against host controller-0
| 2019-07- 10T11:25: 35.026 | 451 | service-group-scn | controller-services | disabling | disabling-failed | ceph-mon(disabling, failed) 10T11:25: 38.863 | 455 | service-group-scn | vim-services | disabled | go-active | 10T11:25: 38.864 | 456 | service-group-scn | cloud-services | disabled | go-active |
| 2019-07-
| 2019-07-
ceph-mon failed going disabled. Which failed the swact. No logs were found to tell what went wrong with ceph-mon.
A separated issue, dbmon was running fine after stx-openstack was applied around 08:10, then it started failing after reapplying stx-openstack, the reapply apparently was not successful and sysinv reported that the stx-openstack as "not applied".
This result does not match what was expected as a failed reapply would not change the fact that the application is applied and running with latest successful apply. The dbmon continue running but it lose access to the mariadb pod and other resources, so it report failure since the reapply.
2019-07-10 08:10:05.824 110608 INFO sysinv. conductor. kube_app [-] Application stx-openstack (1.0-17- centos- stable- versioned) apply completed. conductor. kube_app [-] Application stx-openstack (1.0-17- centos- stable- versioned) apply started. conductor. kube_app [-] Failed to apply application manifest /manifests/ stx-openstack/ 1.0-17- centos- stable- versioned/ stx-openstack- stx-openstack. yaml. See /var/log/armada stx-openstack- apply.log for details. conductor. kube_app [-] Exiting progress monitoring thread for app stx-openstack api.controllers .v1.host [-] stx-openstack system app is present but not applied, skipping re-apply
...
2019-07-10 11:01:21.802 110608 INFO sysinv.
2019-07-10 11:08:37.690 110608 ERROR sysinv.
2019-07-10 11:08:37.696 110608 INFO sysinv.
2019-07-10 12:17:52.178 228896 INFO sysinv.
| 2019-07- 10T08:11: 06.772 | 290 | service-scn | dbmon | unknown | enabled-active | audit success 10T11:05: 46.432 | 295 | service-scn | dbmon | enabled-active | disabling | audit failed
| 2019-07-
...