Description of problem: when you try to download the logs file you get: Download logs failed Error attempting an operation on container: Container GET failed: https://192.168.24.2:13808/v1/AUTH_1c59567439864ec5a6f1b97bc9ca82df/tripleo-ui-logs?format=json 404 Not Found [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.< Version-Release number of selected component (if applicable): 2018-11-06.3 puddle How reproducible: 100% Steps to Reproduce: 1.install osp14 via a customized job with a breakpoint before deployment 2.log in 3.press the question mark at the top of the page 4.press 'DEBUG' button 5.press 'download logs'
The tripleo-ui-logs container is missing in swift
openstack workflow execution output show 79bd90d9-b19f-4318-b8fb-f100153552f6 { "status": "FAILED", "message": "Error attempting an operation on container: Container GET failed: https://192.168.122.38:13808/v1/AUTH_53406fd7b3a54a7c90b8006321f88994/tripleo-ui-logs?format=json 404 Not Found [first 60 chars of response] <html><h1>Not Found</h1><p>The resource could not be found.<", "result": "Failure caused by error in tasks: send_message\n\n send_message [task_ex_id=2b7aa476-62e4-4278-b901-4ab0af01ad95] -> Workflow failed due to message status\n [wf_ex_id=c9a90f77-3fb3-4a8b-a021-0e26d0f4b3fb, idx=0]: Workflow failed due to message status\n" }
Verified. (undercloud) [stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed 14 -p 2018-12-04.4 [stack@undercloud-0 ~]$ rpm -q openstack-tripleo-common openstack-tripleo-common-9.4.1-0.20181012010882.el7ost.noarch (undercloud) [stack@undercloud-0 ~]$ sudo docker exec -ti tripleo_ui bash ()[root@undercloud-0 /]# rpm -q openstack-tripleo-ui openstack-tripleo-ui-9.3.1-0.20180921180344.df30b55.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045