#655 pungi doesn't properly mark compose as failed when x86_64 cloud base image fails
Closed: Invalid 6 years ago Opened 6 years ago by dustymabe.

Yesterday's compose (log) was FINISHED_INCOMPLETE, but the cloud base image failed to build (koji task). The x86_64 cloud base image is blocking according to git so the state should have been DOOMED I think.


This is strange. According to the log the koji command returned exit code 0:

2017-06-21 14:46:27 [IMAGE_BUILD     ] [DEBUG   ] build-image outputs: {'output': "…", 'retcode': 0, 'task_id': 20078750}

When I try to run koji watch-task 20078750 I do get exit code of 1 though.

The output of koji image-build command has correct information about failure, but it does not include exit code.

There is code to wait for the task to finish that runs koji watch-task when the network goes down while the actual task is running. However that did not happen here, as the logs from that would be in the file linked above.

Has this happened again? I'm leaning towards closing this as a one time network fluke.

Metadata Update from @lsedlar:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata