weizhouapache commented on issue #12374:
URL: https://github.com/apache/cloudstack/issues/12374#issuecomment-5644846832

   > [@weizhouapache](https://github.com/weizhouapache) I tested the current 
4.22 branch (4.22.2.0-SNAPSHOT) end to end on clean Debian 13.6 installs:
   > 
   > * management server with the stock MariaDB 11.8 and OpenJDK 21
   > * two KVM hosts with the stock libvirt 11.3, QEMU 10.0 and OpenJDK 21
   > * NFS primary and secondary storage, advanced zone, 4.22.0 systemvm 
template
   > 
   > The packages were built from the unmodified 4.22 branch on Debian 13 with 
JDK 21 (tests skipped).
   > 
   > **Works**
   > 
   > * cloudstack-setup-databases on MariaDB 11.8, cloudstack-setup-management, 
management server and usage server on Java 21
   > * cloudstack-agent installs with no extra steps, hosts added and Up
   > * SSVM and CPVM up, template registration, VM deploy, stop/start/reboot, 
console
   > * volume attach/detach, volume snapshot, volume and template from snapshot
   > * VM snapshot with memory, revert and delete
   > * isolated network with VR, public IP, firewall and port forwarding
   > * VPC with a tier, VPC without tiers
   > * live migration and host maintenance (guest VMs, VR and CPVM evacuated), 
agent and management server restart
   > 
   > **Needs fixing**
   > 
   > 1. MySQL connector. cloudstack-management depends on 
`python3-mysql.connector | mysql-connector-python-py3` and neither can be 
installed on Debian 13. The step from 
[cloudstack-documentation#610](https://github.com/apache/cloudstack-documentation/pull/610)
 does not help here anymore: the MySQL trixie repo has no Python connector, and 
the bookworm `mysql-connector-python-py3` 8.4.0 package depends on 
`python3-distutils`, which Debian 13 dropped. The only way I found was `pip 
install --break-system-packages mysql-connector-python==8.4.0` plus a dummy 
package to satisfy the dependency. The connector is only used by 
`python/lib/cloudutils/db.py`, `cloud-update-xenserver-licenses` and 
`scripts/util/migrate-dynamicroles.py`, and Debian 13 ships `python3-pymysql` 
and `python3-mysqldb`. Would moving these scripts to one of those be acceptable?
   > 2. Live migration fails out of the box with `unable to connect to server 
at <host>:16509: Connection refused`, because libvirtd does not listen. With 
the one line from [kvm: set LIBVIRTD_ARGS so libvirtd listens on Debian and 
Ubuntu hosts #14153](https://github.com/apache/cloudstack/pull/14153) it 
migrates in both directions and host maintenance works.
   > 3. Building the debs on Debian 13:
   >    
   >    * `dpkg-checkbuilddeps` fails on the JDK line (Debian 13 only has 
openjdk-21, and openjdk-21-jdk does not provide java17-sdk) and on the MySQL 
connector.
   >    * The UI build fails on the Debian 13 Node 20 with 
`ERR_OSSL_EVP_UNSUPPORTED` (webpack 4). It works with 
`NODE_OPTIONS=--openssl-legacy-provider`.
   >    * The Marvin sdist is now named `marvin-<version>.tar.gz`, so 
`debian/rules` stops at `cp Marvin-*.tar.gz`. [Packaging: accept normalized 
Marvin archive names #13793](https://github.com/apache/cloudstack/pull/13793) 
fixes this; I left the test results there.
   > 4. Marvin on 4.22 cannot be installed on Python 3.13 because PyCrypt does 
not build. [marvin: use pycryptodome instead of PyCrypt 
#13594](https://github.com/apache/cloudstack/pull/13594) changed it to 
pycryptodome on main only. Could it be backported to 4.22?
   > 
   > I can help with PRs for 1 and 4 and with the compatibility matrix docs 
once there is agreement on the approach.
   
   
   @nagaboinaramgopal 
   debian 13 is actually working well with cloudstack 4.23.0
   please refer to 
https://github.com/apache/cloudstack/discussions/13980#discussioncomment-18233127
   (marvin node is oraclelinux 9, not debian 13)
   
   for the mysql python connector, please refer to 
https://github.com/apache/cloudstack-documentation/pull/678
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to