Open gsmet opened 2 years ago
/cc @geoand, @iocanel
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
The build is still failing:
Build fixed:
Unfortunately, the build failed:
The build is still failing:
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
The build is still failing:
The build is still failing:
Build fixed:
Unfortunately, the build failed:
The build is still failing:
The build is still failing:
The build is still failing:
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
Build fixed:
Unfortunately, the build failed:
The build is still failing:
@iocanel OpenShift + S2i is broken by https://github.com/quarkusio/quarkus/pull/34241 (see openshift-s2i-build-and-deploy/pom.xml ........... FAILED from the logs):
Warning: ARNING] [io.quarkus.container.image.openshift.deployment.OpenshiftProcessor] An exception: 'Can't instantiate binary build, due to error reading/writing stream. Can be caused if the output stream was closed by the server.See if something's wrong in recent events in Cluster = FailedMount openshift-s2i-build-and-deploy-1-build.1775e7c07a4d6d21 MountVolume.SetUp failed for volume "openshift-s2i-build-and-deploy-push-secret-push" : secrets "openshift-s2i-build-and-deploy-push-secret" not found
I'm now checking what's going on with openshift-with-output-directory-build-and-deploy
Both tests seem to work fine against openshift sandbox.
Will check if its an oc cluster up
thing.
Both tests seem to work fine against openshift sandbox.
You can reproduce it locally by adding:
export QUARKUS_CONTAINER_IMAGE_GROUP=quarkustesting
export QUARKUS_CONTAINER_IMAGE_TAG=b1626f4a2775be870c161462d7b3c6465d7b48c4
export QUARKUS_CONTAINER_IMAGE_REGISTRY=quay.io
cd integration-tests/kubernetes/maven-invoker-way
mvn clean install -Dopenshift-e2e-tests
This is what the OpenShift job is doing (see here).
Without these properties, these both tests also work for me, so I think the scenario OpenShift + quarkus.container-image.registry
is also broken (this is the test openshift-with-output-directory-build-and-deploy
). I guess because after the changes, the quarkus.container-image.registry
takes precedence over the OpenShift or S2i extensions, but it still tries to start the build which makes the quarkus deployments fail.
This warning is suspicious:
[WARNING] [io.quarkus.container.image.openshift.deployment.OpenshiftProcessor] An external image registry has been specified, but no push secret or credentials.
Note that I'm also using OpenShift sandbox.
Then I guess we need to fix the CI so that it also passes credentials.
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
The build is still failing:
This issue will be open and closed dependent on the state of OpenShift end-to-end testing building against Quarkus main snapshot.
If you have interest in being notified of this subscribe to the issue.