action #11458

Feature 319716: Automatic Update of YaST at beginning of the installation

Added by maritawerner about 4 years ago. Updated over 3 years ago.

Status:ResolvedStart date:01/04/2016
Priority:UrgentDue date:
Assignee:okurz% Done:

0%

Category:Enhancement to existing tests
Target version:openQA Project - Milestone 3
Difficulty:
Duration:

Description

For details see https://fate.suse.com/319716

First check if the Feature status is "done".

tasks left to be done

  • verify on osd that it's triggered as yast_no_self_update on 12-sp2 server build > 2002
  • add to o3
  • optionally: extend to check that the installer really updates itself in case an update is present

History

#1 Updated by RBrownSUSE almost 4 years ago

  • Target version set to 168

#2 Updated by RBrownSUSE almost 4 years ago

  • Assignee set to dmaiocchi

#3 Updated by dmaiocchi almost 4 years ago

  • Status changed from New to Feedback

feature is not "done"

#4 Updated by okurz almost 4 years ago

  • Target version changed from 168 to Milestone 3

#5 Updated by okurz almost 4 years ago

  • Assignee deleted (dmaiocchi)

#6 Updated by okurz almost 4 years ago

  • Description updated (diff)
  • Category set to Enhancement to existing tests
  • Assignee set to okurz

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 https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1478

Verification run: https://openqa.suse.de/tests/448100

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?
dzedro will ask the YaST team how they plan to test the update feature, e.g. provide a fake update channel (over SCC?).

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.

#7 Updated by RBrownSUSE over 3 years ago

  • Priority changed from Normal to Urgent

#8 Updated by okurz over 3 years ago

As I just learned from https://mailman.suse.de/mlarch/SuSE/research/2016/research.2016.07/msg00080.html the self_update can be disabled with

self_update=0

as boot param. So we should have two scenarios:

  • self_update=1 (current default)
  • self_update=0

#10 Updated by okurz over 3 years ago

  • Description updated (diff)

PR merged, added test_suite "yast_no_self_update" to o.s.d with settings INSTALLONLY=1 and INSTALLER_NO_SELF_UPDATE=1. Added this test suite to server acceptance group and triggering once manually to verify:

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

--> t#484686

#11 Updated by okurz over 3 years ago

  • Description updated (diff)

t#484686 successful, added test_suite to o3 and the test_suite to TW and Leap

#12 Updated by okurz over 3 years ago

  • Description updated (diff)
  • Status changed from Feedback to Resolved

verified that it triggers on new ISOs on osd: t#484785

Also available in: Atom PDF