Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Output column is blank on client view since 0.20.0 #612

Closed
br0ch0n opened this issue Dec 5, 2016 · 3 comments
Closed

Output column is blank on client view since 0.20.0 #612

br0ch0n opened this issue Dec 5, 2016 · 3 comments
Labels
Milestone

Comments

@br0ch0n
Copy link
Contributor

br0ch0n commented Dec 5, 2016

Expected Behavior

Column shows the output of each check on

Current Behavior

Column shows no output on any of the checks

Possible Solution

I suspect this happened in the refactor in sensu/uchiwa-web@c427939#diff-c050398d39586221bc1d98b55bd0a7a9 but haven't dug in enough to confirm. Would make sense since this is broken in 0.20.0

Steps to Reproduce (for bugs)

Run uchiwa 0.20.2 and look at an individual client's view (i.e. /client/(datacenter)/(clientname), not /clients which BTW works fine). If you then click on a check, the output does show up in the check view just fine.
Tested using the 0.19.0, 0.20.0 and 0.20.2 docker images.

Context

Looks fine when downgrading to 0.19.0

Your Environment

  • Uchiwa version used: 0.20.2
  • Sensu version used: 0.26.3
  • Operating System and version (e.g. Ubuntu 14.04): Ubuntu 16.04
@palourde palourde added the Bug label Dec 6, 2016
@palourde palourde added this to the 0.21.0 milestone Dec 7, 2016
@palourde palourde closed this as completed Dec 7, 2016
@br0ch0n
Copy link
Contributor Author

br0ch0n commented Dec 7, 2016

Thanks!

@halcyonardency
Copy link

Update from 0.20.2 -> 0.23.0 fixed this for us, however it wasn't working until I let the browser cache expire (took a few minutes). A simple shift-refresh didn't help and if I went into incognito mode, I could see the fix was applied. Is there a reference somewhere for what does/does not get cached by a browser? It'd be great if there was maybe a UI button to force clearing of the local browser's cache for Uchiwa, without having to go into developer tools or other hurdles. Thanks!

@palourde
Copy link
Contributor

@xyntrix We just released 0.23.1 which we hope will definitively solve any caching issues after an upgrade. Please let us know how it goes and if you still face any issue!

Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants