action #117373
closedBCI failure in golang-1.19: cannot use path@version syntax in GOPATH mode
100%
Description
Test failure in _root_BCI-tests_go_docker
test:
GOPATH=/tmp/tmphlrolqq5/gopath go install github.com/rancher/dapper@latest
package github.com/rancher/dapper@latest: cannot use path@version syntax in GOPATH mode
e.g. in scenario sle-15-SP4-BCI-Updates-aarch64-lang_image_on_SLES_15-SP1@aarch64-virtio fails in
_root_BCI-tests_go_docker
Updated by ph03nix over 2 years ago
My suspect is: https://github.com/SUSE/BCI-tests/pull/171
Updated by ph03nix over 2 years ago
However it run on the current golang:1.19 container:
# podman run --rm -ti registry.suse.com/bci/golang:1.19
14ec6a8a9596:/ # GOPATH=/tmp/tmphlrolqq5/gopath go install github.com/rancher/dapper@latest
go: downloading github.com/rancher/dapper v0.6.0
go: downloading github.com/sirupsen/logrus v1.5.0
go: downloading github.com/urfave/cli v1.22.4
go: downloading github.com/mattn/go-isatty v0.0.12
go: downloading golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e
go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.0
go: downloading github.com/russross/blackfriday/v2 v2.0.1
go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0
14ec6a8a9596:/ #
Now checking with the to-test container as well:
podman run --rm -ti registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19
91b6bae36916:/ # GOPATH=/tmp/tmphlrolqq5/gopath go install github.com/rancher/dapper@latest
go: downloading github.com/rancher/dapper v0.6.0
go: downloading github.com/sirupsen/logrus v1.5.0
go: downloading github.com/urfave/cli v1.22.4
go: downloading github.com/mattn/go-isatty v0.0.12
go: downloading golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e
go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.0
go: downloading github.com/russross/blackfriday/v2 v2.0.1
go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0
Both work. Hmm....
Updated by ph03nix over 2 years ago
I see that part of the test run succeed. I restarted the failing ones, let's see in an hour what happens.
Updated by ph03nix over 2 years ago
There are different issues here present.
RUN curl -sLf https://github.com/rancher/machine/releases/download/${CATTLE_MACHINE_VERSION}/rancher-machine-${ARCH}.tar.gz | tar xvzf - -C /usr/bin
---> Running in f2c617ab4704\n\x1b[91m\ngzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
package github.com/rancher/dapper@latest: cannot find package "github.com/rancher/dapper@latest"
Looks like the introduced dapper package is not available on ppc64le
can't load package: package github.com/rancher/dapper@latest: cannot find package "github.com/rancher/dapper@latest" in any of:\n\t/usr/lib64/go/1.10/src/github.com/rancher/dapper@latest (from $GOROOT)
Issue is only present on 15 and 15-SP1, 12-SP5, and 15-SP2+ are just fine on s390x and x86_64 and aarch64, e.g. https://openqa.suse.de/tests/9624231
Updated by ph03nix over 2 years ago
So, on ppc64le the rancher test fails because it's not available. On s390x we have part of the test runs passing and some of them failing for the same reason, which does not make any sense. I cloned a passing job run as https://openqa.suse.de/tests/9629475 to have a reference test run from now.
Updated by ph03nix over 2 years ago
Cannot reproduce the issue on SLES15:
sles15:~/BCI-tests # docker run --rm -ti registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19
Unable to find image 'registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19' locally
1.19: Pulling from suse/sle-15-sp4/update/cr/totest/images/bci/golang
4b638a0b0919: Pull complete
25adbd4c951a: Pull complete
Digest: sha256:9e0aa91860085bd2f6e42e2ff39ca735d4b336feaa15cf89c17fe01ea5987e2c
Status: Downloaded newer image for registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19
211288d95763:/ # GOPATH=/tmp/tmptt3krvkt/gopath go install github.com/rancher/dapper@latest
go: downloading github.com/rancher/dapper v0.6.0
go: downloading github.com/sirupsen/logrus v1.5.0
go: downloading github.com/urfave/cli v1.22.4
go: downloading github.com/mattn/go-isatty v0.0.12
go: downloading golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e
go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.0
go: downloading github.com/russross/blackfriday/v2 v2.0.1
go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0
211288d95763:/ # cat /etc/os-release
NAME="SLES"
VERSION="15-SP4"
VERSION_ID="15.4"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP4"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp4"
DOCUMENTATION_URL="https://documentation.suse.com/"
211288d95763:/ # exit
csles15:~/BCI-tests # cat /etc/os-release
NAME="SLES"
VERSION="15"
VERSION_ID="15"
PRETTY_NAME="SUSE Linux Enterprise Server 15"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15"
sles15:~/BCI-tests #
Updated by ph03nix over 2 years ago
Ok, see https://suse.slack.com/archives/C02CGKBCGT1/p1664454357648809
We agreed, that for this issue we're gonna mark the test runs as softfailure, as long as at least one build per architecture passes.
Updated by dancermak over 2 years ago
ph03nix wrote:
Cannot reproduce the issue on SLES15:
sles15:~/BCI-tests # docker run --rm -ti registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19 Unable to find image 'registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19' locally 1.19: Pulling from suse/sle-15-sp4/update/cr/totest/images/bci/golang 4b638a0b0919: Pull complete 25adbd4c951a: Pull complete Digest: sha256:9e0aa91860085bd2f6e42e2ff39ca735d4b336feaa15cf89c17fe01ea5987e2c Status: Downloaded newer image for registry.suse.de/suse/sle-15-sp4/update/cr/totest/images/bci/golang:1.19 211288d95763:/ # GOPATH=/tmp/tmptt3krvkt/gopath go install github.com/rancher/dapper@latest go: downloading github.com/rancher/dapper v0.6.0 go: downloading github.com/sirupsen/logrus v1.5.0 go: downloading github.com/urfave/cli v1.22.4 go: downloading github.com/mattn/go-isatty v0.0.12 go: downloading golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.0 go: downloading github.com/russross/blackfriday/v2 v2.0.1 go: downloading github.com/shurcooL/sanitized_anchor_name v1.0.0 211288d95763:/ # cat /etc/os-release NAME="SLES" VERSION="15-SP4" VERSION_ID="15.4" PRETTY_NAME="SUSE Linux Enterprise Server 15 SP4" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15:sp4" DOCUMENTATION_URL="https://documentation.suse.com/" 211288d95763:/ # exit csles15:~/BCI-tests # cat /etc/os-release NAME="SLES" VERSION="15" VERSION_ID="15" PRETTY_NAME="SUSE Linux Enterprise Server 15" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15" sles15:~/BCI-tests #
You're reproducing it wrongly. You have to install dapper on the host. It's a wrapper around docker and cannot be installed in a container.
Updated by ph03nix over 2 years ago
dancermak wrote:
You're reproducing it wrongly. You have to install dapper on the host. It's a wrapper around docker and cannot be installed in a container.
And suddenly it becomes clear to me, why it's failing on SLES15 and 15-SP1. The go version is too low for them facepalm
Updated by ph03nix over 2 years ago
Fix for BCI: https://github.com/SUSE/BCI-tests/pull/175
Updated by ph03nix over 2 years ago
Now running into mapping output file failed: no space left on device
problems: https://openqa.suse.de/tests/9634169#step/_root_BCI-tests_go_docker/7
Updated by ph03nix about 2 years ago
Created a tutorial page on how to trigger new container HDD test runs: https://confluence.suse.com/pages/viewpage.action?pageId=1093763100
I also triggered the creation of new HDD test runs for ALL versions.
Updated by ph03nix about 2 years ago
- Related to action #117517: Automate the container host image generation process added
Updated by ph03nix about 2 years ago
- % Done changed from 0 to 80
Almost there, last issue are timeout issues on aarch64. Affected test run restarted.
Updated by ph03nix about 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
All tests are passing now