Frequently Asked Questions (FAQ)
This page answers common questions about Apache Ambari 3.1. For documented behavior, follow the linked platform, monitoring, frontend, upgrade, and development guides rather than older 3.0 setup examples.
What runtime does 3.1 require?
Ambari helpers build and run with JDK 17 and Maven 3.9.x. Linux packages target CPython 3.9 (cp39) on the selected platform ABI; the packaged private libraries must not be replaced with a runtime pip install. See Python Runtime and Java Dependencies.
Which Python is used to build Ambari?
The source-level interpreter requirement and the native-extension ABI in a packaged RPM are separate contracts. Verify the executable selected by the build and use the matching cp39 wheel target. On Rocky Linux 8, do not assume generic python3 is Python 3.9.
Which UI is supported?
Ambari 3.1 uses ambari-web/latest as the primary React UI. The /latest/# entry point, authentication, permissions, Hosts, Services, Configs, Alerts, Kerberos, HA, upgrades, Views, Themes, and monitoring workflows are covered by the React User Guide. Classic Ember is a migration comparison, not the 3.1 operating path.
Why can I see a page but not change it?
Read access and mutation access are separate. Cluster, host, service, datasource, dashboard, and administration operations use distinct permission checks. A direct URL does not grant a missing permission; test the actual role and API authorization response.
What changed in monitoring?
The native monitoring area uses Prometheus-compatible discovery, VMAGENT, VictoriaMetrics, datasources, PromQL, targets, and dashboards. The monitoring migration guide explains that new metadata tables do not import AMS history or convert old widget layouts. Plan archives and custom query rewrites separately.
How do I qualify a 3.1 candidate?
Use the upgrade guide to separate Ambari package/UI/database changes, Stack service changes, and monitoring cutover. Verify artifact provenance, Java/Python ABI, database backup, browser/authentication paths, and the real topology before maintenance.
How should I troubleshoot a failed operation?
Inspect the persisted background request, task logs, component state, and owner before retrying. Refresh and server restart recovery restore checkpoints where available; they do not justify resubmitting completed work. For monitoring, distinguish discovery, scrape, remote-write, storage, datasource, and dashboard failures.
Where are test reports?
Java reports are under ambari-server/target/surefire-reports/ and ambari-server/target/failsafe-reports/; Python results and coverage are under ambari-server/target/python-test-results/ and ambari-server/target/python-coverage/. Website yarn test:i18n and browser checks are separate from Ambari product acceptance. See Unit Test Reports.