Critical The WMCO v7 and v8 pipelines have been failing due to build issues with kubelet. This needs to be fixed.
2024-05-02 19:59:23,549 - atomic_reactor.tasks.binary_container_build - INFO - Go compliance shim [412] [rhel-9-golang-1.19][openshift-golang-builder]: invoking real go binary 2024-05-02 19:59:23,549 - atomic_reactor.tasks.binary_container_build - INFO - error obtaining VCS status: exit status 128 2024-05-02 19:59:23,559 - atomic_reactor.tasks.binary_container_build - INFO - Use -buildvcs=false to disable VCS stamping. 2024-05-02 19:59:23,559 - atomic_reactor.tasks.binary_container_build - INFO - Go compliance shim [412] [rhel-9-golang-1.19][openshift-golang-builder]: Exited with: 1 2024-05-02 19:59:23,559 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] Call tree: 2024-05-02 19:59:23,566 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] 1: /remote-source/build/windows-machine-config-operator/kubelet/hack/lib/golang.sh:747 kube::golang::build_some_binaries(...) 2024-05-02 19:59:23,574 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] 2: /remote-source/build/windows-machine-config-operator/kubelet/hack/lib/golang.sh:906 kube::golang::build_binaries_for_platform(...) 2024-05-02 19:59:23,574 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] 3: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) 2024-05-02 19:59:23,574 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] Call tree: 2024-05-02 19:59:23,574 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] 1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) 2024-05-02 19:59:23,574 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] Call tree: 2024-05-02 19:59:27,075 - atomic_reactor.tasks.binary_container_build - INFO - !!! [0502 19:59:23] 1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) 2024-05-02 19:59:27,076 - atomic_reactor.tasks.binary_container_build - INFO - make[1]: *** [Makefile:92: all] Error 1 2024-05-02 19:59:27,078 - atomic_reactor.tasks.binary_container_build - INFO - make[1]: Leaving directory '/remote-source/build/windows-machine-config-operator/kubelet' 2024-05-02 19:59:27,078 - atomic_reactor.tasks.binary_container_build - INFO - make: *** [Makefile:235: kubelet] Error 2 2024-05-02 19:59:27,078 - atomic_reactor.tasks.binary_container_build - INFO - 2024-05-02 19:59:27,078 - atomic_reactor.tasks.binary_container_build - ERROR - Error: building at STEP "RUN make kubelet": while running runtime: exit status 2
This issue has been seen before for azure-cloud-node-manager.exe, and it was fixed by disabling buildvcs. This is most likely something we cannot freely do to the kubelet build, as we depend on the git versioning to advertise the current version of the kubelet to cluster.
- relates to
-
RHEL-36097 go-toolset-container: Builds fail if `.git` directory is present
-
- New
-
- links to
-
RHBA-2024:129984
Red Hat OpenShift for Windows Containers 8.1.3 product release
- mentioned on
(1 mentioned on)