Bug 732331
| Summary: | The job cloned by webui could submit successfully and no warning when task is not applicable for distro | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | yanfu,wang <yanwang> |
| Component: | web UI | Assignee: | Raymond Mancy <rmancy> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 0.6 | CC: | bpeck, dcallagh, ebaak, mcsontos, mishin, rmancy, stl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-01 05:14:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
yanfu,wang
2011-08-22 02:53:40 UTC
I'd like to get away from beaker doing the task filtering. Right now we filter in two places. 1 - When you run the bkr workflow-simple command it queries the scheduler for what tasks apply to that distro. Then gives you the warning that you mentioned. 2 - Filtering at step 1 is new, before that we filtered at submission time. This is where the cloning comes in and it simply strips the wrong tasks without giving you a warning. We have always planned to remove the filtering at step 2. If you tell beaker to do something via the xml it should just do it. This allows the filtering to be done in something else like TCMS. I hope this makes sense. (In reply to comment #1) > I'd like to get away from beaker doing the task filtering. Right now we filter > in two places. > > 1 - When you run the bkr workflow-simple command it queries the scheduler for > what tasks apply to that distro. Then gives you the warning that you > mentioned. > > 2 - Filtering at step 1 is new, before that we filtered at submission time. > This is where the cloning comes in and it simply strips the wrong tasks without > giving you a warning. > > We have always planned to remove the filtering at step 2. If you tell beaker > to do something via the xml it should just do it. This allows the filtering to > be done in something else like TCMS. > > > I hope this makes sense. Thank you for your reply. I would like to state my feeling from QE usage. First, I don't use TCMS and I just run job depend on beaker. If I run the job via xml and filtering do as step 2, I or others QE might mistakenly believe that the result is passed since the result return PASS, but in fact no our task included to run. This problem is likely to occur if a great mass of jobs to be scheduled. Second, I think run by xml in web-ui should consistent with command line way from user experience at least. My understand may wrong but still hope some improvement to be done :-) Thank you. As Bill mentioned in comment 1, if you give Beaker job XML to run it accepts it as is. We are trying to get Beaker out of the business of deciding what tests to run when, and managing the associated metadata. Those decisions should be made by external tools when submitting jobs to Beaker (for example workflow-tomorrow which talks to TCMS). |