Project

General

Profile

action #12804

[functional][u][sles][opensuse][installation] Do more easy to debug tests by using chroot installations … or containers :)

Added by okurz about 4 years ago. Updated 7 months ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Enhancement to existing tests
Target version:
Start date:
2016-07-21
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

e.g. see https://jenkins.debian.net/view/All/job/chroot-installation_jessie_install_education-logic-games_upgrade_to_stretch/111/console

why do we need to bootstrap a full installation and watch at the screen when the result is just that package dependencies can not be resolved? I think for this we should rather user jenkins and chroot installations. This might be more of an issue for generic "SUSE/openSUSE testing approach" but please don't just close this ticket but move it to this project or create one if we don't have that progress project so far.

further interesting references

https://jenkins.debian.net/view/All/job/g-i-installation_debian_sid_daily_lxde/


Related issues

Related to openQA Project - action #20246: [gsoc] Investigate/implement container-based backendNew2017-07-04

History

#1 Updated by okurz about 4 years ago

  • Description updated (diff)

#2 Updated by okurz almost 4 years ago

  • Category set to Enhancement to existing tests

#3 Updated by asmorodskyi over 3 years ago

  • Subject changed from Do more easy to debug tests by using chroot installations to [sles][opensuse][installation] Do more easy to debug tests by using chroot installations

#4 Updated by okurz about 2 years ago

  • Subject changed from [sles][opensuse][installation] Do more easy to debug tests by using chroot installations to [functional][sles][opensuse][installation] Do more easy to debug tests by using chroot installations
  • Target version set to future

#5 Updated by okurz almost 2 years ago

  • Subject changed from [functional][sles][opensuse][installation] Do more easy to debug tests by using chroot installations to [functional][u][sles][opensuse][installation] Do more easy to debug tests by using chroot installations … or containers :)

I think by now containers are the way to go :)

#6 Updated by okurz almost 2 years ago

  • Related to action #20246: [gsoc] Investigate/implement container-based backend added

#7 Updated by okurz almost 2 years ago

  • Target version changed from future to Milestone 21

Shortly discussed with slindomansilla. What we think might be feasible and useful is to conduct one of the existing test modules from openQA scenarios like "textmode" within a container. This would fit in somewhere between tests in OBS like https://build.opensuse.org/project/show/home:okurz:test-packagehub and the openQA installation scenarios. The quickmost dirty approach is probably when we boot any existing (older, stable) OS disk image, install docker in there, pull the latest published image of the product to test, add more current repos with SUSEConnect/zypper, register, install and conduct a simple test. However, this sounds a bit wasteful as we would need to boot a VM to conduct a container based test within. I feel we really should use gitlab CI instead. Maybe one micro-app that listens to AMQP OBS events and on new publications of the products we test trigger a container based CI test in a gitlab project.

#8 Updated by okurz over 1 year ago

  • Target version changed from Milestone 21 to future

#9 Updated by SLindoMansilla 7 months ago

  • Status changed from New to Workable
  • Priority changed from Normal to Low
  • Estimated time set to 42.00 h

Also available in: Atom PDF