action #25626
closed
[sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WE
Added by SLindoMansilla over 6 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
Invalid add-on ftp url for WE
openQA test in scenario sle-15-Leanos-DVD-x86_64-we-ftp@64bit fails in
addon_products_sle
Reproducible¶
Fails since (at least) Build 93.17
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Assignee set to sebchlad
- Priority changed from Normal to High
- Target version set to Milestone 11
@sebchlad: can we assign the ticket to the sprint because it's related to the existing issue about "WE"? -> #23818
- Related to action #23818: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15 added
- Related to deleted (action #23818: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15)
- Blocked by action #23818: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15 added
From SCRUM perspective, since this is a blocker of a current planned "story"*, it has to be implicitly done within the sprint without needing to change the planned ones. Changing the planning always blurs the overview of planned ticket and doesn't help for review & retro.
- * poo#23818 is actually an epic that should be splitted into stories
- Blocked by deleted (action #23818: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15)
- Blocks action #23818: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15 added
- Status changed from New to Feedback
YaST-change is in the product, so fixed and not blocking our sprint ticket anymore
Don't know if anyone wants to verify that, by entering an invalid URL, but the yast2-packager version is > 4.0.7 in Build 280.1, setting to feedback
- Blocks deleted (action #23818: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15)
- Due date set to 2017-10-11
- Assignee deleted (
sebchlad)
- Due date changed from 2017-10-11 to 2017-10-25
- Status changed from Feedback to In Progress
- Assignee set to riafarov
So for WE on SLE15 we have we-module now and don't trigger we-ftp at all anymore. But we want to test the use of any addon as a network repository which we should not miss. I suggest we check that we have this, e.g. with HA addon medium. It's not about the specific addon or module but about the yast installer feature so we could choose any.
suggestions¶
- look for current state of SLE15 test to verify we have at least one testsuite testing adding addons from an external medium, http, ftp, etc.
- update ticket description
- if necessary: adapt/add corresponding test suites for SLE15
- Related to action #25896: [sle][functional] Create test suite to test adding addon medium on SLE 15 added
- Status changed from In Progress to Resolved
Also available in: Atom
PDF