coordination #17436

Updated by okurz over 6 years ago

## acceptance criteria 

 * **AC1:** Only repository content from is used for all openSUSE tests after installation observation 
 * **AC2:** Same as **AC1** but for the installer system itself 

 ## tasks 

 * check test cases for the execution of tests/update/ and see if the same approach can be adapted for a generic approach (1-2h) 
 * start by selecting a standard gnome/kde test suite and any extra tests scenario, make sure the online repos not pointing to are disabled and check if all packages can still be installed (2-4h) 
 * rewrite all occurences of "" in the SUT to the according path pointing to, e.g. with a test module that calls sed -i -e 's/…/g' /etc/zypp/repos.d/* in the installed system (2-8h) 
 * investigate how repos are used in the installer system, replace occurences of as described above or not add any online repos there if possible (2-16h) 

 ## further details 

 ### observation 

 see for example This bug was just "found" by openQA when also users reported this. The reason is probably that the tests still have published repos from enabled causing an upgrade to find packages from either the new snapshot or the old published data which can make tests pass when they shouldn't. Then the tests fail in the subsequent snapshot because the repos were updated in the meantime. 

 ### proposal ## suggestions 

 * check test cases for the execution of tests/update/ 

 ## further details 

 proposal by nussel in #17818 
 On openSUSE the 'crash' test doesn't work as the debuginfo repo is not mirrored to openqa. So whenever the kernel gets updated that test fails due to a mismatch between the installed kernel and the debug information in the debuginfo repo. 

 openQA should keep a local copy of all repos and intercept access to so files are downloaded from matching repos actually. 

 from #17926 

 Follow up to bug 

 The problem: 
 whlie testing upgrade scenarios from e.g. 42.2 to TW-Next (the version being tested in openQA), the CURRENTLY published TW on download.o.o is ALSO taken into account (online repo enabled) 

 In case of the boo#1030759 this results in the updater NOT tagging libmutter0 is an obsolete package (it is tagged 'weakremove', which means it is ONLY marked for deletion if it is NOT found in any of the enabled repos. As TW (published) still contains the package, it is not removed - furhter blocking the update of gnome-shell * mutter, which leads to the test failures as seen in e.g. 

 We had seen similar test issues in the past, be it that stuff 'works' during the openQA test until TW-Next is published (then packages disappear, and tests would no longer pass) 
 In any case, having the repo published at download.o.o available to the tests is defeating openQA as it is intended totally, as many tests are not reliable this way (testing a repo combination that no user will possibly be able to have on his system) Shows that the repos are in fact enabled. is an example from the 'other direction of the same problem'. With snapshot 0320, libmarco-private0 was dropped (replaced by libmarco-private1); when 0320 was being tested though, the previously published snapshot was available and thus this did not show an error in its test run at As soon as snapshot 0320 has been published, the available package list changed and the test is thus invalid (and fails with one day delay). After 0322 was published, reran the 42.2-> tw update passed. before publish: vs after publish and rerun: 

 The whole openSUSE Factory snapshot should be synced to o3 and probably the same for Leap so all repository content should be there on o3.