Hide Forgot
Description of problem: I'm missing ability to search for a hostname under Watchdog page. Currently you have to go through all the pages (1,2,3,4 etc.) till you get to the system you're interested in. Using some kind of search bar would save some time and improve usability of this part of WebUI. https://beaker.engineering.redhat.com/watchdogs/
Is there any reason you are searching for a particular system on the Watchdogs page? You can find the current recipe running on a system by clicking through from the system page, or searching on the Recipes page.
Hi, the use case is that I'd like to get the current watchdog timeout value for a system I've reserved through the reserve workflow so I can evaluate whether I need to extend the watchdog timeout or I can finish my testing without it. Btw, is it possible to get the watchdog timeout value for certain system from bkr command line tool?
This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration. Please feel free to reopen the bug with additional information and/or business cases behind it.
Hi, since I provided the data requested in comment #2 and did not get an answer to my question I'm reopening this bug.
Dear Jan, I'm picking this one up. First off: is still still a valid request or do you not need it any more? If so, would you be able to elaborate on the reason as to why it is useful to you to know if you need to extend the watchdog time out? Thanks Jan!
I'd say it's still valid. I did not get any answer to my question in comment 2. Is there a user friendly way how to get this information? Second thing is the user experience perspective - Beaker WebUI provides a watchdog page where I as a user would dig for this information but when I get there, I have to go through it without any filter and that makes the watchdog page senseless in my opinion. What it should be used for then?
A simple fqdn search bar would solve the whole thing. I don't need to filter by system properties, just a hostname.
Dear Jan, currently there is no such facility to get this information unfortunately. I understand that adding a simple filter in the UI would solve the problem and we are aware of the short comings of the view. We would like to work towards a better solution than just adding filters here and there. Perhaps a solution for the client giving you the information might be better? We can't really know until we understand how you accomplish your work and how extending the watchdog time out fits in. Would you mind elaborating why you need to extend the watchdog time out? If it sounds as if I'm pulling your leg here... it's not. I'm seriously interested. Kind Regards
(In reply to Roman Joost from comment #9) > Dear Jan, > > currently there is no such facility to get this information unfortunately. I > understand that adding a simple filter in the UI would solve the problem and > we are aware of the short comings of the view. > > We would like to work towards a better solution than just adding filters > here and there. Perhaps a solution for the client giving you the information > might be better? We can't really know until we understand how you accomplish > your work and how extending the watchdog time out fits in. > Would you mind elaborating why you need to extend the watchdog time out? > > If it sounds as if I'm pulling your leg here... it's not. I'm seriously > interested. > > Kind Regards Hi, sorry for delay. The workflow is really simple. If an automated test in beaker job fails I'd clone the job and append /distribution/reservesys at the end of the recipe. I don't add RESERVETIME so the default is used. Once the system is reserved I'd login and now I ask myself. Ok, I have the machine so do I need to extend the reservation a bit or the current reservation time is enough to debug the problem? There's no easy way how to do that. I know that there are following ways how to get the info: 1. check the "Time remaining" under /distribution/reservesys in recipe URL that you get when you login into reserved system 2. check the watchdog web page I'm not really fan of webUI clicking. If adding a filter to webUI is not what you'd like to do, adding it to beaker command line client would be ok and even better.
Hello, thank you for opening issue in Beaker project. This issue was marked with component "web ui". As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX. New UI will be reimplemented within new versions of Beaker. If you have any questions feel free to reach out to me. Best regards, Martin <martin.styk>