Hi - Anticipating the 3.0 release, I tried to upgrade an Ambari 2.8 test cluster (docker environment, Bigtop 3.2.0, Centos 7.9) to Ambari 3.0 (snapshot from trunk) and ran into some issues.
When running ambari-server upgrade, some stuff from /var/lib/ambari-server/ambari-env.sh gets reverted(?) to the older version. I can get past this by running the schema upgrade manually with the "--add-opens" stuff”: /usr/jdk64/jdk-17.0.2/bin/java --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util.regex=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang.reflect=ALL-UNNAMED -cp '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' org.apache.ambari.server.upgrade.SchemaUpgradeHelper > /var/log/ambari-server/ambari-server.out 2>&1 And then modifying ambari-env.sh to reflect latest updates. After this Ambari Server starts and runs fine. Start / Stop services (hdfs, yarn, zookeeper) surfaced issues with bigtop-select/distro-select. I replaced with the python3 version, and those specific errors went away, but starting some services just hangs and never completes. I’m not sure what the issue is. Will upgrading from 2.8 -> 3.0 be viable when 3.0 is released? Thanks!
