sinnykumari added a new comment to an issue you are following:
``
This looks like a race condition where the updates compose was
running at the same time as the twoweek nightly atomic run.
updates compose ostree tasks started at 08:48:45 and ended at 09:27:07:
2018-06-25 08:48:45 [INFO ] [BEGIN] ---------- PHASE: OSTREE ----------
...
2018-06-25 09:27:07 [INFO ] [DONE ] ---------- PHASE: OSTREE ----------
twoweek compose image build tasks started at 09:17:42 and finished at 09:43:04:
2018-06-25 09:17:42 [INFO ] [BEGIN] ---------- PHASE: IMAGE_BUILD ----------
...
2018-06-25 09:43:04 [IMAGE_BUILD ] [INFO ] [DONE ] Creating image (formats:
qcow2-raw-xz, arches: aarch64-ppc64le-x86_64, variant: AtomicHost, subvariant: AtomicHost)
(task id: 27853671)
Ah I see.
I wonder if it was a race condition, why did it pick OSTree version 28.20180623.0 instead
of 28.20180624.0 ?
mark this as another reason we want to generate the ISO and VM images
inside the updates compose and not as a separate compose.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7585