https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-02-21T22:04:54ZopenSUSE Project Management ToolopenQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=929412018-02-21T22:04:54Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[opensuse][functional] Sync all repos for TW and Leap for all tested versions</i> to <i>[opensuse][functional][medium] Sync all repos for TW and Leap for all tested versions</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/92941/diff?detail_id=91381">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul><p>Discussed with openSUSE RMs regarding online repos: We have still the online<br>
published repos enabled in many openQA tests.</p>
<ul>
<li>Is it possible to sync all repos, including non-oss, debug, source,
update? -> space should not be the problem on o3 but syncing big repos
would delay the testing. Probably we already sync debug. We should make
sure non-oss is synced as well. Avoid big source in general. Optional:
Only sync the relevant parts of the source repo for corresponding tests,
e.g. zypper_info on source packages or a toolchain or compile test</li>
<li>Is there any build validation test where we need the online published
repos enabled? -> No, we could not think of any. This confirms the
hypothesis by okurz that relying on them would be an invalid test by
definition.</li>
</ul>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=929472018-02-21T22:05:25Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2018-03-27</i></li><li><strong>Target version</strong> set to <i>Milestone 15</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1029492018-03-16T09:25:33Zriafarov
<ul><li><strong>Assignee</strong> set to <i>riafarov</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1035162018-03-19T08:55:36Zriafarov
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1038252018-03-20T08:55:04Zriafarov
<ul></ul><p>Waiting for the reviews and then need to request deployment: <a href="https://gitlab.suse.de/openqa/scripts/merge_requests/192" class="external">https://gitlab.suse.de/openqa/scripts/merge_requests/192</a> <br>
I will trigger the dry runs for all profiles we call from cron</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1038552018-03-20T09:20:36Zriafarov
<ul></ul><p>Waiting for the feedback on <a href="https://gitlab.suse.de/openqa/scripts/merge_requests/192" class="external">https://gitlab.suse.de/openqa/scripts/merge_requests/192</a> if we want to sync more and then need to adjust tests after rsync is deployed to o3.</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1039782018-03-20T14:31:57Zriafarov
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1043892018-03-21T14:35:33Zriafarov
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1043982018-03-21T14:39:37Zriafarov
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Blocked</i></li></ul><p>Figuring out how to conduct rsync.pl deployment to o3 first.</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1044072018-03-21T15:25:53Zriafarov
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>In Progress</i></li></ul><p>Here are the instructions how to handle rsync.pl update:<br>
riafarov: o3:/opt/openqa-scripts/HOW_TO_MODIFY explains how to do that. I wonder why that file is not in the repo itself. maybe you can move that file there? do you have ssh access to o3?<br>
riafarov: <a href="http://susepaste.org/31955383" class="external">http://susepaste.org/31955383</a> if you don't have access to the file</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1044252018-03-21T16:47:22Zriafarov
<ul></ul><p>We will sync rsync changes deployment with work DimStar does for new builder migration. <a href="https://gitlab.suse.de/openqa/scripts/merge_requests/196" class="external">https://gitlab.suse.de/openqa/scripts/merge_requests/196</a> is additional minor change. <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4679" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4679</a> changes for tests.</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1055802018-03-27T09:02:21Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-03-27</i> to <i>2018-04-10</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1056642018-03-27T12:18:04Zriafarov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed child" href="/issues/20892">action #20892</a>: [perl] product-builder: adjust openQA rsync.pl</i> added</li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1057302018-03-27T13:17:39Zriafarov
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/105730/diff?detail_id=105421">diff</a>)</li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1071312018-03-30T06:51:03Zmichel_mnonormand@linux.vnet.ibm.com
<ul></ul><p>Would the rsync.pl be able to be used outside SUSE network to sync my local openQA server instance ?</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1087302018-03-30T09:19:06Zokurzokurz@suse.com
<ul></ul><p>michel_mno wrote:</p>
<blockquote>
<p>Would the rsync.pl be able to be used outside SUSE network to sync my local openQA server instance ?</p>
</blockquote>
<p>Well, first problem I see is that rsync.pl is not open-sourced. Next problem I see currently o3 syncs from an iternal host. Can we access the TW + leap snapshots that are under current testing from the outside?</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1089702018-04-03T06:16:53Zriafarov
<ul></ul><p>okurz wrote:<br>
I was not able to access them using rsync from R&D network, but those work if you add them using zypper, so I guess something can be done here, but not with rsync.pl.</p>
<blockquote>
<p>michel_mno wrote:</p>
<blockquote>
<p>Would the rsync.pl be able to be used outside SUSE network to sync my local openQA server instance ?</p>
</blockquote>
<p>Well, first problem I see is that rsync.pl is not open-sourced. Next problem I see currently o3 syncs from an iternal host. Can we access the TW + leap snapshots that are under current testing from the outside?</p>
</blockquote>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1096662018-04-04T14:23:14Zriafarov
<ul></ul><p>So as of now we only have problems with source repos as we don't want to sync whole repos cause of the single package, so this is remaining part to implement it in rsync.pl and then adjust the test to add OSS source repo.</p>
<p>As per access from outside, we have tested that zypper is able to access snapshot repos outside of R&D network, however you cannot list directories/files over http (gets redirected to https) or ftp.<br>
If full path is known, you should be able to access it over http:</p>
<pre><code>wget http://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-non-oss-i586-x86_64-Snapshot20180324/repodata/repomd.xml
</code></pre> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1098552018-04-05T10:54:53Zpcervinkapcervinka@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/34288">action #34288</a>: [qam] test fails in zypper_info - zypper_info shouldn't be started</i> added</li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1098582018-04-05T10:57:41Zpcervinkapcervinka@suse.com
<ul></ul><p>Please update conditions for loading zypper_info, it shouldn't be run on SLE12GA. See <a href="https://openqa.suse.de/tests/overview?distri=sle&version=12&build=20180405-1&groupid=35" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12&build=20180405-1&groupid=35</a> and <a href="https://progress.opensuse.org/issues/34288" class="external">https://progress.opensuse.org/issues/34288</a></p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1098732018-04-05T11:14:23Zpcervinkapcervinka@suse.com
<ul></ul><p>Not only on SLE12GA, it caused also issue on SLE12SP3 <a href="https://openqa.suse.de/tests/1591046#step/zypper_info/9" class="external">https://openqa.suse.de/tests/1591046#step/zypper_info/9</a></p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1100442018-04-05T16:40:45Zriafarov
<ul></ul><p>Another broken test suite: <a href="https://openqa.opensuse.org/tests/651007#comments" class="external">https://openqa.opensuse.org/tests/651007#comments</a> we don't have update repos in the image we have created.</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1101522018-04-06T08:30:17Zriafarov
<ul></ul><p>So, after many fixes for zypper_info we have excluded following scenarios to replace repos:<br>
create_hdd_gnome<br>
kde-live_installation<br>
krypton-live<br>
kde-live<br><br>
gnome-live<br><br>
krypton-live-installation<br>
krypton-live-wayland<br>
kde-live-wayland<br>
gnome-live_installation</p>
<p>create_hdd_gnome breaks yast2_control_center as no update repo is available and online update module fails.<br>
For live images on leap we have totally different release process and as of now we may simply not schedule modules if variables are not set. This is still required for TW live, and works there.</p>
<p>Also in create_hdd we get problems with packagekit: <a href="https://openqa.opensuse.org/tests/651489#step/zypper_ar/10" class="external">https://openqa.opensuse.org/tests/651489#step/zypper_ar/10</a></p>
<p>Here are fixes for packagekit and live images:<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4797" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4797</a></p>
<p>yast2 control center is fixed by adding update repos:<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4793" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4793</a></p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1103862018-04-09T08:10:15Zokurzokurz@suse.com
<ul></ul><p>Adding update repos explicitly with <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4793" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4793</a> but apparently for openSUSE Tumbleweed we already have an update repo: <a href="https://openqa.opensuse.org/tests/652265#step/yast2_control_center/27" class="external">https://openqa.opensuse.org/tests/652265#step/yast2_control_center/27</a> Do we need to retrigger the create image job?</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1109922018-04-10T07:56:14Zriafarov
<ul></ul><p>All found issues are fixed. zypper_info is still an issue, as well as yast update module in yast control center</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1111482018-04-10T08:48:28Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-04-10</i> to <i>2018-04-24</i></li></ul> openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1119342018-04-11T13:54:27Zriafarov
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>So we reached safe state, remaining tasks are mentioned in <a href="https://progress.opensuse.org/issues/34732" class="external">https://progress.opensuse.org/issues/34732</a> which is follow up.<br>
Acceptance criteria here was too optimistic, we cannot and should not sync all and always replace. Resolving this ticket.</p>
openQA Tests - action #32038: [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versionshttps://progress.opensuse.org/issues/32038?journal_id=1226472018-05-30T11:16:35Zriafarov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/36333">action #36333</a>: [opensuse][y][medium] Invalid repositories - failing kate install</i> added</li></ul>