Comment 6 for bug 1837792

Frank Miller (sensfan22) wrote :

From Anujeyan's logs the application apply started here:
2019-07-24 21:57:06.749 106112 INFO sysinv.conductor.kube_app [-] Starting progress monitoring thread for app stx-openstack

It timed-out/faiuled here:
2019-07-24 22:27:18.158 106112 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-24 22:27:18.159 106112 INFO sysinv.conductor.kube_app [-] Exiting progress monitoring thread for app stx-openstack
2019-07-24 22:27:18.175 106112 ERROR sysinv.conductor.kube_app [-] Application apply aborted!.

According to Bob Church, this seems to be the key log indicating what is failing:

neutron-dhcp-agent-compute-0-9c041f23-s7rzv_openstack_init-266eabb307aafd458f62869249a54abaa6028b4567c44a1ad2895cf3b6a112e1.log:{"log":"Entrypoint WARNING: 2019/07/24 21:57:19 entrypoint.go:71: Resolving dependency Job neutron-db-sync in namespace openstack failed: Job Job neutron-db-sync in namespace openstack is not completed yet .\n","stream":"stdout","time":"2019-07-24T21:57:19.528744365Z"}