okd-project / okd-coreos-pipeline Goto Github PK

When running pipeline : kubectl create -n okd-coreos -f environments/kind/pipelineruns/okd-coreos-4.15-dev-pipelinerun.yaml

Task cosa-build-baseos fails in step fetch-and-build-baseos with error:

error: Packages not found: ose-aws-ecr-image-credential-provider
failed to execute cmd-fetch: exit status 1

After following the instructions, the builds do not work on the latest OKD 4.11 from the current CRC.
The OpenShift instructions for Tekton show the setup of a service account with anyuid:
https://tekton.dev/docs/pipelines/install/ (OpenShift tab, which mentions a non-existing system account ?).

Unfortunately that does not seem to work.
I can imagine that because of the kvm plugin it uses something may go wrong on CRC ( OpenShift Local ) ?
I would just think that when building OKD images, OKD on CRC would be a logical choice, so whatever is needed should be documented, or mentioned that it does not work following the instructions.

Implement a sane strategy to prune old pipelineruns on op1st

see:
https://docs.openshift.com/container-platform/4.11/cicd/pipelines/automatic-pruning-taskrun-pipelinerun.html

This is the same issue as https://issues.redhat.com/browse/ART-4352 which is for RHCOS.

Basically AFAICS today OKD builds a custom image derived from FCOS. Let's publish that image in a convenient place external to the release image so it can be used in external container builds, like https://github.com/coreos/coreos-layering-examples

The release in sig-cloud-okd repo is hardcoded which is consumed by all the releases pipelines.
I guess it's not critical currently as 4.15 may not diverged too much from 4.14, but it might be in the future.

We can fix it with a sed 's/4.14/4.15/' alike command after the cosa-init execution as we do for the RPM artifacts

But we first need to tag the builds in the cloud9s-okd-4.15-release tag
I can do the tags, and even build the new NVRs but I'd need the exact version of what's in 4.15 release