action #32038
closed
coordination #17436: [tools][functional][y][epic] tests must not have access to published repos, e.g. download.o.o on Tumbleweed -> remove all references to download.o.o from repos during installation and afterwards
[opensuse][functional][medium] Sync all repos for TW and Leap for all tested versions
Added by riafarov about 6 years ago.
Updated about 6 years ago.
Category:
Enhancement to existing tests
Description
Motivation¶
As we expect some problems if we disable online repos, we should sync all repos, so all used packages are available.
Acceptance criteria¶
- AC1: All used repos are synced
- AC2: Official openSUSE online repos are not used (no exceptions)
Tasks¶
- DONE: Identify all repos for all TW and Leap tested versions (including different archs)
- DONE: Identify if we can afford syncing all of them -> Make sure that oss, non-oss, debug is synced, avoid source and update for now
- DONE: Adjust rsync.pl to sync these repos as per results of task #2 (syncing oss and non-oss and oss debug repos).
- Enable behavior which is currently enabled by "DISABLE_ONLINE_REPOS" variable for all test suites PR#4679
- Flip "DISABLE_ONLINE_REPOS" to "ENABLE_ONLINE_REPOS" and activate if required at all (e.g. post-release tests) PR#4679.
- Avoid big source in general. Optional: Only sync the relevant parts of the source repo for corresponding tests, e.g. zypper_info on source packages or a toolchain or compile test. Alternative: Note down in tickets
- Subject changed from [opensuse][functional] Sync all repos for TW and Leap for all tested versions to [opensuse][functional][medium] Sync all repos for TW and Leap for all tested versions
- Description updated (diff)
- Status changed from New to Workable
Discussed with openSUSE RMs regarding online repos: We have still the online
published repos enabled in many openQA tests.
- Is it possible to sync all repos, including non-oss, debug, source,
update? -> space should not be the problem on o3 but syncing big repos
would delay the testing. Probably we already sync debug. We should make
sure non-oss is synced as well. Avoid big source in general. Optional:
Only sync the relevant parts of the source repo for corresponding tests,
e.g. zypper_info on source packages or a toolchain or compile test
- Is there any build validation test where we need the online published
repos enabled? -> No, we could not think of any. This confirms the
hypothesis by okurz that relying on them would be an invalid test by
definition.
- Due date set to 2018-03-27
- Target version set to Milestone 15
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Blocked
Figuring out how to conduct rsync.pl deployment to o3 first.
- Status changed from Blocked to In Progress
Here are the instructions how to handle rsync.pl update:
riafarov: o3:/opt/openqa-scripts/HOW_TO_MODIFY explains how to do that. I wonder why that file is not in the repo itself. maybe you can move that file there? do you have ssh access to o3?
riafarov: http://susepaste.org/31955383 if you don't have access to the file
- Due date changed from 2018-03-27 to 2018-04-10
- Related to action #20892: [perl] product-builder: adjust openQA rsync.pl added
- Description updated (diff)
- Status changed from In Progress to Feedback
Would the rsync.pl be able to be used outside SUSE network to sync my local openQA server instance ?
michel_mno wrote:
Would the rsync.pl be able to be used outside SUSE network to sync my local openQA server instance ?
Well, first problem I see is that rsync.pl is not open-sourced. Next problem I see currently o3 syncs from an iternal host. Can we access the TW + leap snapshots that are under current testing from the outside?
okurz wrote:
I was not able to access them using rsync from R&D network, but those work if you add them using zypper, so I guess something can be done here, but not with rsync.pl.
michel_mno wrote:
Would the rsync.pl be able to be used outside SUSE network to sync my local openQA server instance ?
Well, first problem I see is that rsync.pl is not open-sourced. Next problem I see currently o3 syncs from an iternal host. Can we access the TW + leap snapshots that are under current testing from the outside?
So as of now we only have problems with source repos as we don't want to sync whole repos cause of the single package, so this is remaining part to implement it in rsync.pl and then adjust the test to add OSS source repo.
As per access from outside, we have tested that zypper is able to access snapshot repos outside of R&D network, however you cannot list directories/files over http (gets redirected to https) or ftp.
If full path is known, you should be able to access it over http:
wget http://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-non-oss-i586-x86_64-Snapshot20180324/repodata/repomd.xml
- Related to action #34288: [qam] test fails in zypper_info - zypper_info shouldn't be started added
All found issues are fixed. zypper_info is still an issue, as well as yast update module in yast control center
- Due date changed from 2018-04-10 to 2018-04-24
- Status changed from Feedback to Resolved
So we reached safe state, remaining tasks are mentioned in https://progress.opensuse.org/issues/34732 which is follow up.
Acceptance criteria here was too optimistic, we cannot and should not sync all and always replace. Resolving this ticket.
- Related to action #36333: [opensuse][y][medium] Invalid repositories - failing kate install added
Also available in: Atom
PDF