Comment 4 for bug 1813635

I could, finally, get a success application-apply, however the behaviour is odd.

After adding the 192.168.204.2 IP into the NO_PROXY variable, the download of images started, however, the apply process failed as some images weren't downloaded:

2019-01-28 18:07:56.558 11851 ERROR sysinv.conductor.kube_app [-] Deployment of application stx-openstack failed: failed to download one or more image(s).
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app Traceback (most recent call last):
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/conductor/kube_app.py", line 898, in perform_app_apply
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app self._download_images(app)
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/conductor/kube_app.py", line 471, in _download_images
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app reason="failed to download one or more image(s).")
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app KubeAppApplyFailure: Deployment of application stx-openstack failed: failed to download one or more image(s).
2019-01-28 18:07:56.558 11851 TRACE sysinv.conductor.kube_app
2019-01-28 18:07:56.562 11851 ERROR sysinv.conductor.kube_app [-] Application apply aborted!.
2019-01-28 18:11:21.426 12613 INFO sysinv.api.controllers.v1.host [-] controller-0 ihost_patch_start_2019-01-28-18-11-21 patch
2019-01-28 18:11:21.427 12613 INFO sysinv.api.controllers.v1.host [-] controller-0 ihost_patch_end. No changes from mtce/1.0.
2019-01-28 18:14:05.437 11851 INFO sysinv.conductor.kube_app [-] Application (stx-openstack) apply started.

Running again 'system applycation-apply stx-openstack' and without any change, the images were downloaded and the progress reached the 42%:

2019-01-28 18:18:00.475 11851 INFO sysinv.conductor.kube_app [-] processing chart: osh-openstack-rabbitmq, overall completion: 32.0%
2019-01-28 18:18:35.551 11851 INFO sysinv.conductor.kube_app [-] processing chart: osh-openstack-keystone, overall completion: 37.0%
2019-01-28 18:19:49.370 11851 INFO sysinv.conductor.kube_app [-] processing chart: osh-openstack-glance, overall completion: 42.0%

But it failed later:

2019-01-28 18:49:52.400 11851 ERROR sysinv.conductor.kube_app [-] Application apply aborted!.
(There's a lot of log here, so i'm not sure what to paste, the complete file is attached anyway)

Then, running the command again caused a successful application-apply.

+---------------+-----------------+------------------------+---------+-----------+
| application | manifest name | manifest file | status | progress |
+---------------+-----------------+------------------------+---------+-----------+
| stx-openstack | armada-manifest | manifest-no-tests.yaml | applied | completed |
+---------------+-----------------+------------------------+---------+-----------+

Questions:

- It is normal to not get an applied application at the first attempt?
- If the apply fails, which log would be more helpful to debug the issue?
- Are the pod logs useful?