[Bug] on openEuler 22.03 (LTS-SP4) system, cloudberrydb-1.6.0 install with source code ,error occured when gpinitsystem

[fsmiledream]

Cloudberry Database version

cloudberrydb-1.6.0

What happened

20240906:18:23:28:112430 gpinitsystem:cloudberrydb1:gpadmin-[INFO]:-No errors generated from parallel processes
20240906:18:23:28:112430 gpinitsystem:cloudberrydb1:gpadmin-[INFO]:-Restarting the CloudberryDB instance in production mode
Traceback (most recent call last):
File "/usr/local/cloudberrydb/bin/gpstop", line 9, in
from gppylib.mainUtils import *
File "/usr/local/cloudberrydb/lib/python/gppylib/mainUtils.py", line 31, in
from gppylib.commands import gp, unix
File "/usr/local/cloudberrydb/lib/python/gppylib/commands/gp.py", line 22, in
from gppylib.db import dbconn
File "/usr/local/cloudberrydb/lib/python/gppylib/db/dbconn.py", line 15, in
from gppylib.commands.unix import UserId
File "/usr/local/cloudberrydb/lib/python/gppylib/commands/unix.py", line 17, in
from gppylib.commands.base import *
File "/usr/local/cloudberrydb/lib/python/gppylib/commands/base.py", line 32, in
from pg import DB
File "/usr/local/lib/python3.9/site-packages/pg/init.py", line 3
async,
^
SyntaxError: invalid syntax
20240906:18:23:28:112430 gpinitsystem:cloudberrydb1:gpadmin-[FATAL]:-Error from CloudberryDB instance shutdown, check log files Script Exiting!

What you think should happen instead

No response

How to reproduce

The err is the same as 1.5.4 with rpm/source . now 1.6.0rpm is repaired，but 1.6.0 install with source code is still same error

Operating System

openEuler 22.03 (LTS-SP4)

Anything else

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct.

[tuhaihe]

Hi @Zhangbaowen-Hashdata @edespino could you help take a look? Thanks.

[yihong0618]

solution

pip3 uninstall pg
pip3 uninstall PyGreSQL

then
pip3 install -U PyGreSQL

[yihong0618]

solution

pip3 uninstall pg pip3 uninstall PyGreSQL

then pip3 install -U PyGreSQL

---

we can reproduce this by

pip3 uninstall pg
pip3 uninstall PyGreSQL

then
pip3 install -U PyGreSQL
pip3 install pg

then error happened

then use the solution can fix this.

[avamingli]

solution

pip3 uninstall pg pip3 uninstall PyGreSQL

then pip3 install -U PyGreSQL

Thanks @yihong0618 .
Generally, I think we need to update XXX.dependency if XXX is officially supported to avoid such issue.
@tuhaihe @Zhangbaowen-Hashdata Could anyone of you help to track this, thanks.

[fsmiledream]

@yihong0618 Thank you very much! Using your solution ,I can also initsystem successfully.
I also hope source code can be fixed and updated .

[yihong0618]

@yihong0618 Thank you very much! Using your solution ,I can also initsystem successfully. I also hope source code can be fixed and updated .

my pleasure

[tuhaihe]

Thanks @yihong0618 !
Hi @avamingli I think we should update the doc on building from source code. Let me talk with our devops team.

[gongxun0928]

@tuhaihe @avamingli @Zhangbaowen-Hashdata We need to use pip3 install -r ../../python-dependencies.txt like Readme.CentOS.bash. In this way, Python dependencies will use a fixed version instead of relying on the version in the apt source.

[avamingli]

@tuhaihe @avamingli @Zhangbaowen-Hashdata We need to use pip3 install -r ../../python-dependencies.txt like Readme.CentOS.bash. In this way, Python dependencies will use a fixed version instead of relying on the version in the apt source.

+1, that's what I suggest.
We should be clear which OS is officially supported(probably Release team knows well about it) , update xxx_dependencies.txt by the way,

[my-ship-it]

@Zhangbaowen-Hashdata, Hi Baowen, could you please try the suggestions above?

[Baowen648]

@Zhangbaowen-Hashdata, Hi Baowen, could you please try the suggestions above?

I will conduct a verification locally first, and if there are no issues, I will propose a new PR.

[yjhjstz]

@Zhangbaowen-Hashdata, Hi Baowen, could you please try the suggestions above?

I will conduct a verification locally first, and if there are no issues, I will propose a new PR.

any progress ?

[Baowen648]

I've raised the PR need to wait for the merger.
#664