jialiang
jialiang
@brahmareddybattula git checks failed because ambari metrics error， please check the compilation problem of ambari metrics. 
@brahmareddybattula so will all PR be stuck due to metrics compilation failure?
> [#3286 (comment)](https://github.com/apache/ambari/pull/3286#issuecomment-1223890660) > > I think [AMBARI-24695](https://issues.apache.org/jira/browse/AMBARI-24695), [AMBARI-24693](https://issues.apache.org/jira/browse/AMBARI-24693), [AMBARI-24707](https://issues.apache.org/jira/browse/AMBARI-24707) should be adopted to branch-2.7 in order to build it. Thanks for your answer, best regards @eubnara
@sekikn @iwasakims Could you help review this PR?
@brahmareddybattula All PRs needed for the Ambari 2.8 release have been cherry-picked into this PR, please help review.
@brahmareddybattula It seems there was an issue with the CI environment. The tests passed locally and also passed upon re-triggering the CI.
@brahmareddybattula The "Trigger CI" empty commit, which was made to trigger CI, has been deleted.
@brahmareddybattula It seems like the CI/CD environment is having issues again, If it gets resolved, could you help manually trigger the CI for this PR? Otherwise, I'll have to submit...
@arshadmohammad It seems like there's an issue with the Python environment in the CI/CD. Could you help check the CI/CD environment?
@brahmareddybattula Yes, I will rebase all my PRs on the latest trunk branch.