Closed jschmid1 closed 5 years ago
@susebot run teuthology
Commit 700a2e511741fbeebd5b7262748e62d8fca0bc3d is NOT OK for suite $SUITE. Check tests results in the Jenkins job: http://storage-ci.suse.de:8080/job/pr-deepsea/205/
something seems to be not right with the CI. @kshtsk @smithfarm
@susebot run teuthology
Commit 127333ea95e73dca810829e9157729f59101df32 is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://storage-ci.suse.de:8080/job/pr-deepsea/207/
Abort, retry, ignore? [a/r/i/...? shows all options] (a): a
[91mMedia source 'http://download.opensuse.org/distribution/leap/15.1/repo/oss/' does not contain the desired medium
[0m[91mProblem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
Abort, retry, ignore? [a/r/i/...? shows all options] (a): a �[91mMedia source 'http://download.opensuse.org/distribution/leap/15.1/repo/oss/' does not contain the desired medium �[0m�[91mProblem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint.
Yeah, that looks like you need to refresh the repositories @kshtsk
retest this please
@susebot run teuthology
Commit 127333ea95e73dca810829e9157729f59101df32 is OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://storage-ci.suse.de:8080/job/pr-deepsea/210/
1) Error messages should not be executed.
2) Unify error messages in case
wal
and nodb
3) Fix filestore deployment
Checklist: