https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-12-19T07:45:51ZopenSUSE Project Management ToolopenQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=345382016-12-19T07:45:51Zmaritawernermawerner@suse.com
<ul><li><strong>Assignee</strong> set to <i>maritawerner</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=352182017-01-05T13:52:13Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Infrastructure</i></li><li><strong>Target version</strong> set to <i>Milestone 5</i></li></ul> openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=365502017-01-18T06:55:53Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> changed from <i>maritawerner</i> to <i>mitiao</i></li></ul><p>AFAIU sunny is fine with taking the offline migration scenarios of openQA into the migration job group. That currently involves x86_64 and ppc64le. s390x is currently under development and not yet touched by this.</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/21934">@mitiao</a>: Do you agree to move the according scenarios into the migration job group? If yes, please do so.</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=365642017-01-18T07:28:10Zmitiao
<ul></ul><p>okurz wrote:</p>
<blockquote>
<p>AFAIU sunny is fine with taking the offline migration scenarios of openQA into the migration job group. That currently involves x86_64 and ppc64le. s390x is currently under development and not yet touched by this.</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/21934">@mitiao</a>: Do you agree to move the according scenarios into the migration job group? If yes, please do so.</p>
</blockquote>
<p>Yes, I will do it.</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=367302017-01-19T07:54:42Zmitiao
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>I am a little confused that all migration scenarios in ONE job group. <br>
As we can see the all migration scenarios across 3 medium types which are sle-12-SP3-Server-DVD, sle-12-SP3-Server-DVD-HA and sle-12-SP3-Desktop-DVD, do you mean that all migrations would be combined into ONE job group on TOP-Level? <br>
Or just according to each medium type to separately combine them into ONE job group as a subgroup in Server, HA and Desktop?</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=367382017-01-19T08:37:36Zokurzokurz@suse.com
<ul></ul><p>hm, good point. As we want more functional groups for each product I suggest to split the online migration group per product and put offline+online together in one job group for each product as you have it already for Server and Desktop. As HA is considered its own product it would mean to also split that into a parent group "HA" with a subgroup "Acceptance: HA" and a subgroup "Migration" like this:</p>
<ul>
<li><p>Server</p>
<ul>
<li>Acceptance: Server</li>
<li>Kernel</li>
<li>FIPS</li>
<li>Migration <-- including both offline+online but only for SLES</li>
</ul></li>
<li><p>Desktop</p>
<ul>
<li>…</li>
<li>Migration</li>
</ul></li>
<li><p>HA</p>
<ul>
<li>…</li>
<li>Migration</li>
</ul></li>
</ul>
<p>Also, it was already mentioned that "Acceptance: Server" is not a good name and "Functional" would better describe it (by <a class="user active user-mention" href="https://progress.opensuse.org/users/21718">@sebchlad</a>, <a class="user active user-mention" href="https://progress.opensuse.org/users/6976">@maritawerner</a>).</p>
<p>so I see the following tasks:</p>
<ul>
<li>Rename existing job groups "Online Migration" to just "Migration"</li>
<li>Create new parent group "HA"</li>
<li>Move existing job group "HA" into the new parent and rename "Functional"</li>
<li>Rename "Acceptance: Server" to "Functional"</li>
<li>Rename "Acceptance: Desktop" to "Functional"</li>
</ul>
<p>@all: agreed?</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=367582017-01-19T09:16:30Zmitiao
<ul></ul><p>+1</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=370422017-01-20T07:00:24Zmitiao
<ul></ul><p>Combined migration scenarios for each product in following job groups:</p>
<p>Migration: Server<br>
Migration: Desktop<br>
Migration: HA</p>
<p>Also created functional group for HA and rename acceptance groups for Server and Desktop as following:</p>
<p>Functional: Server<br>
Functional: Destkop<br>
Functional: HA</p>
<p>I still remain the product suffix because that would be confused with many same name gropus shown in different folder in page <a href="https://openqa.suse.de/admin/groups" class="external">https://openqa.suse.de/admin/groups</a> if suffix removed.<br>
Maybe better to have sub-name to differ them?</p>
<p>Also I removed 'Acceptance' for FIPS since it is only for Server.</p>
<p>Please have a review for all of my changes.<br>
Thanks.</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=370442017-01-20T08:04:55Zokurzokurz@suse.com
<ul></ul><blockquote>
<p>I still remain the product suffix because that would be confused with many same name gropus shown in different folder in page <a href="https://openqa.suse.de/admin/groups" class="external">https://openqa.suse.de/admin/groups</a> if suffix removed.<br>
Maybe better to have sub-name to differ them?</p>
</blockquote>
<p>I understand the problem but I think it is only for the admin during creation of the job groups. I propose to leave out the sub-name. Or do you see a problem which would be visible by non-admin users, too?</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=370462017-01-20T08:39:50Zmitiao
<ul></ul><p>okurz wrote:</p>
<blockquote>
<blockquote>
<p>I still remain the product suffix because that would be confused with many same name gropus shown in different folder in page <a href="https://openqa.suse.de/admin/groups" class="external">https://openqa.suse.de/admin/groups</a> if suffix removed.<br>
Maybe better to have sub-name to differ them?</p>
</blockquote>
<p>I understand the problem but I think it is only for the admin during creation of the job groups. I propose to leave out the sub-name. Or do you see a problem which would be visible by non-admin users, too?</p>
</blockquote>
<p>Yes, this problem is only for admin, for 'Operater' they can access above page without edit privilege and for 'User' they don't have permission to access it.<br>
Without consideration of admin page, it's fine to remove suffix, and I will do it. </p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=370482017-01-20T08:46:04Zmitiao
<ul></ul><p>mitiao wrote:</p>
<blockquote>
<p>okurz wrote:</p>
<blockquote>
<blockquote>
<p>I still remain the product suffix because that would be confused with many same name gropus shown in different folder in page <a href="https://openqa.suse.de/admin/groups" class="external">https://openqa.suse.de/admin/groups</a> if suffix removed.<br>
Maybe better to have sub-name to differ them?</p>
</blockquote>
<p>I understand the problem but I think it is only for the admin during creation of the job groups. I propose to leave out the sub-name. Or do you see a problem which would be visible by non-admin users, too?</p>
</blockquote>
<p>Yes, this problem is only for admin, for 'Operater' they can access above page without edit privilege and for 'User' they don't have permission to access it.<br>
Without consideration of admin page, it's fine to remove suffix, and I will do it.</p>
</blockquote>
<p>Trid and given 'Unable to apply changes'.<br>
Seems now openQA doesn't supprot same name for job group</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=380782017-02-06T05:33:13Zmitiao
<ul></ul><p>All proxyscc online migration server scenarios are in Migration: Server job group.<br>
Should I move the scenarios involved with ha addon into Migration: HA job group like offline migration do?</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=380802017-02-06T05:58:36Zokurz@suse.deokurz@suse.de
<ul></ul><blockquote>
<p>Should I move the scenarios involved with ha addon into Migration: HA<br>
job group like offline migration do?</p>
</blockquote>
<p>I think that makes sense</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=397742017-02-14T09:21:44Zmitiao
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>The scenarios involved with HA addon have been moved into Migration: HA job group.</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=403442017-02-17T11:17:13Zokurzokurz@suse.com
<ul></ul><p>please check the so called "autoupgrade" testsuites which are still in the "Functional: Server" group: <a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP3&groupid=55" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP3&groupid=55</a></p>
<p>To me it seems they are "migration jobs" based on autoyast configuration files, right? E.g. see <a href="https://openqa.suse.de/tests/780094#step/bootloader/6" class="external">https://openqa.suse.de/tests/780094#step/bootloader/6</a> for the "autoyast*.xml autoupgrade=1" typing</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=403502017-02-17T12:25:28Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>In Progress</i></li></ul> openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=404762017-02-20T09:04:46Zmitiao
<ul></ul><p>Moved them into Migration: Server group.<br>
<a class="user active user-mention" href="https://progress.opensuse.org/users/15410">@dgutu</a> are you maintaining these 5 autoupgrade by autoyast configuration files?<br>
If any unknown issue on them, I could ask you. :)</p>
openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=424002017-03-01T09:24:17Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 5</i> to <i>Milestone 6</i></li></ul> openQA Tests - action #15546: [Migration] Combine both online and offline upgrades into one jobgrouphttps://progress.opensuse.org/issues/15546?journal_id=443822017-03-21T05:34:45Zmitiao
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Can be resolved as all migration cases combined into migration groups.</p>