build: uft docker image: no error handling in build script
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Davlet Panech |
Bug Description
Brief Description
-----------------
The build script for uft docker image falsely reports success even when the build fails. This prevents the master build script from retrying the build step in case of intermittent network problems.
Severity
--------
Minor
Steps to Reproduce
------------------
Disconnect from the network and try to build uft using build-stx-images.
Expected Behavior
------------------
Build fails and returns non-zero to the shell
Actual Behavior
----------------
Build succeeds and returns zero to the shell
Reproducibility
---------------
Seen once
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
master/2024-04-17
Last Pass
---------
N/A
Timestamp/Logs
--------------
08:44:44 Building uft
08:44:44 get_git 'https:/
08:44:44 /localdisk/
08:44:44 Running: /bin/bash -c rm -rf UFT.clone_tmp && git clone --recursive https:/
<...>
08:44:45 Sending build context to Docker daemon 1.051MB
08:44:45 Step 1/37 : FROM registry.
08:45:31 missing or empty Content-Length header
08:45:31 Error response from daemon: No such image: jenkins/
08:45:31 Running: docker push starlingx/
Test Activity
-------------
N/A
Workaround
----------
N/A
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.10.0 stx.apps stx.build |
Changed in starlingx: | |
assignee: | nobody → Davlet Panech (dpanech) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /app-intel- ethernet- operator/ +/916117
Review: https:/