action #15136

action #9486: [sle][opensuse][functional][epic][y]Network Installations

[functional][hard][yast][y] network installations over SMB

Added by okurz over 3 years ago. Updated over 1 year ago.

Status:RejectedStart date:09/02/2017
Priority:NormalDue date:
Assignee:okurz% Done:

100%

Category:New test
Target version:QA - future
Difficulty:
Duration:

Description

Motivation

test install over SMB repositories

Acceptance criteria

  • AC1: We have at least one installation scenario installing from a repository shared over SMB on both osd as well as o3

Tasks

The only missing part is tests on o3 needing a SMB server as we already have on osd. We could be messy and apply what we have on osd or do it the right way and use salt recipes. But so far o3 has salt installed but does not seem to use it itself.

further details

/etc/samba/smb.conf from osd

[global]
    workgroup = openqa.suse.de
    passdb backend = tdbsam
    printing = cups
    printcap name = cups
    printcap cache time = 750
    cups options = raw
    map to guest = Bad User
    logon path = \\%L\profiles\.msprofile
    logon home = \\%L\%U\.9xprofile
    logon drive = P:
    usershare allow guests = No
    add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
    domain logons = No
    domain master = No
    security = user
    wins support = No
[inst]
    comment = openqa assets
    guest ok = Yes
    inherit acls = Yes
    path = /var/lib/openqa/factory/repo/
    read only = Yes

Original proposal: different alternatives

  • check SMB testsuite in SLEnkins (@mawerner, @theheijk)
  • add https/smb/nfs support to openqa.suse.de (run the corresponding servers there)
  • test against dist.suse.de already offering smb. As builds are not preserved on dist we would need to restrict this to milestone builds

Checklist


Subtasks

action #16610: [s390x] Add ability to install via smb Resolved


Related issues

Blocked by openQA Tests - action #29393: [sle][functional][tools] test fails in bootloader_s390 - ... Resolved 14/12/2017

History

#1 Updated by mkravec over 3 years ago

NFS - works fine on openqa.suse.de - https://openqa.suse.de/tests/646729
HTTPS - I am not sure if there is support in sles, there is no HTTPS option in installer (F4 menu) and iirc it did not work when I entered manually

#2 Updated by maritawerner about 3 years ago

HTTPS is covered in a separate ticket.

#3 Updated by okurz about 3 years ago

take a look into the parent task #9486, there is #15148 for https

#4 Updated by okurz about 3 years ago

  • Assignee changed from maritawerner to thehejik

@thehejik

  • would the SMB testsuite in slenkins help us to test installation over SMB?

If I get it right a SMB test suite should setup a server and a client and check that the client can access files from the server. If that is the case with the existing test case can we use that server component to do an installation from it when we put installation media (e.g. SLES + some addons) on the server?

On which architectures would that be possible for both server+client?

#5 Updated by thehejik about 3 years ago

okurz wrote:

@thehejik


  • would the SMB testsuite in slenkins help us to test installation over SMB?

Unfortunately, I don't see any way how to (re)use SMB server SUT from SLEnkins samba testsuite as a source of test-image for any openQA job.

If I get it right a SMB test suite should setup a server and a client and check that the client can access files from the server. If that is the case with the existing test case can we use that server component to do an installation from it when we put installation media (e.g. SLES + some addons) on the server?

I got your point but I found it a bit difficult to implement because:
* SLEnkins suites are running on special ovs/tap workers in openQA, it means that regular job running on x86_64 worker will have no access to ovs/tap network and vice versa
* It will need some locking policy to be set, for example if a new image is available run SMB server test, copy new image on that server and then run job for SMB installation
* interoperability between normal needle based test and SLEnkins SUTs is not supported (not sure if possible)

On which architectures would that be possible for both server+client?

The current SLEnkins wrapper in openQA supports only x86_64 VMs and the same stands for slenkins-cloud. SLEnkins itself supports aarch64, x86_64, ppc64le, ppc64 and s390 architectures but only if you are running the test on bare-metal with help of kvm or on x86_64 in emulation mode (s390 supported only on SLE11 in emu).

