https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-04-06T16:19:00ZopenSUSE Project Management ToolopenQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=227802016-04-06T16:19:00ZRBrownSUSErbrown@suse.com
<ul><li><strong>Target version</strong> set to <i>168</i></li></ul> openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=228562016-04-11T08:29:07ZRBrownSUSErbrown@suse.com
<ul><li><strong>Assignee</strong> set to <i>dmaiocchi</i></li></ul> openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=229822016-04-19T09:50:16Zdmaiocchi
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>feature is not "done"</p>
openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=238442016-05-30T12:53:59Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>168</i> to <i>Milestone 3</i></li></ul> openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=240722016-06-06T07:24:46Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> deleted (<del><i>dmaiocchi</i></del>)</li></ul> openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=245162016-06-18T11:39:12Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/24516/diff?detail_id=25426">diff</a>)</li><li><strong>Category</strong> set to <i>Enhancement to existing tests</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>deleted content in this ticket duplicated from fate as discussed with marita. The fate entry is still not set to DONE but the code already has some kind of auto-update included. I worked around an issue which came up interlinked with this on ssh+X installs in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1478" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1478</a></p>
<p>Verification run: <a href="https://openqa.suse.de/tests/448100" class="external">https://openqa.suse.de/tests/448100</a></p>
<p>However during discussion in the openQA call questions came up if the system we test does not change too much under our hands while testing, i.e. calling the same test a later time would behave differently because the installer would have an update?<br>
dzedro will ask the YaST team how they plan to test the update feature, e.g. provide a fake update channel (over SCC?).</p>
<p>So I consider this ticket done unless dzedro comes back with different ideas from next meeting with YaST team. Also, I would like to resolve it only after the corresponding fate issue is marked as done.</p>
openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=250082016-07-11T13:46:48ZRBrownSUSErbrown@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=250382016-07-12T07:18:20Zokurzokurz@suse.com
<ul></ul><p>As I just learned from <a href="https://mailman.suse.de/mlarch/SuSE/research/2016/research.2016.07/msg00080.html" class="external">https://mailman.suse.de/mlarch/SuSE/research/2016/research.2016.07/msg00080.html</a> the self_update can be disabled with</p>
<pre><code>self_update=0
</code></pre>
<p>as boot param. So we should have two scenarios:</p>
<ul>
<li><code>self_update=1</code> (current default)</li>
<li><code>self_update=0</code></li>
</ul>
openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=252222016-07-19T14:27:38Zokurzokurz@suse.com
<ul></ul><p>PR ready <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1540" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1540</a></p>
openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=254042016-07-25T08:52:32Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/25404/diff?detail_id=26092">diff</a>)</li></ul><p>PR merged, added test_suite "yast_no_self_update" to o.s.d with settings <code>INSTALLONLY=1</code> and <code>INSTALLER_NO_SELF_UPDATE=1</code>. Added this test suite to server acceptance group and triggering once manually to verify:</p>
<pre><code>openqa_client_osd jobs post DISTRI=sle ARCH=x86_64 BACKEND=qemu BETA=1 BUILD=2002 DESKTOP=gnome FLAVOR=Server-DVD HDDSIZEGB=20 ISO=SLE-12-SP2-Server-DVD-x86_64-Build2002-Media1.iso MACHINE=64bit TEST=okurz_verify_yast_no_self_update_poo11458 QEMUCPU=qemu64 VERSION=12-SP2 WORKER_CLASS=qemu_x86_64
</code></pre>
<p>--> <a href="https://openqa.suse.de/tests/484686" class="external">t#484686</a></p>
openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=254262016-07-25T11:52:00Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/25426/diff?detail_id=26108">diff</a>)</li></ul><p><a href="https://openqa.suse.de/tests/484686" class="external">t#484686</a> successful, added test_suite to o3 and the test_suite to TW and Leap</p>
openQA Tests - action #11458: Feature 319716: Automatic Update of YaST at beginning of the installationhttps://progress.opensuse.org/issues/11458?journal_id=254282016-07-25T11:53:19Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/25428/diff?detail_id=26110">diff</a>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>verified that it triggers on new ISOs on osd: <a href="https://openqa.suse.de/tests/484785" class="external">t#484785</a></p>