[MCOL-5088] Docker: Cluster creation did not finish waiting for PM1 to be initialized -develop only Created: 2022-05-13  Updated: 2023-07-02

Status: Stalled
Project: MariaDB ColumnStore
Component/s: CI
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Daniel Lee (Inactive) Assignee: Roman
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MCOL-5050 Worker node crash after DDL . Possibl... Closed

 Description   

Build tested:
Docker image: mariadb/enterprise-columnstore-dev:develop
DIGEST: 0ef42dd37b31

When creating a single or multiple cluster, provisioning failed to finish while waiting for PM1 to be initialized.

To reproduce

1. Clone https://github.com/mariadb-corporation/mariadb-skysql-columnstore-docker.git repo

git clone https://github.com/mariadb-corporation/mariadb-skysql-columnstore-docker.git myrepo

2. cd myrepo
3. copy .env_exsample to .env. Edit .env and change IMAGE_NAME as the following

IMAGE_NAME=mariadb/enterprise-columnstore-dev:develop

4. Create cluster

docker-compose up -d && docker exec -it mcs1 cluster-demo

MM2018-Daniel:mdbdocker dlee$ docker-compose up -d && docker exec -it mcs1 cluster-demo
Creating network "mariadb-skysql-columnstore-docker_default" with the default driver
Creating volume "mariadb-skysql-columnstore-docker_data1" with default driver
Creating volume "mariadb-skysql-columnstore-docker_data2" with default driver
Creating volume "mariadb-skysql-columnstore-docker_data3" with default driver
Creating volume "mariadb-skysql-columnstore-docker_storagemanager" with default driver
Pulling pm3 (mariadb/enterprise-columnstore-dev:develop)...
develop: Pulling from mariadb/enterprise-columnstore-dev
1a930d163dca: Pull complete
f5a73ad70827: Pull complete
32ce0d5fe200: Pull complete
e33ceabf414c: Pull complete
045a1d17846f: Pull complete
22cc7585e0bd: Pull complete
e7baf1bd9fd4: Pull complete
d61bc23707e0: Pull complete
5d85bed45fba: Pull complete
374bbb6962b4: Pull complete
e45522a6663b: Pull complete
48aac212709c: Pull complete
951056ddaaef: Pull complete
d5a59be05173: Pull complete
Digest: sha256:0ef42dd37b31f13a76b05fd5dddc8e42099a03ac3eac8cb49e6c3fcdb812bf6f
Status: Downloaded newer image for mariadb/enterprise-columnstore-dev:develop
Pulling mx1 (mariadb/maxscale:)...
latest: Pulling from mariadb/maxscale
1a930d163dca: Already exists
b27873e05c9b: Pull complete
ba6151aeb825: Pull complete
fdc61be8b9a4: Pull complete
71b2e942c58c: Pull complete
a9821c0e851e: Pull complete
c2379ead24e3: Pull complete
935799117e3c: Pull complete
b7aa31fa58c1: Pull complete
9e4e65713f74: Pull complete
dc7dbe210428: Pull complete
Digest: sha256:b81efb9fcd437fc57c4eaab6757bbb399e66d7454fe812dfa4fe9e22336f7d9d
Status: Downloaded newer image for mariadb/maxscale:latest
Creating mcs3 ... done
Creating mcs2 ... done
Creating mcs1 ... done
Creating mx1  ... done
Waiting for PM1 to be initialized ..........................................................................................................................



 Comments   
Comment by Roman [ 2022-05-19 ]

Presumably this is MCOL-5050. The develop didn't have the proper fix when docker image had been first tested.

Comment by alexey vorovich (Inactive) [ 2022-05-19 ]

Great , thnks

So dleeyh will need to wait for the next CRON build and test ?

Comment by Daniel Lee (Inactive) [ 2022-05-20 ]

Docker images tested: mariadb/enterprise-columnstore-dev:develop

Digest: sha256:dbee1cf30fefdcf3495d391f16f699ca44ca73148b52bbd120369f75c87aa2c4

This new image still has the reported issues. :develop-6 is fine.

Generated at Thu Feb 08 02:55:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.