-1. I have a blocker issue that should be fixed before Ambari 2.2.2 is released.
Without my patch (https://issues.apache.org/jira/browse/AMBARI-16072), issue may be encountered when adding services to a Kerberized cluster. Typically this will be after an upgrade to 2.2.2 and if AMS is set to distributed mode, however issues may occur in other scenarios since the stack advisor is not feed a complete set of data. My patch fixes this. Thanks, Rob On 4/21/16, 11:28 PM, "Srimanth Gunturi" <[email protected]> wrote: >Hello, > >I have created an ambari-2.2.2 release candidate. > >GIT source tag (release-2.2.2-rc0) >https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.2.2-rc0 > >Staging site: http://people.apache.org/~srimanth/apache-ambari-2.2.2-rc0/ > >PGP release keys (signed using 0EF56BD9) >http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x2F261D94 > >One can look into the issues fixed in this release at >https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334712/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel > >Vote will be open for 72 hours. >[ ] +1 approve >[ ] +0 no opinion >[ ] -1 disapprove (and reason why) > > >Best regards, >Srimanth? >
