My guess is that this is due to running this both on GitHub Actions and
Jenkins. The Actions run succeeded, so I don't think we need to worry about
this - https://github.com/apache/beam/actions/runs/6714783844
It seems like for the metrics job the opposite happened - the Actions run
failing trigge
I took a quick look -- the error is the following:
*22:17:26* ERROR: (gcloud.container.clusters.update) ResponseError:
code=400, message=Operation
operation-1698804621818-e9c8fe33-d4a2-44cd-86aa-9c4e09dea259 is
currently upgrading cluster io-datastores. Please wait and try again
once it is done.
Something went wrong during the automatic credentials rotation for
IO-Datastores Cluster, performed at Wed Nov 01 00:52:45 UTC 2023. It may be
necessary to check the state of the cluster certificates. For further details
refer to the following links:
* Failing job:
https://ci-beam.apache.org/j
Update - the job has been successfully run and the permanent fix is merged.
I'll follow up with a PR to fix the links in the failure email.
On Thu, Dec 1, 2022 at 2:00 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Something went wrong during the automatic credentials rotation for
Something went wrong during the automatic credentials rotation for
IO-Datastores Cluster, performed at Thu Dec 01 18:58:27 UTC 2022. It may be
necessary to check the state of the cluster certificates. For further details
refer to the following links:
* https://ci-beam.apache.org/job/beam_SeedJo
Something went wrong during the automatic credentials rotation for
IO-Datastores Cluster, performed at Thu Dec 01 18:58:27 UTC 2022. It may be
necessary to check the state of the cluster certificates. For further details
refer to the following links:
* https://ci-beam.apache.org/job/beam_SeedJo
Does that have potential to break other things? We could presumably also
update
https://github.com/apache/beam/blob/4718cdff87fed4f92636e94dbf3a04c2315d6a95/.test-infra/jenkins/job_IODatastoresCredentialsRotation.groovy#L38
to pool-1 instead.
I put up https://github.com/apache/beam/pull/24466 in
Thanks for reporting. I have bumped the pool size of io-datastore as we
have more tests being added and the default-pool frequently becomes
unschedulable due to memory constraints. A simple fix is just rename the
'pool1' back to 'default-pool'.
On Thu, Dec 1, 2022 at 1:26 PM Danny McCormick
wrote
Yes, I was just starting to look into this. Looks like this is the result
of this job failing -
https://github.com/apache/beam/blob/ec2a07b38c1f640c62e7c3b96966f18b334a7ce9/.test-infra/jenkins/job_IODatastoresCredentialsRotation.groovy#L49
The error is:
```
*21:25:58* + gcloud container clusters
Is there something we need to do here?
On Thu, Dec 1, 2022 at 10:10 AM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Something went wrong during the automatic credentials rotation for
> IO-Datastores Cluster, performed at Thu Dec 01 15:00:47 UTC 2022. It may be
> necessary to check
Something went wrong during the automatic credentials rotation for
IO-Datastores Cluster, performed at Thu Dec 01 15:00:47 UTC 2022. It may be
necessary to check the state of the cluster certificates. For further details
refer to the following links:
* https://ci-beam.apache.org/job/beam_SeedJo
Something went wrong during the automatic credentials rotation for
IO-Datastores Cluster, performed at Thu Dec 01 00:53:08 UTC 2022. It may be
necessary to check the state of the cluster certificates. For further details
refer to the following links:
* https://ci-beam.apache.org/job/beam_SeedJo
12 matches
Mail list logo
