Brief Description
-----------------
Docker image "armada" failed in Jenkins recently due to a transient network outage. Jenkins retried building it, and these subsequent attempts failed because the 1st attempt didn't cleanup after itself (I think). Error handling needs improvement. Its not clear whether this logic is in armada's (custom) build script or in the generic build-stx-images.sh .
Severity
--------
Minor
Steps to Reproduce
------------------
See logs
Expected Behavior
------------------
Build should recover from transient errors
Actual Behavior
----------------
1st failure causes subsequent attempts to fail as well.
Reproducibility
---------------
Seen once
System Configuration
--------------------
N/A
Branch/Pull Time/Commit
-----------------------
master/2023-09-27
Last Pass
---------
N/A
Timestamp/Logs
--------------
From the bottom of https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230927T060059Z/logs/build-docker-images-stable.log.txt:
[2023-09-27T15:16:02.341Z] Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
[2023-09-27T15:16:02.592Z] + git clone https://github.com/yaml/libyaml.git
[2023-09-27T15:16:02.592Z] Cloning into 'libyaml'...
[2023-09-27T15:16:02.592Z] fatal: unable to access 'https://github.com/yaml/libyaml.git/': Failed to connect to github.com port 443: No route to host
[2023-09-27T15:16:04.454Z] The command '/bin/sh -c set -ex && buildDeps=' automake gcc libssl-dev libtool make python3-pip ' && apt-get -qq update && apt-get install -y $buildDeps git --no-install-recommends && git clone https://github.com/yaml/libyaml.git && cd libyaml && git checkout $LIBYAML_VERSION && ./bootstrap && ./configure && make && make install && cd .. && rm -fr libyaml && python3 -m pip install -U pip && pip3 install -r requirements.txt --no-cache-dir && apt-get purge -y --auto-remove $buildDeps && apt-get autoremove -yqq --purge && apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* /usr/share/man /usr/share/doc /usr/share/doc-base' returned a non-zero code: 128
[2023-09-27T15:16:04.454Z] make: *** [Makefile:109: build_armada] Error 128
[2023-09-27T15:16:04.454Z] Failed to make armada-image image. Aborting...
[2023-09-27T15:16:04.454Z] Command (bash) failed, attempt 1 of 3.
[2023-09-27T15:16:04.454Z] Waiting 30 seconds before retrying...
[2023-09-27T15:16:36.380Z] Running: bash build-armada-image.sh armada-image jenkins/armada-image:master-debian-stable-build
[2023-09-27T15:16:36.380Z] /tmp/armada-ulCcwTZ5ot /localdisk/loadbuild/jenkins/debian-master/std/build-images/armada
[2023-09-27T15:16:36.380Z] Cloning into 'integ'...
[2023-09-27T15:16:36.380Z] /localdisk/loadbuild/jenkins/debian-master/std/build-images/armada
[2023-09-27T15:16:36.380Z] /localdisk/loadbuild/jenkins/debian-master/std/build-images/armada/patches /localdisk/loadbuild/jenkins/debian-master/std/build-images/armada
[2023-09-27T15:16:36.380Z] error: patch failed: charts/armada/templates/deployment-api.yaml:178
[2023-09-27T15:16:36.380Z] error: charts/armada/templates/deployment-api.yaml: patch does not apply
[2023-09-27T15:16:36.380Z] error: patch failed: charts/armada/values.yaml:206
Test Activity
-------------
N/A
Workaround
----------
N/A
Armada image removed by https:/