action #105256
closed
[qac] openqa_bootstrap_container: unable to access https://github.com/...
Added by dimstar almost 3 years ago.
Updated about 2 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-openqa_bootstrap_container@64bit fails in
openqa_bootstrap_container
The bootstrap script reports fatal: unable to access 'https://github.com/os-autoinst/os-autoinst-distri-opensuse.git/': SS: certificate problem: unable to get local issuer certificate
Test suite description¶
Maintainer: dheidler. Install openQA in nspawn container using openqa-bootstrap-container script.
Reproducible¶
Fails since (at least) Build 20220113
Expected result¶
Last good: 20220112 (or more recent)
Further details¶
Always latest result in this scenario: latest
@dheidler, this module is maintained by you but I assign it to qac. Please clarify which team will take over.
- Subject changed from openqa_bootstrap_container: unable to access https://github.com/... to [qac] openqa_bootstrap_container: unable to access https://github.com/...
yep, good assignment as dheidler wanted to fork os-autoinst-distri-openQA ;)
The issue is this:
# There are non-fatal errors when zyppering inside chroot, so ignoring errors on the next line
# Allow command line options without quotes
# shellcheck disable=SC2086
zypper -n --root $CONTAINER_PATH install --no-recommends -ly $PKGS_TO_INSTALL || test $? = 107
Those errors are not fatal to zypper, but they should be treated as such:
(428/550) Installing: ca-certificates-mozilla-2.52-1.2.noarch ..............................................................................................................................................................................[done]
Additional rpm output:
/sbin/update-ca-certificates: line 110: /dev/fd/63: No such file or directory
Without /dev/ being mounted, update-ca-certificates fails and SSL connections won't work.
There are also some other packages affected by this.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: openqa_bootstrap_container
https://openqa.opensuse.org/tests/2179684
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: openqa_bootstrap_container
https://openqa.opensuse.org/tests/2206673
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
- Status changed from New to Resolved
This test has been reliably passing in the last three months (as much as the test history shows)
I don't think at this time we can specify what fixed it (I somewhat recall zypp being involved in possibly addressing it); as nobody is probably going to look at it from here on,let's close the ticket
Also available in: Atom
PDF