action #94174
open
action #94090: [qe-core][qac][study] End-to-end combination test scenarios
[opensuse] Enable k3s and Rancher tests in openqa.suse.de
Added by szarate about 3 years ago.
Updated 3 months ago.
Description
The schedule atm for Tumbleweed and Leap is being managed at https://github.com/pdostal/qe-rancher, we could deploy/port this to a different CI that would take care of scheduling on both places if needed?.
What we need is to bring this to osd for the time being on the last SP, and at the product level too under it's own job group (that matches those on TW).
we might need to re-discuss this. I am in contact with the team that tests specifically Rancher (rke2, k3s, rke) in various operating systems (RHEL, Ubuntu, SLES) [1].
I am trying that we don't duplicate QA effort and try to separate responsibilities with both departments. Please hold on this task until we have better clearance. In any case, I guess this is container space, so we should discuss about this task. I am a bit surprise to find these plans from your team without first contacting our team which is one of main's responsibilities is containers...
[1] https://geekos.prv.suse.net/team/5ffcb3d12641e42e16bf7880
Hi. This ticket was the only one that was part of the ticket category "Scheduling". I don't know who created that ticket category which was not documented on https://progress.opensuse.org/projects/openqatests/wiki#ticket-workflow . Also I see the category as a bad choice because it's orthogonal to existing categories like "New test" or "Bugs in existing tests". So I removed the category and moved the ticket to "New Tests" instead as this is for new test coverage.
okurz wrote:
Hi. This ticket was the only one that was part of the ticket category "Scheduling". I don't know who created that ticket category which was not documented on https://progress.opensuse.org/projects/openqatests/wiki#ticket-workflow . Also I see the category as a bad choice because it's orthogonal to existing categories like "New test" or "Bugs in existing tests". So I removed the category and moved the ticket to "New Tests" instead as this is for new test coverage.
Hi Oliver, I created the category a while ago, would you undo the change? as a New test is not the same as changes in schedules.I'll take care of documenting the category later
Can we please only use orthogonal categories? A ticket in "scheduling" could be "bug in existing tests" and vice versa, right? Discussions with project managers showed that the categories "bugs in existing tests" and "new tests" and "enhancements" are helpful, the others not so much. If you insist I will create the category again
okurz wrote:
Can we please only use orthogonal categories? A ticket in "scheduling" could be "bug in existing tests" and vice versa, right? Discussions with project managers showed that the categories "bugs in existing tests" and "new tests" and "enhancements" are helpful, the others not so much. If you insist I will create the category again
I'll insist in this case, because PM are not the only persons who can benefit from having a distinction between ticket categories. However I'll note your comment for future iterations.
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Also available in: Atom
PDF