https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842017-09-27T14:45:00ZopenSUSE Project Management ToolopenQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=658962017-09-27T14:45:00ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>Related:</p>
<ul>
<li>Previous bug: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1059744" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1059744</a></li>
<li>Now error message is shown: <a href="https://github.com/yast/yast-packager/pull/285" class="external">https://github.com/yast/yast-packager/pull/285</a></li>
</ul>
openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=659042017-09-27T16:40:37Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> set to <i>sebchlad</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>Milestone 11</i></li></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/21718">@sebchlad</a>: can we assign the ticket to the sprint because it's related to the existing issue about "WE"? -> <a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" title="action: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15 (Resolved)" href="https://progress.opensuse.org/issues/23818">#23818</a></p>
openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=659062017-09-27T16:40:45Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/23818">action #23818</a>: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15</i> added</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=660962017-09-29T08:56:56ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/23818">action #23818</a>: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15</i>)</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=661022017-09-29T08:57:13ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/23818">action #23818</a>: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15</i> added</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=661082017-09-29T09:14:44ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>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.</p>
<ul>
<li>* poo#23818 is actually an epic that should be splitted into stories</li>
</ul>
openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=661122017-09-29T09:14:52ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocked by</strong> deleted (<i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/23818">action #23818</a>: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15</i>)</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=661142017-09-29T09:14:57ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/23818">action #23818</a>: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15</i> added</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=661542017-09-29T11:08:20ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>PR: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3643" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3643</a></p>
openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=664862017-10-05T13:36:36Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>YaST-change is in the product, so fixed and not blocking our sprint ticket anymore<br>
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</p>
openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=664942017-10-05T13:37:15Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/23818">action #23818</a>: [sles][functional][sle15] Adapt WE and related test scenarios to SLE15</i>)</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=666762017-10-06T20:40:58Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2017-10-11</i></li><li><strong>Assignee</strong> deleted (<del><i>sebchlad</i></del>)</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=669422017-10-10T09:41:26Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2017-10-11</i> to <i>2017-10-25</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>riafarov</i></li></ul><p>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.</p>
<a name="suggestions"></a>
<h2 >suggestions<a href="#suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>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.</li>
<li>update ticket description</li>
<li>if necessary: adapt/add corresponding test suites for SLE15</li>
</ul>
openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=670142017-10-10T15:12:10Zriafarov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/25896">action #25896</a>: [sle][functional] Create test suite to test adding addon medium on SLE 15</i> added</li></ul> openQA Tests - action #25626: [sle][functional] test fails in addon_products_sle - Invalid add-on ftp url for WEhttps://progress.opensuse.org/issues/25626?journal_id=670182017-10-10T15:12:40Zriafarov
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Resolving and work on outcome of this ticket in <a href="https://progress.opensuse.org/issues/25896" class="external">https://progress.opensuse.org/issues/25896</a></p>