[Failing Test]: beam_PostRelease_Python_Candidate script broken

Abacn commented 1 year ago

What happened?

test: https://ci-beam.apache.org/job/beam_PostRelease_Python_Candidate/

This test suite is documented as part of release candidate validation. From the history the last successful run was V2.46.0 rc1; and as of V2.49.0 rc1 it is broken. Error message:

18:53:26 ERROR: Failed to create topic [projects/apache-beam-testing/topics/wordstream-python-topic-1]: Resource already exists in the project (resource=wordstream-python-topic-1).
18:54:02 ERROR: (gcloud.pubsub.topics.create) Failed to create the following: [wordstream-python-topic-1].

Issue Failure

Failure: Test is continually failing

Issue Priority

Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)

Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Abacn commented 1 year ago

example run: #27463

kennknowles commented 1 year ago

This is kind of minor, but maybe we can clarify what this suite actually does and name it better.

kennknowles commented 1 year ago

I only see 2.46.0 and 2.49.0 runs. Is it not actually in use and the instructions are wrong?

Abacn commented 1 year ago

This is kind of minor, but maybe we can clarify what this suite actually does and name it better. I only see 2.46.0 and 2.49.0 runs. Is it not actually in use and the instructions are wrong?

Changed to P2 since we now understand the cause well (not due to Beam).

It is referred in release documentation as part of release validation: https://github.com/apache/beam/blob/c8f68f92097de33fe2c6863344404a1b9922ae27/website/www/site/content/en/contribute/release-guide.md?plain=1#L843 checking the history this step has long been existed.

Validation may be done with this automated process or run manually. Since 2.46.0 passed the validation, the issue seems to be more recent (delete then create topic with same name failing).

Nevertheless I think a proper fix to the script should be avoiding create topic with same name twice. Leave this issue open for this task.

apache / beam