does removing mysql-community package affects cloudera-manager-agent

[#1]

Hello! 

One of my cluster servers has this Mysql and its a old version which needs to be upgraded as per server team because of vulnerability issues. 

I see the server doesnt have any sql service or process running and our cluster uses Postgres , nor I am able to see the status of the mysql on the server

root 17280 7440 0 18:23 pts/0 00:00:00 grep --color=auto -i mysql 

so, when i try to remove the package it says the cloudera-manager-agent  is dependent on this mysql, but we never use mysql but only postgres as our hadoop DB .

Question: can I remove this or not ? does the CM agent need this mysql or not ?

If It is needed and I upgrade the Mysql to latest version how do I change the upgraded config to the cluster settings ?

Dependencies Resolved

=============================================================================================================================================================================================
Package Arch Version Repository Size
=============================================================================================================================================================================================
Removing:
mysql-community-client x86_64 5.7.25-1.el7 @mysql57-community 107 M
mysql-community-common x86_64 5.7.25-1.el7 @mysql57-community 2.6 M
mysql-community-libs x86_64 5.7.25-1.el7 @mysql57-community 9.5 M
mysql-community-libs-compat x86_64 5.7.25-1.el7 @mysql57-community 9.2 M
Removing for dependencies:
MySQL-python x86_64 1.2.5-1.el7 @base 284 k
cloudera-manager-agent x86_64 5.14.0-1.cm5140.p0.25.el7 @Cloudera-manager 76 M
net-snmp x86_64 1:5.7.2-49.el7_9.1 @centos7_optional_local 850 k
net-snmp-agent-libs x86_64 1:5.7.2-49.el7_9.1 @centos7_optional_local 2.1 M
perl-DBD-MySQL x86_64 4.023-6.el7 @centos7_online 323 k
postfix x86_64 2:2.10.1-9.el7 @32F960A7-7DB1-D008-64D9-307AB478D4B1 12 M
qt-mysql x86_64 1:4.8.7-9.el7_9 @B8A1CC78-DAEF-672D-98A2-2EB8FE14490E 74 k

Transaction Summary
=============================================================================================================================================================================================
Remove 4 Packages (+7 Dependent packages)

Installed size: 220 M
Is this ok [y/N]: n
Exiting on user command

[#2]

@sass Cloudera agent is still needed you can't remove that. If there is no way then after removing you have to install agent packages again. 

Regarding the DB upgrade you don't have to modify any file but in worst case you can check "db.properties" file to see if this has right values in place so that CM can work. 

[#3]

Thanks for answering it @GangWar 

Now that we shouldnt remove these packages which will affect cloudera agent

mysql-community-client x86_64 5.7.25-1.el7 @mysql57-community 107 M
mysql-community-common x86_64 5.7.25-1.el7 @mysql57-community 2.6 M
mysql-community-libs x86_64 5.7.25-1.el7 @mysql57-community 9.5 M
mysql-community-libs-compat x86_64 5.7.25-1.el7 @mysql57-community 9.2 M

To what version should I upgrade this Mysql and if I upgrade the Mysql will the agent take the newly installed package without any issues or need to edit some config file..

Our server team doesnt want us to keep the below Mysql version on the server as its old. 

mysql -V
mysql Ver 14.14 Distrib 5.7.21, for Linux (x86_64) using EditLine wrapper

and this is the package details from other server in the cluster 

which of these packages are used by the cloudera-agent now ??

mysql -V
mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1
rpm -qa|grep -i mysql
akonadi-mysql-1.9.2-4.el7.x86_64
perl-DBD-MySQL-4.023-6.el7.x86_64
MySQL-python-1.2.5-1.el7.x86_64
qt-mysql-4.8.7-9.el7_9.x86_64

[#4]

@sass You can check the supported versions of database below and then choose anyone to upgrade to. 

https://docs.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html#cdh...

The packages you listed are SQL packages not the DB so DB server upgrade should take care of the dependencies. 

CM server just need a DB running in healthy state with all configuration set rightly.