#6 Updated by mgriessmeier about 3 years ago

We've set up a smb server on o.s.d. which can be accessed over the share 'install' and points to the /var/lib/openqa/factory/repo/ like our ftp server does.

first quick try on s390x succeeded

#7 Updated by thehejik about 3 years ago

mgriessmeier wrote:

We've set up a smb server on o.s.d. which can be accessed over the share 'install' and points to the /var/lib/openqa/factory/repo/ like our ftp server does.


first quick try on s390x succeeded

Yeah, thats much better solution I think.

#8 Updated by mgriessmeier about 3 years ago

working testcases on o.s.d for s390x:

SLES: https://openqa.suse.de/tests/773865
SLES+HA: https://openqa.suse.de/tests/773864

#9 Updated by maritawerner about 3 years ago

  • Checklist set to [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le

So we need to add the other arches as well (if possible).

#10 Updated by thehejik about 3 years ago

  • Status changed from New to In Progress

#11 Updated by thehejik about 3 years ago

  • Checklist changed from [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le to [ ] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le

I have created simple smb install test for x86_64 using standard variables:
NETBOOT=1 (in Media definition on o.s.d)
MIRROR_SMB=smb://openqa.suse.de/inst/SLE-12-SP3-Server-DVD-x86_64-Build0256-Media1 (from rsync.pl - needs to be modified for MIRROR_SMB and for FLAVOR=Server-MINI-ISO)
INSTALL_SOURCE=smb

And it works, see http://dhcp209.suse.cz/tests/3349

Complete test sles12_minimal_base-smb definition:
DESKTOP=textmode
HDDSIZEGB=50
INSTALLONLY=1
INSTALL_SOURCE=smb
MIRROR_SMB=smb://openqa.suse.de/inst/SLE-12-SP3-Server-DVD-x86_64-Build0256-Media1
NETBOOT=1
PATTERNS=base,minimal
TOGGLEHOME=1

Needles https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/316

#12 Updated by thehejik about 3 years ago

  • Checklist set to [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO

#13 Updated by thehejik about 3 years ago

  • Checklist set to [ ] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO

#14 Updated by thehejik about 3 years ago

  • Checklist changed from [ ] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le to [ ] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le, [ ] wait for fix poo#17346, [ ] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097
  • Status changed from In Progress to Feedback

Modification of rsync.pl done at https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097
but I can't test it due https://progress.opensuse.org/issues/17346 - rsync.pl does a sync even if --dry option is used for sle12_sp3

#15 Updated by thehejik about 3 years ago

  • Checklist changed from [ ] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le, [ ] wait for fix poo#17346, [ ] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097 to [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [ ] wait for fix poo#17346, [ ] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le

#16 Updated by thehejik about 3 years ago

  • Checklist set to [x] wait for fix poo#17346

#17 Updated by thehejik about 3 years ago

  • Checklist set to [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097

#18 Updated by okurz about 3 years ago

https://gitlab.suse.de/openqa/scripts/merge_requests/67 merged.

I adapted the existing testsuite "smb+xfs" as it was used for s390x and enabled aarch64, x64_64 and ppc64le scenarios within the test development group. After they are shown to be stable we move them to "sles: functional"

#19 Updated by thehejik about 3 years ago

  • Checklist changed from [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le to [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [x] x86_64, [ ] ppc64le

I have added test for x86_64 medium Server-MINI-ISO named "gnome_smb" https://openqa.suse.de/tests/803763#

I'm affraid that Oli's approach with smb+xfs will not work because MIRROR_SMB is available only for Server-MINI-ISO medium and bootloader_setup.pm doesn't know the SMB URI - contrary to bootloader_s390.pm where the SMB URI is hardcoded.

Results for oli's smb+xfs:
* ppc failed https://openqa.suse.de/tests/802730#step/bootloader_ofw/9 - it is still using ISO as install source
* x86 failed https://openqa.suse.de/tests/802914#step/bootloader/15 - empty dialog for smb share
* aarch64 missing

#20 Updated by okurz almost 3 years ago

So what are your plans on this? The tests in test development still show the same results (and keep wasting ressources). We could just remove them and assume the coverage on s390x is enough in general. Or just add some test settings? The test code can be cleaned up nevertheless to not do something "architecture" specific which it actually isn't.

#21 Updated by thehejik almost 3 years ago

okurz wrote:

So what are your plans on this? The tests in test development still show the same results (and keep wasting ressources). We could just remove them and assume the coverage on s390x is enough in general. Or just add some test settings? The test code can be cleaned up nevertheless to not do something "architecture" specific which it actually isn't.

Please remove your tests from Test Development group, it will not work and as you said it is just wasting resources. Right now we have a coverage for s390x from Mathias and x86_64 from me.

Imo it would be nice to have ppc64le and aarch64 SMB installation tests as well.

#22 Updated by okurz almost 3 years ago

Agreed. misleading scenarios for smb+xfs@ppc64le and smb+xfs@x86_64 removed from test development group so that they won't get scheduled and provide a wrong impression.

@thehejik feel free to unassign the ticket from yourself when you don't plan to work on it in the next time.

#23 Updated by thehejik almost 3 years ago

  • Assignee deleted (thehejik)

#24 Updated by okurz about 2 years ago

  • Checklist changed from [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [x] x86_64, [ ] ppc64le to [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le
  • Status changed from Feedback to Workable

I'm afraid what thehejik mentioned in #15136#note-19 could have never worked because the variable NETBOOT=1 is not set. The installer never switched to use SMB -> #30640

#25 Updated by okurz about 2 years ago

  • Blocked by action #29393: [sle][functional][tools] test fails in bootloader_s390 - check settings of samba server on o.s.d added

#26 Updated by mkravec about 2 years ago

  • Assignee set to mloviska

#27 Updated by okurz about 2 years ago

  • Checklist changed from [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [ ] x86_64, [ ] ppc64le to [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [x] x86_64, [ ] ppc64le
  • Target version set to Milestone 14

blocking tickets resolved, e.g. also #30640

IMHO the missing part is now openSUSE which needs help of the openQA or openSUSE admins to setup a SMB server on o3. The architectures aarch64 and ppc64le do not need an extra SMB test.

#28 Updated by okurz about 2 years ago

  • Subject changed from network installations over SMB to [functional]network installations over SMB

#29 Updated by okurz about 2 years ago

  • Checklist changed from [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [ ] aarch64, [x] x86_64, [ ] ppc64le to [x] modify rsync.pl for generating MIRROR_SMB for FLAVOR=Server-MINI-ISO, [x] wait for fix poo#17346, [x] test and merge rsync.pl from https://gitlab.suse.de/thehejik/scripts/commit/e19ae8a59b86df8ea39d4d81d7f5bea8ed61a097, [x] s390x, [x] x86_64
  • Subject changed from [functional]network installations over SMB to [functional][hard][yast]network installations over SMB
  • Description updated (diff)
  • Assignee deleted (mloviska)
  • Target version changed from Milestone 14 to Milestone 18

Actually I think we are good enough here with covering x86_64 and s390x architecture-wise. So the missing part is only openSUSE now.

@mloviska I don't see you actually working on this so I unassign you.

#30 Updated by okurz almost 2 years ago

  • Subject changed from [functional][hard][yast]network installations over SMB to [functional][hard][yast][y] network installations over SMB

#31 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 18 to Milestone 18

#32 Updated by okurz over 1 year ago

  • Target version changed from Milestone 18 to future

#33 Updated by okurz over 1 year ago

  • Status changed from Workable to Rejected
  • Assignee set to okurz

ok, I give up now ;)

#34 Updated by mgriessmeier about 1 year ago

  • Related to action #47879: [functional][u][s390x] test fails in bootloader_s390: smb test is not booting the installer over info-file added

#35 Updated by mgriessmeier about 1 year ago

  • Related to deleted (action #47879: [functional][u][s390x] test fails in bootloader_s390: smb test is not booting the installer over info-file)

Also available in: Atom PDF