New commit detected on ManageIQ/manageiq-ui-classic/fine: https://github.com/ManageIQ/manageiq-ui-classic/commit/ca348c4761ab68f771ab59d3ac62905dd69b55f8 commit ca348c4761ab68f771ab59d3ac62905dd69b55f8 Author: Dan Clarizio <dclarizi> AuthorDate: Wed Apr 12 08:06:11 2017 -0700 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Apr 13 14:12:14 2017 -0400 Merge pull request #1018 from yaacov/add-hint-to-check-hawkular-when-error-originate-form-the-hawkular-client Add hint to check Hawkular when error originates from the Hawkular cl… (cherry picked from commit 55300f34e7f4292e7fa577b9c24c7cda9848d890) https://bugzilla.redhat.com/show_bug.cgi?id=1442167 app/services/hawkular_proxy_service.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Hello Yaacov, This BZ seems to have been handled extensively. However, I do not understand how it would be possible to reproduce it. Can you please describe steps to reproduce? Einat
> However, I do not understand how it would be possible to reproduce it. Whooo that a hard question ... You will need a malfunction Hawkular [1], if Hawkular does "504 Gateway Time-out" , and users may think the problem is with CFME, but in fact they have to check their Hawkular. Bug: you will get an error message that say "504 Gateway Time-out" Fix: you will get an error message that say "Gateway Time-out (please check your hawkular server)" [1] We can simulate negative flows like that using the MoHawk server, that is built especially for simulating errors in Hawkular and large scale databases. backported to fine https://github.com/ManageIQ/manageiq-ui-classic/pull/1018
Moving back to ON_QA. Yaacov should stopping hawakular's pod show this error message?
> should stopping hawakular's pod show this error message? no, but it will show a different one ...
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/RHSA-2017:1367