CREATE IF NOT EXISTS failed for background DDL

[xxchan]

Describe the bug

User feedback: https://web.clearfeed.app/collections/4875?request=332

dev=> show jobs;
┌────┬──────────────────────────────────────────────────────────────────────────────────┬──────────────┐
│ Id │                                    Statement                                     │   Progress   │
├────┼──────────────────────────────────────────────────────────────────────────────────┼──────────────┤
│ 17 │ CREATE MATERIALIZED VIEW IF NOT EXISTS mv1 AS SELECT range(1, x * 100000) FROM t │ 0.00% (0/99) │
└────┴──────────────────────────────────────────────────────────────────────────────────┴──────────────┘
(1 row)

Time: 18.766 ms
dev=> select * from mv1;
ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: Catalog error
  2: table or source not found: mv1

Time: 3.064 ms
dev=> create materialized view if not exists mv1 as select range(1,x*100000) from t;
ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: Catalog error
  2: gRPC request to meta service (call `/ddl_service.DdlService/CreateMaterializedView`) failed: Some entity that we attempted to create already exists
  3: table with name mv1 exists

Time: 36.995 ms
dev=> 
dev=> create materialized view if not exists mv1 as select range(1,x*100000) from t;
ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: Catalog error
  2: gRPC request to meta service (call `/ddl_service.DdlService/CreateMaterializedView`) failed: Some entity that we attempted to create already exists
  3: table with name mv1 exists

Time: 53.492 ms
dev=> create materialized view mv1 as select range(1,x*100000) from t;
ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: Catalog error
  2: gRPC request to meta service (call `/ddl_service.DdlService/CreateMaterializedView`) failed: Some entity that we attempted to create already exists
  3: table with name mv1 exists

Suspicious code:
I just noticed in the code that for BACKGROUND_DDL, we don’t wait_version for the DDL here, so I’m thinking it may be possible that the frontend table catalog isn’t aware of the already existing table, so send the DDL request to meta, which was rejected by meta later.

risingwave/src/frontend/src/catalog/catalog_service.rs

Lines 297 to 299 in 9ed1c60

	if matches!(create_type, PbCreateType::Foreground) {
	self.wait_version(version).await?
	}

Error message/log

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[xxchan]

@yezizp2012 can you help with this issue?