Re: Review Request 35866: Kerberos configs aren't restored when moving back from Review to the Configure Identities step
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35866/#review93822 --- Ship it! Ship It! - Jaimin Jetly On July 31, 2015, 11:54 p.m., Richard Zang wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35866/ --- (Updated July 31, 2015, 11:54 p.m.) Review request for Ambari, Jaimin Jetly and Yusaku Sako. Bugs: AMBARI-12141 https://issues.apache.org/jira/browse/AMBARI-12141 Repository: ambari Description --- Kerberos configs aren't restored when moving back from Review to the Configure Identities step Diffs - ambari-web/app/controllers/main/admin/kerberos/step2_controller.js 1ffab0d ambari-web/app/controllers/main/admin/kerberos/step4_controller.js 08f4e10 ambari-web/app/routes/add_kerberos_routes.js e3a40f8 ambari-web/app/routes/add_service_routes.js 262049e ambari-web/app/utils/config.js 11df7ee ambari-web/test/controllers/main/admin/kerberos/step4_controller_test.js af0650c Diff: https://reviews.apache.org/r/35866/diff/ Testing --- Unit test passed. 6419 tests complete (9 seconds) 86 tests pending Thanks, Richard Zang
[jira] [Updated] (AMBARI-12141) Kerberos configs aren't restored when moving back from Review to the Configure Identities step
[ https://issues.apache.org/jira/browse/AMBARI-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-12141: -- Attachment: AMBARI-12141_v3.patch Kerberos configs aren't restored when moving back from Review to the Configure Identities step -- Key: AMBARI-12141 URL: https://issues.apache.org/jira/browse/AMBARI-12141 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.2.0, 2.1.1 Attachments: AMBARI-12141.patch, AMBARI-12141_v2.patch, AMBARI-12141_v3.patch * Enable Kerberos on the cluster * Open Add Service Wizard * Proceed to the step Configure Identities * Input Admin principal, Admin password * Click Next * Click Back * Fields Admin principal, Admin password are empty, but should be filed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12572) Config versions shows not all versions after save
[
https://issues.apache.org/jira/browse/AMBARI-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650061#comment-14650061
]
Hadoop QA commented on AMBARI-12572:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748271/AMBARI-12572-2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3508//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3508//console
This message is automatically generated.
Config versions shows not all versions after save
-
Key: AMBARI-12572
URL: https://issues.apache.org/jira/browse/AMBARI-12572
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.1
Reporter: Xi Wang
Assignee: Xi Wang
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12572-2.patch, AMBARI-12572.patch,
AMBARI-12572.patch, Screen Shot 2015-07-24 at 2.04.29 PM.png
1. Go to service conf tab.
2. Add or change some properties.
3. Save config version.
4. Only current and previous version are shown. see attached.
All versions appear after refreshing the page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Review Request 37008: On Install wizard UI - Some advanced HDFS properties show with wrong label when navigate from step 8 back to step 7
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37008/ --- Review request for Ambari and Jaimin Jetly. Bugs: AMBARI-12443 https://issues.apache.org/jira/browse/AMBARI-12443 Repository: ambari Description --- On Install wizard UI - Some advanced HDFS properties show with wrong label when navigate from step 8 Review back to step 7 Customize Services For example, the dfs.datanode.http.address is displayed as DataNode See screenshot attached for details. The dfs.datanode.http.address is show with the correct label when navigate from step 6 Assign Slaves and Clients to step 7 Customize Services Diffs - ambari-web/app/utils/helper.js 3ac6991 ambari-web/test/utils/helper_test.js b273120 Diff: https://reviews.apache.org/r/37008/diff/ Testing --- unit test manually patch the UI with changes and run thru the cluster deploy wizard, go back and forth between stp 8 and step 7 Thanks, Di Li
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Description: There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650088#comment-14650088 ] Hudson commented on AMBARI-12613: - SUCCESS: Integrated in Ambari-branch-2.1 #305 (See [https://builds.apache.org/job/Ambari-branch-2.1/305/]) AMBARI-12613. Allow for granular authorization inorder to update User resource properties via Ambari's REST API (rlevas) (rlevas: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=abce3cd5ac6a6a1caa7311fd8b93c5878889ed26) * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1, 2.1.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Attachments: AMBARI-12613_branch-2.0.maint_01.patch, AMBARI-12613_branch-2.1_01.patch, AMBARI-12613_trunk_01.patch Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 37003: Add Data Visualization to Hive View
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37003/ --- Review request for Ambari and Yusaku Sako. Bugs: AMBARI-12615 https://issues.apache.org/jira/browse/AMBARI-12615 Repository: ambari Description --- Refer to the description in AMBARI-12615 Diffs - ambari-web/app/views/main/views/details.js e90cb20 contrib/views/hive/pom.xml 39f6848 contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/browser/HiveBrowserService.java a0d44f5 contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/JobService.java 526f13f contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/ResultsPaginationController.java 18152ad contrib/views/hive/src/main/resources/ui/hive-web/.jshintrc c1fe863 contrib/views/hive/src/main/resources/ui/hive-web/app/components/visualization-tabs-widget.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/query-tabs.js 4f5176c contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/visualization-ui.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/initializers/i18n.js af5e3a7 contrib/views/hive/src/main/resources/ui/hive-web/app/templates/components/visualization-tabs-widget.hbs PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/templates/visualization-ui.hbs PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/utils/constants.js e4e445a contrib/views/hive/src/main/resources/ui/hive-web/app/views/visualization-ui.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/bower.json 37ea901 Diff: https://reviews.apache.org/r/37003/diff/ Testing --- Tested manually with different datasets of different size. Tested switching to visualization tab with multiple SQL tabs having different queries. Tested switching between the two visualization tabs multiple times. Tested with upto 3 rows in the resultset with all possible combinations of scale and chart types. Tested with Google Chrome, Safari, Firefox and Internet Explorer 10. Tested end to end with Ambari Web and Hive View. Existing Ambari Web unit tests pass. 6482 tests complete (22 seconds) 94 tests pending [INFO] [INFO] --- apache-rat-plugin:0.11:check (default) @ ambari-web --- [INFO] 51 implicit excludes (use -debug for more details). [INFO] Exclude: .idea/** [INFO] Exclude: package.json [INFO] Exclude: public/** [INFO] Exclude: public-static/** [INFO] Exclude: app/assets/** [INFO] Exclude: vendor/** [INFO] Exclude: node_modules/** [INFO] Exclude: node/** [INFO] Exclude: npm-debug.log [INFO] 1169 resources included (use -debug for more details) Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. Compiler warnings: WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.' Warning: org.apache.xerces.parsers.SAXParser: Feature 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 1169 licence. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 49.809s [INFO] Finished at: Fri Jul 31 18:39:11 PDT 2015 [INFO] Final Memory: 12M/439M [INFO] Thanks, Vivek Ratnavel Subramanian
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: External issue URL: https://reviews.apache.org/r/37003/ Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Attachment: AMBARI-12615.patch Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 Attachments: AMBARI-12615.patch There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-12141) Kerberos configs aren't restored when moving back from Review to the Configure Identities step
[ https://issues.apache.org/jira/browse/AMBARI-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-12141. --- Resolution: Fixed committed to trunk and 2.1 Kerberos configs aren't restored when moving back from Review to the Configure Identities step -- Key: AMBARI-12141 URL: https://issues.apache.org/jira/browse/AMBARI-12141 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.2.0, 2.1.1 Attachments: AMBARI-12141.patch, AMBARI-12141_v2.patch, AMBARI-12141_v3.patch * Enable Kerberos on the cluster * Open Add Service Wizard * Proceed to the step Configure Identities * Input Admin principal, Admin password * Click Next * Click Back * Fields Admin principal, Admin password are empty, but should be filed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12574) Add distributionManagement tag to ambari-metrics.
[ https://issues.apache.org/jira/browse/AMBARI-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650089#comment-14650089 ] Hudson commented on AMBARI-12574: - SUCCESS: Integrated in Ambari-branch-2.1 #305 (See [https://builds.apache.org/job/Ambari-branch-2.1/305/]) AMBARI-12574. Add distributionManagement tag to ambari-metrics. (Ashish Singh via swagle) (swagle: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=408d768c9d36abf401801282d530283071730add) * ambari-metrics/pom.xml Add distributionManagement tag to ambari-metrics. - Key: AMBARI-12574 URL: https://issues.apache.org/jira/browse/AMBARI-12574 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.1.0 Environment: Deploy the ambari metrics artifacts to Nexus. Reporter: Ashish Singh Assignee: Ashish Singh Priority: Critical Fix For: 2.1.0, 2.1.1, 2.1.2, trunk Attachments: 0001-AMBARI-12574-Add-distributionManagement-tag-to-ambar.patch Add distributionManagement to ambari metrics. This is needed for Open Data Platform initiative. Currently, without this tag deploy build will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Apache Ambari Release 2.0.2 RC1
Hi, I have created an Apache Ambari 2.0.2 Release Candidate (RC1). This is a maintenance release for branch-2.0.maint GIT source tag: *https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1* Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc1/ PGP release key used (signed using 392F57AC): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS One can look into the issues fixed in this release at https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747 Total 2.0.2 JIRAs: 12 Total JIRAs Resolved as Fixed: 12 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 Here's how to verify the tarball hashes: git clone --branch release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src cd apache-ambari-2.0.2-src git clean -xdf cd ambari-web npm install ulimit -n 2048 brunch build rm -rf node_modules mv public public-static cd ../.. tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src # Verify my signature, gpg --verify apache-ambari-2.0.2-src.tar.gz.asc apache-ambari-2.0.2-src.tar.gz gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC gpg: Good signature from Alejandro Fernandez (Apache Ambari Release Management) alejan...@apache.org openssl md5 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided openssl sha1 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.sha1 # and compare to the file I provided # I made sure ratcheck passes cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck cd apache-ambari-2.0.2-ratcheck mvn clean apache-rat:check Thanks, Alejandro Fernandez Apache Ambari PMC
[jira] [Commented] (AMBARI-12602) [PluggableStackDefinition] Create tool for generating pluggable stack definition
[ https://issues.apache.org/jira/browse/AMBARI-12602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649285#comment-14649285 ] Hudson commented on AMBARI-12602: - SUCCESS: Integrated in Ambari-trunk-Commit #3202 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3202/]) AMBARI-12602. [PluggableStackDefinition] Create tool for generating pluggable stack definition (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=dde648d7c42eb3bf0fd47f418c916cd9ee341e91) * ambari-common/src/main/python/white_labeling/WhiteLabelStackDefinition.py * ambari-common/src/main/python/white_labeling/__init__.py * ambari-common/src/main/python/pluggable_stack_definition/__init__.py * ambari-common/src/main/python/pluggable_stack_definition/test.json * ambari-common/src/main/python/white_labeling/test.json * ambari-common/src/main/python/pluggable_stack_definition/GenerateStackDefinition.py [PluggableStackDefinition] Create tool for generating pluggable stack definition Key: AMBARI-12602 URL: https://issues.apache.org/jira/browse/AMBARI-12602 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 Create tool for generating stack definition from existing one with chnaged set of services, service versions, package list etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12605) SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration
[ https://issues.apache.org/jira/browse/AMBARI-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649286#comment-14649286 ] Hudson commented on AMBARI-12605: - SUCCESS: Integrated in Ambari-trunk-Commit #3202 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3202/]) AMBARI-12605. SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=3a4d890351e63031faafa235d647edbb8076bfff) * ambari-agent/src/main/python/ambari_agent/main.py SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration -- Key: AMBARI-12605 URL: https://issues.apache.org/jira/browse/AMBARI-12605 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 Ambari agent shows warning on every ambari-server restart [root@c6406 ~]# ambari-agent restart Restarting ambari-agent Verifying Python version compatibility... Using python /usr/bin/python2.6 Found ambari-agent PID: 2978 Stopping ambari-agent /usr/lib/python2.6/site-packages/ambari_agent/main.py:314: SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration global is_logger_setup It's related to -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12603) serviceAccounts page doesn't show user properties
[ https://issues.apache.org/jira/browse/AMBARI-12603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649177#comment-14649177 ] Hudson commented on AMBARI-12603: - ABORTED: Integrated in Ambari-trunk-Commit #3201 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3201/]) AMBARI-12603 serviceAccounts page doesn't show user properties. (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=eee2a7a8807982b71163a54f097f815fa9cb2eb9) * ambari-web/app/views/main/admin/serviceAccounts_view.js * ambari-web/app/controllers/global/cluster_controller.js * ambari-web/app/controllers/main/admin/serviceAccounts_controller.js serviceAccounts page doesn't show user properties - Key: AMBARI-12603 URL: https://issues.apache.org/jira/browse/AMBARI-12603 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.1.1 Attachments: AMBARI-12603.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12601) Specifying heterogeneous storage does not work for DataNode Directories
[
https://issues.apache.org/jira/browse/AMBARI-12601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649176#comment-14649176
]
Hudson commented on AMBARI-12601:
-
ABORTED: Integrated in Ambari-trunk-Commit #3201 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3201/])
AMBARI-12601 Specifying heterogeneous storage does not work for DataNode
Directories. (ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=bcf15099dd36acd4c0be8e19b27b436044357b9b)
* ambari-web/app/utils/config.js
* ambari-web/app/models/configs/objects/service_config_property.js
* ambari-web/test/utils/config_test.js
* ambari-web/app/data/HDP2.2/site_properties.js
Specifying heterogeneous storage does not work for DataNode Directories
---
Key: AMBARI-12601
URL: https://issues.apache.org/jira/browse/AMBARI-12601
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Blocker
Fix For: 2.1.1
Attachments: AMBARI-12601.patch, AMBARI-12601_branch_2.1.1.patch
Heterogenous storage specification for dfs.data.dir introduced in Ambari
1.7.0 is no longer working.
STR:
Go to HDFS Configs
Prepend the content of DataNode directories with [SSD] so that it looks
like:
{noformat}
[SSD]/grid/0/hadoop/hdfs/data
{noformat}
An error is shown (must be a slash or drive)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12601) Specifying heterogeneous storage does not work for DataNode Directories
[
https://issues.apache.org/jira/browse/AMBARI-12601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649173#comment-14649173
]
Hudson commented on AMBARI-12601:
-
ABORTED: Integrated in Ambari-branch-2.1 #299 (See
[https://builds.apache.org/job/Ambari-branch-2.1/299/])
AMBARI-12601 Specifying heterogeneous storage does not work for DataNode
Directories. (ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=580277d615508ff8f41335631081f4380815f5d4)
* ambari-web/test/utils/config_test.js
* ambari-web/app/utils/config.js
* ambari-web/app/data/HDP2.2/site_properties.js
* ambari-web/app/models/configs/objects/service_config_property.js
Specifying heterogeneous storage does not work for DataNode Directories
---
Key: AMBARI-12601
URL: https://issues.apache.org/jira/browse/AMBARI-12601
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Blocker
Fix For: 2.1.1
Attachments: AMBARI-12601.patch, AMBARI-12601_branch_2.1.1.patch
Heterogenous storage specification for dfs.data.dir introduced in Ambari
1.7.0 is no longer working.
STR:
Go to HDFS Configs
Prepend the content of DataNode directories with [SSD] so that it looks
like:
{noformat}
[SSD]/grid/0/hadoop/hdfs/data
{noformat}
An error is shown (must be a slash or drive)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12606) Add ZooKeeper Server action is disabled after filtering on hosts page
[ https://issues.apache.org/jira/browse/AMBARI-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649284#comment-14649284 ] Hudson commented on AMBARI-12606: - SUCCESS: Integrated in Ambari-trunk-Commit #3202 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3202/]) AMBARI-12606 Add ZooKeeper Server action is disabled after filtering on hosts page. (atkach) (atkach: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=8ef13054985b69b8d5e44b2e419723b7dc658b33) * ambari-web/app/controllers/main/service/item.js Add ZooKeeper Server action is disabled after filtering on hosts page - Key: AMBARI-12606 URL: https://issues.apache.org/jira/browse/AMBARI-12606 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.1 Attachments: AMBARI-12606.patch STR: 1. Install cluster with at least 2 hosts and install only 1 ZooKeeper Server. 2. Go to Hosts page and apply some filter to get No hosts to display as a result. 3. Without clearing filters go to ZooKeeper service page. Add ZooKeeper Server will be disabled, but we still have available hosts to install ZooKeeper Server on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12607) Repo build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-12607: --- Attachment: AMBARI-12607.patch Repo build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Attachments: AMBARI-12607.patch Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 36986: Repo build script not handling HDP-2.3 or HDP-2.4 stacks
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36986/ --- Review request for Ambari and Jonathan Hurley. Repository: ambari Description --- Repo build script not handling HDP-2.3 or HDP-2.4 stacks. Modify the existing script to handle 2.3 and 2.4 stacks. Diffs - ambari-server/set-hdp-repo-url.sh fed7a94 Diff: https://reviews.apache.org/r/36986/diff/ Testing --- No tests required; it's a build issue. Thanks, Nate Cole
Re: Review Request 36986: Repo build script not handling HDP-2.3 or HDP-2.4 stacks
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36986/ --- (Updated July 31, 2015, 8:17 a.m.) Review request for Ambari and Jonathan Hurley. Bugs: AMBARI-12607 https://issues.apache.org/jira/browse/AMBARI-12607 Repository: ambari Description --- Repo build script not handling HDP-2.3 or HDP-2.4 stacks. Modify the existing script to handle 2.3 and 2.4 stacks. Diffs - ambari-server/set-hdp-repo-url.sh fed7a94 Diff: https://reviews.apache.org/r/36986/diff/ Testing --- No tests required; it's a build issue. Thanks, Nate Cole
[jira] [Updated] (AMBARI-12607) Repo build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-12607: --- Summary: Repo build script not handling HDP-2.3 or HDP-2.4 stacks (was: Build script not handling HDP-2.3 or HDP-2.4 stacks) Repo build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12607) Build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649143#comment-14649143 ] Nate Cole commented on AMBARI-12607: No tests. This is a build concern. Build script not handling HDP-2.3 or HDP-2.4 stacks --- Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36917: Host check/clean-up logic should clean up new packages and folder names
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36917/#review93720 --- Ship it! Ship It! - Nate Cole On July 30, 2015, 9:32 a.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36917/ --- (Updated July 30, 2015, 9:32 a.m.) Review request for Ambari, Andrew Onischuk and Nate Cole. Bugs: AMBARI-12581 https://issues.apache.org/jira/browse/AMBARI-12581 Repository: ambari Description --- Few HDP-2.3 installation ran into problem when install performed on VMs that are not clean. One of the reported problem is: Traceback (most recent call last): File /var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py, line 38, in module AfterInstallHook().execute() File /usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py, line 218, in execute method(env) File /var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py, line 35, in hook link_configs(self.stroutfile) File /var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py, line 91, in link_configs _link_configs(k, json_version, v) File /var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py, line 156, in _link_configs conf_select.select(HDP, package, version) File /usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py, line 241, in select shell.checked_call(get_cmd(set-conf-dir, package, version), logoutput=False, quiet=False, sudo=True) File /usr/lib/python2.6/site-packages/resource_management/core/shell.py, line 70, in inner result = function(command, **kwargs) File /usr/lib/python2.6/site-packages/resource_management/core/shell.py, line 92, in checked_call tries=tries, try_sleep=try_sleep) File /usr/lib/python2.6/site-packages/resource_management/core/shell.py, line 140, in _call_wrapper result = _call(command, **kwargs_copy) File /usr/lib/python2.6/site-packages/resource_management/core/shell.py, line 291, in _call raise Fail(err_msg) resource_management.core.exceptions.Fail: Execution of 'conf-select set-conf-dir --package ranger-kms --stack-version 2.3.0.0-2557 --conf-version 0' returned 1. ranger-kms not installed or incorrect package name AMBARI-12515 is looking into making conf-select call more robust but host-clean up script (along with host checkup) need to be modified to handle the new folders introduced under /etc as well as /usr/hdp/current or /usr/hdp/version. Suggestion from Nate Cole regarding cleaning up conf dirs. cd /etc remove accumulo ambari-* atlas hadoop-* hive* hive-* mahout phoenix ranger spark zookeeper falcon hadoop hbase kafka knox oozie ranger-* (ranger-admin, ranger-kms, ranger-usersync) slider sqoop storm pig flume hive-hcatalog The host check script should be modified to include these folders in the report so that the cleanup script can clean it. Diffs - ambari-agent/src/main/python/ambari_agent/HostCheckReportFileHandler.py a4b898d ambari-agent/src/main/python/ambari_agent/HostInfo.py 385c758 ambari-server/src/main/resources/custom_actions/scripts/check_host.py 40bea98 Diff: https://reviews.apache.org/r/36917/diff/ Testing --- [INFO] [INFO] Reactor Summary: [INFO] [INFO] Ambari Views .. SUCCESS [4.140s] [INFO] Ambari Metrics Common . SUCCESS [1.754s] [INFO] Ambari Server . SUCCESS [1:10.901s] [INFO] Ambari Agent .. SUCCESS [16.487s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1:34.779s [INFO] Finished at: Wed Jul 29 20:05:08 EEST 2015 [INFO] Final Memory: 87M/1452M Thanks, Dmitro Lisnichenko
[jira] [Created] (AMBARI-12608) Spectrum Scale service should be able to save core-site changes
Nathan Falk created AMBARI-12608:
Summary: Spectrum Scale service should be able to save core-site
changes
Key: AMBARI-12608
URL: https://issues.apache.org/jira/browse/AMBARI-12608
Project: Ambari
Issue Type: Improvement
Components: ambari-web
Affects Versions: 2.1.0
Reporter: Nathan Falk
Priority: Minor
Fix For: 2.1.0
With the upcoming release of IBM Open Platform 4.1, which is based on Ambari
2.1, it will be possible to add a stack to use Spectrum Scale in place of HDFS
as the underlying filesystem for hadoop.
A new service named 'GPFS' is introduced in this stack, and in the absence of
HDFS, the core-site.xml, hadoop-env.xml and hdfs-site.xml files will be
provided in services/GPFS/configuration.
There is code in ambari-web which restricts the services which are permitted to
save core-site changes. In the file
ambari-web/app/mixins/common/configs/configs_saver.js, there is a function
allowSaveSite (line numbers may differ in the current version of the file -
this is from 2 or 3 weeks ago):
{code}
483 /**
484* for some file names we have a restriction
485* and can't save them, in this this method will return false
486* @param fName
487* @returns {boolean}
488*/
489 allowSaveSite: function(fName) {
490 switch (fName) {
491 case 'mapred-queue-acls.xml':
492 return false;
493 case 'core-site.xml':
494 return ['HDFS', 'GLUSTERFS',
'RANGER_KMS'].contains(this.get('content.serviceName'));
495 default :
496 return true;
497 }
498 },
{code}
In order for the 'GPFS' service to save changes to core-site.xml, 'GPFS' needs
to be added to the list on line 494, or some other mechanism would have to be
provided to allow 3rd-party stacks to redefine which service owns core-site.xml.
We are currently working around this problem by modifying
/usr/lib/ambari-server/web/javascripts/app.js.gz directly, but this type of
approach is inherently error-prone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-12538) Attempting to access the Ambari Dashboard results in an HTTP 500 Error after changing cluster name and restarting the Ambari server
[
https://issues.apache.org/jira/browse/AMBARI-12538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar resolved AMBARI-12538.
Resolution: Fixed
Resolved via:
{{b04fb76 Thu May 28 17:53:02 EEST 2015 Jonathan Hurley
jhur...@hortonworks.com AMBARI-11487 - Changed Configurations During Upgrade
Are Reverted During Finalize (jonathanhurley)}}
Anyway, cluster name was updated successfully at DB
Attempting to access the Ambari Dashboard results in an HTTP 500 Error after
changing cluster name and restarting the Ambari server
---
Key: AMBARI-12538
URL: https://issues.apache.org/jira/browse/AMBARI-12538
Project: Ambari
Issue Type: Bug
Affects Versions: 2.1.0
Environment: SLES11 SP3
Reporter: Zack Marsh
Priority: Critical
Fix For: 2.1.1
Steps to reproduce:
* Login to Ambari Web UI
* Rename cluster (Admin - Manage Ambari - Rename Cluister - Enter new
name )
* Restart Ambari Server via CLI (ambari-server restart)
* Login to Ambari Web UI again
* When attempting to access the Ambari Dashboard an HTTP 500 Error will occur:
{code}
Error
500 status code received on GET method for API:
/api/v1/clusters/CLUSTERNAME/requests?to=endpage_size=10fields=Requests
Error message: Server Error
{code}
Excerpt from the Ambari Server log:
{code}
24 Jul 2015 16:40:41,013 ERROR [qtp-client-25] ReadHandler:91 - Caught a
runtime exception executing a query
java.lang.RuntimeException: Failed to construct logical request during
replay: org.apache.ambari.server.ClusterNotFoundException: Cluster not found,
clusterName=PIRIPIRI
at
org.apache.ambari.server.topology.PersistedStateImpl.getAllRequests(PersistedStateImpl.java:167)
at
org.apache.ambari.server.topology.TopologyManager.ensureInitialized(TopologyManager.java:91)
at
org.apache.ambari.server.topology.TopologyManager.getRequests(TopologyManager.java:198)
at
org.apache.ambari.server.actionmanager.ActionManager.getRequestsByStatus(ActionManager.java:232)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider.getRequestResources(RequestResourceProvider.java:414)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider.getResources(RequestResourceProvider.java:200)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
at
org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:482)
at
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:381)
at
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
at
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:105)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
at
org.apache.ambari.server.api.services.RequestService.getRequests(RequestService.java:95)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
[jira] [Created] (AMBARI-12607) Build script not handling HDP-2.3 or HDP-2.4 stacks
Nate Cole created AMBARI-12607: -- Summary: Build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36943: [Preview] RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/#review93719 --- ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py (lines 48 - 50) https://reviews.apache.org/r/36943/#comment148123 If this is true, then the upgrade pack for 2.2.x - 2.2.y needs to be updated. If not, then this version check should be for 2.3. ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml (line 140) https://reviews.apache.org/r/36943/#comment148124 +1 for this comment. Also, python says 2.2 and higher, so would need HDP-2.2 - 2.2 upgrade pack change. - Nate Cole On July 30, 2015, 11:33 a.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/ --- (Updated July 30, 2015, 11:33 a.m.) Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, and Nate Cole. Bugs: AMBARI-12594 https://issues.apache.org/jira/browse/AMBARI-12594 Repository: ambari Description --- RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py d599b8c ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 3dda481 ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py 37dcb20 Diff: https://reviews.apache.org/r/36943/diff/ Testing --- OK -- Total run:808 Total errors:0 Total failures:0 OK Performing tests on live cluster Thanks, Dmitro Lisnichenko
[jira] [Updated] (AMBARI-12593) Enable Kerberos: Config values should be trimmed
[ https://issues.apache.org/jira/browse/AMBARI-12593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-12593: - Attachment: AMBARI-12593_v2.patch Enable Kerberos: Config values should be trimmed Key: AMBARI-12593 URL: https://issues.apache.org/jira/browse/AMBARI-12593 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.2.0 Attachments: AMBARI-12593.patch, AMBARI-12593_v2.patch Configurations on Configure Kerberos step in Kerberos wizard should be trimmed. For example if hostname will contain spaces, it's not so obvious and will fail wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36988: AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36988/#review93730 --- Ship it! Ship It! - Sid Wagle On July 31, 2015, 3:12 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36988/ --- (Updated July 31, 2015, 3:12 p.m.) Review request for Ambari and Sid Wagle. Repository: ambari Description --- AMS shows a validation error that hbase_regionserver_heapsize should not be below 12GB. Though this is correct, it does not apply when HBase is used in embedded mode - so this validation error should not show up. Diffs - ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 3e34b09 ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py c03e62b Diff: https://reviews.apache.org/r/36988/diff/ Testing --- -- Ran 241 tests in 8.811s OK -- Total run:784 Total errors:0 Total failures:0 OK Thanks, Dmytro Sen
[jira] [Commented] (AMBARI-12607) Repo build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649400#comment-14649400 ] Hudson commented on AMBARI-12607: - SUCCESS: Integrated in Ambari-branch-2.1 #301 (See [https://builds.apache.org/job/Ambari-branch-2.1/301/]) AMBARI-12607. Repo build script not handling HDP-2.3 or HDP-2.4 stacks (ncole) (ncole: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f58a7a91d935ac77ddbb26478be5f97b81660f21) * ambari-server/set-hdp-repo-url.sh Repo build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Attachments: AMBARI-12607.patch Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12609) Host Checks: Rerun checks doesn't work properly
[ https://issues.apache.org/jira/browse/AMBARI-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-12609: - Attachment: AMBARI-12609.patch Host Checks: Rerun checks doesn't work properly - Key: AMBARI-12609 URL: https://issues.apache.org/jira/browse/AMBARI-12609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.2.0 Attachments: AMBARI-12609.patch Since we have started use custom commands for checking hosts after registering Rerun checks doesn't work properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 36991: Ambari upgrade to 2.1 fails (thinks hbase is installed)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36991/ --- Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi. Bugs: AMBARI-12611 https://issues.apache.org/jira/browse/AMBARI-12611 Repository: ambari Description --- Ambari upgrade to 2.1 fails (thinks hbase is installed) Diffs - ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java 3312145 Diff: https://reviews.apache.org/r/36991/diff/ Testing --- unit tests passed Thanks, Dmytro Sen
[jira] [Updated] (AMBARI-12610) AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-12610: Attachment: AMBARI-12610.patch AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode -- Key: AMBARI-12610 URL: https://issues.apache.org/jira/browse/AMBARI-12610 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12610.patch AMS shows a validation error that hbase_regionserver_heapsize should not be below 12GB. Though this is correct, it does not apply when HBase is used in embedded mode - so this validation error should not show up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12611) Ambari upgrade to 2.1 fails (thinks hbase is installed)
Dmytro Sen created AMBARI-12611: --- Summary: Ambari upgrade to 2.1 fails (thinks hbase is installed) Key: AMBARI-12611 URL: https://issues.apache.org/jira/browse/AMBARI-12611 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Ambari upgrade to 2.1 fails (thinks hbase is installed) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12593) Enable Kerberos: Config values should be trimmed
[ https://issues.apache.org/jira/browse/AMBARI-12593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649355#comment-14649355 ] Aleksandr Kovalenko commented on AMBARI-12593: -- +1 for patch Enable Kerberos: Config values should be trimmed Key: AMBARI-12593 URL: https://issues.apache.org/jira/browse/AMBARI-12593 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.2.0 Attachments: AMBARI-12593.patch, AMBARI-12593_v2.patch Configurations on Configure Kerberos step in Kerberos wizard should be trimmed. For example if hostname will contain spaces, it's not so obvious and will fail wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12610) AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode
Dmytro Sen created AMBARI-12610: --- Summary: AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode Key: AMBARI-12610 URL: https://issues.apache.org/jira/browse/AMBARI-12610 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 AMS shows a validation error that hbase_regionserver_heapsize should not be below 12GB. Though this is correct, it does not apply when HBase is used in embedded mode - so this validation error should not show up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12609) Host Checks: Rerun checks doesn't work properly
Antonenko Alexander created AMBARI-12609: Summary: Host Checks: Rerun checks doesn't work properly Key: AMBARI-12609 URL: https://issues.apache.org/jira/browse/AMBARI-12609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.2.0 Since we have started use custom commands for checking hosts after registering Rerun checks doesn't work properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36991: Ambari upgrade to 2.1 fails (thinks hbase is installed)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36991/#review93732 --- Ship it! Ship It! - Alexandr Antonenko On July 31, 2015, 4:14 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36991/ --- (Updated July 31, 2015, 4:14 p.m.) Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi. Bugs: AMBARI-12611 https://issues.apache.org/jira/browse/AMBARI-12611 Repository: ambari Description --- Ambari upgrade to 2.1 fails (thinks hbase is installed) Diffs - ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java 3312145 Diff: https://reviews.apache.org/r/36991/diff/ Testing --- unit tests passed Thanks, Dmytro Sen
Review Request 36988: AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36988/ --- Review request for Ambari and Sid Wagle. Repository: ambari Description --- AMS shows a validation error that hbase_regionserver_heapsize should not be below 12GB. Though this is correct, it does not apply when HBase is used in embedded mode - so this validation error should not show up. Diffs - ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 3e34b09 ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py c03e62b Diff: https://reviews.apache.org/r/36988/diff/ Testing --- -- Ran 241 tests in 8.811s OK -- Total run:784 Total errors:0 Total failures:0 OK Thanks, Dmytro Sen
[jira] [Commented] (AMBARI-12609) Host Checks: Rerun checks doesn't work properly
[ https://issues.apache.org/jira/browse/AMBARI-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649340#comment-14649340 ] Aleksandr Kovalenko commented on AMBARI-12609: -- +1 for the patch Host Checks: Rerun checks doesn't work properly - Key: AMBARI-12609 URL: https://issues.apache.org/jira/browse/AMBARI-12609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.2.0 Attachments: AMBARI-12609.patch Since we have started use custom commands for checking hosts after registering Rerun checks doesn't work properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12611) Ambari upgrade to 2.1 fails (thinks hbase is installed)
[ https://issues.apache.org/jira/browse/AMBARI-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-12611: Attachment: AMBARI-12611.patch Ambari upgrade to 2.1 fails (thinks hbase is installed) --- Key: AMBARI-12611 URL: https://issues.apache.org/jira/browse/AMBARI-12611 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12611.patch Ambari upgrade to 2.1 fails (thinks hbase is installed) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12607) Repo build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649423#comment-14649423 ] Hudson commented on AMBARI-12607: - SUCCESS: Integrated in Ambari-trunk-Commit #3203 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3203/]) AMBARI-12607. Repo build script not handling HDP-2.3 or HDP-2.4 stacks (ncole) (ncole: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=8171776ba7bf6fc53541fb295e3f2bed29cc3473) * ambari-server/set-hdp-repo-url.sh Repo build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Attachments: AMBARI-12607.patch Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36986: Repo build script not handling HDP-2.3 or HDP-2.4 stacks
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36986/#review93721 --- Ship it! ambari-server/set-hdp-repo-url.sh (line 60) https://reviews.apache.org/r/36986/#comment148125 Not very maintanable :( Maybe we need a Jira to track this enhancement. - Jonathan Hurley On July 31, 2015, 8:17 a.m., Nate Cole wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36986/ --- (Updated July 31, 2015, 8:17 a.m.) Review request for Ambari and Jonathan Hurley. Bugs: AMBARI-12607 https://issues.apache.org/jira/browse/AMBARI-12607 Repository: ambari Description --- Repo build script not handling HDP-2.3 or HDP-2.4 stacks. Modify the existing script to handle 2.3 and 2.4 stacks. Diffs - ambari-server/set-hdp-repo-url.sh fed7a94 Diff: https://reviews.apache.org/r/36986/diff/ Testing --- No tests required; it's a build issue. Thanks, Nate Cole
[jira] [Commented] (AMBARI-12602) [PluggableStackDefinition] Create tool for generating pluggable stack definition
[ https://issues.apache.org/jira/browse/AMBARI-12602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649237#comment-14649237 ] Hudson commented on AMBARI-12602: - SUCCESS: Integrated in Ambari-branch-2.1 #300 (See [https://builds.apache.org/job/Ambari-branch-2.1/300/]) AMBARI-12602. [PluggableStackDefinition] Create tool for generating pluggable stack definition (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=0d4003790ef423b81ba3fb38922ce2b63297eb4a) * ambari-common/src/main/python/white_labeling/__init__.py * ambari-common/src/main/python/pluggable_stack_definition/__init__.py * ambari-common/src/main/python/white_labeling/WhiteLabelStackDefinition.py * ambari-common/src/main/python/pluggable_stack_definition/test.json * ambari-common/src/main/python/pluggable_stack_definition/GenerateStackDefinition.py * ambari-common/src/main/python/white_labeling/test.json [PluggableStackDefinition] Create tool for generating pluggable stack definition Key: AMBARI-12602 URL: https://issues.apache.org/jira/browse/AMBARI-12602 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 Create tool for generating stack definition from existing one with chnaged set of services, service versions, package list etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12606) Add ZooKeeper Server action is disabled after filtering on hosts page
[ https://issues.apache.org/jira/browse/AMBARI-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649235#comment-14649235 ] Hudson commented on AMBARI-12606: - SUCCESS: Integrated in Ambari-branch-2.1 #300 (See [https://builds.apache.org/job/Ambari-branch-2.1/300/]) AMBARI-12606 Add ZooKeeper Server action is disabled after filtering on hosts page. (atkach) (atkach: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=50c9b23d5dc420bca7839db613c74e93c98ac91e) * ambari-web/app/controllers/main/service/item.js Add ZooKeeper Server action is disabled after filtering on hosts page - Key: AMBARI-12606 URL: https://issues.apache.org/jira/browse/AMBARI-12606 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.1 Attachments: AMBARI-12606.patch STR: 1. Install cluster with at least 2 hosts and install only 1 ZooKeeper Server. 2. Go to Hosts page and apply some filter to get No hosts to display as a result. 3. Without clearing filters go to ZooKeeper service page. Add ZooKeeper Server will be disabled, but we still have available hosts to install ZooKeeper Server on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12600) Update latest url to work for Ubuntu/Debian
[ https://issues.apache.org/jira/browse/AMBARI-12600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649236#comment-14649236 ] Hudson commented on AMBARI-12600: - SUCCESS: Integrated in Ambari-branch-2.1 #300 (See [https://builds.apache.org/job/Ambari-branch-2.1/300/]) AMBARI-12600. Update latest url to work for Ubuntu/Debian (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=056f5c8379ebb224ff438b995aa7900cd8266aef) * ambari-server/src/main/resources/stacks/HDP/2.3/repos/repoinfo.xml.rej Update latest url to work for Ubuntu/Debian --- Key: AMBARI-12600 URL: https://issues.apache.org/jira/browse/AMBARI-12600 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 Currently repositories for ubuntu and debian are not updated with the builds and even fail validation, the second is RE issue. However the first one is taken care in this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12605) SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration
[ https://issues.apache.org/jira/browse/AMBARI-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649238#comment-14649238 ] Hudson commented on AMBARI-12605: - SUCCESS: Integrated in Ambari-branch-2.1 #300 (See [https://builds.apache.org/job/Ambari-branch-2.1/300/]) AMBARI-12605. SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=3d1b2fe892d6258245ce0f8de7a087ea30bf8e31) * ambari-agent/src/main/python/ambari_agent/main.py SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration -- Key: AMBARI-12605 URL: https://issues.apache.org/jira/browse/AMBARI-12605 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 Ambari agent shows warning on every ambari-server restart [root@c6406 ~]# ambari-agent restart Restarting ambari-agent Verifying Python version compatibility... Using python /usr/bin/python2.6 Found ambari-agent PID: 2978 Stopping ambari-agent /usr/lib/python2.6/site-packages/ambari_agent/main.py:314: SyntaxWarning: name 'is_logger_setup' is assigned to before global declaration global is_logger_setup It's related to -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12593) Enable Kerberos: Config values should be trimmed
[ https://issues.apache.org/jira/browse/AMBARI-12593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649524#comment-14649524 ] Hudson commented on AMBARI-12593: - SUCCESS: Integrated in Ambari-branch-2.1 #302 (See [https://builds.apache.org/job/Ambari-branch-2.1/302/]) AMBARI-12593. Enable Kerberos: Config values should be trimmed v2 (alexantonenko) (hiveww: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=1308604b902119f6a9aa005f3a3bd9998873a3ac) * ambari-web/app/data/HDP2/site_properties.js * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * ambari-web/app/assets/test/tests.js * ambari-web/test/controllers/main/admin/kerberos/step2_controller_test.js * ambari-web/app/models/configs/objects/service_config_property.js * ambari-web/app/utils/config.js Enable Kerberos: Config values should be trimmed Key: AMBARI-12593 URL: https://issues.apache.org/jira/browse/AMBARI-12593 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.2.0 Attachments: AMBARI-12593.patch, AMBARI-12593_v2.patch Configurations on Configure Kerberos step in Kerberos wizard should be trimmed. For example if hostname will contain spaces, it's not so obvious and will fail wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12612) Namenode dir textarea vanishes when value contains /home in path
[
https://issues.apache.org/jira/browse/AMBARI-12612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srimanth Gunturi updated AMBARI-12612:
--
Attachment: Screen Shot 2015-07-31 at 11.39.45 AM.png
Screen Shot 2015-07-31 at 10.27.30 AM.png
Namenode dir textarea vanishes when value contains /home in path
Key: AMBARI-12612
URL: https://issues.apache.org/jira/browse/AMBARI-12612
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.0
Reporter: Srimanth Gunturi
Fix For: 2.1.1
Attachments: Screen Shot 2015-07-31 at 10.27.30 AM.png, Screen Shot
2015-07-31 at 11.39.45 AM.png
Install a cluster with ZK+AMS services only. Then add HDFS service using the
add-service wizard. In the configurations step, enter the value of 'NameNode
directories' to '/home/foo' which should generate the validation error
{{Can't start with home(s)}}.
Now switch to configs of all other services and go back to HDFS configs. Now
the textarea is not shown.
Workaround: Hit _Back_ followed by _Next_ to show the text-area. OR just
refresh the page to repopulate the configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649549#comment-14649549 ] Jaimin D Jetly commented on AMBARI-12598: - +1 for the patch kafka_client_jaas.conf not being managed by Ambari -- Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.1 Attachments: AMBARI-12598.patch when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12483) Code clean; Documentation; Add more features about Docker networking and image building
[ https://issues.apache.org/jira/browse/AMBARI-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pengcheng Xu updated AMBARI-12483: -- Attachment: AMBARI-12483.patch add comments, document, add Weave DNS, add host network setup script, change cluster configuration, add new Docker image install methods add Ambari-agents inside VM, fix network issued, add SSH to Docker container, automatic network configuration, new command line interface Code clean; Documentation; Add more features about Docker networking and image building --- Key: AMBARI-12483 URL: https://issues.apache.org/jira/browse/AMBARI-12483 Project: Ambari Issue Type: Technical task Components: ambari-agent Reporter: Pengcheng Xu Assignee: Pengcheng Xu Fix For: 2.2.0 Attachments: AMBARI-12483.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12612) Namenode dir textarea vanishes when value contains /home in path
Srimanth Gunturi created AMBARI-12612:
-
Summary: Namenode dir textarea vanishes when value contains /home
in path
Key: AMBARI-12612
URL: https://issues.apache.org/jira/browse/AMBARI-12612
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.0
Reporter: Srimanth Gunturi
Fix For: 2.1.1
Install a cluster with ZK+AMS services only. Then add HDFS service using the
add-service wizard. In the configurations step, enter the value of 'NameNode
directories' to '/home/foo' which should generate the validation error {{Can't
start with home(s)}}.
Now switch to configs of all other services and go back to HDFS configs. Now
the textarea is not shown.
Workaround: Hit _Back_ followed by _Next_ to show the text-area. OR just
refresh the page to repopulate the configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-11741) HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available
[ https://issues.apache.org/jira/browse/AMBARI-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649596#comment-14649596 ] Xi Wang commented on AMBARI-11741: -- Second patch committed to trunk and branch-2.1 HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available -- Key: AMBARI-11741 URL: https://issues.apache.org/jira/browse/AMBARI-11741 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-11741-2.patch, AMBARI-11741.patch When Ambari is not able to get JMX metrics from the NameNode (this is a separate issue). It's showing n/a for most, except Upgrade status. It is incorrectly showing Upgrade not finalized. If data is not available, it should say n/a. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-11741) HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available
[ https://issues.apache.org/jira/browse/AMBARI-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang resolved AMBARI-11741. -- Resolution: Fixed HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available -- Key: AMBARI-11741 URL: https://issues.apache.org/jira/browse/AMBARI-11741 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-11741-2.patch, AMBARI-11741.patch When Ambari is not able to get JMX metrics from the NameNode (this is a separate issue). It's showing n/a for most, except Upgrade status. It is incorrectly showing Upgrade not finalized. If data is not available, it should say n/a. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36649: Simulate Ambari Agents to test 3k Node Cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36649/ --- (Updated July 31, 2015, 6:48 p.m.) Review request for Ambari and Alejandro Fernandez. Changes --- add comments, document, add Weave DNS, add host network setup script, change cluster configuration, add new Docker image install methods add Ambari-agents inside VM, fix network issued, add SSH to Docker container, automatic network configuration, new command line interface Bugs: AMBARI-12339 https://issues.apache.org/jira/browse/AMBARI-12339 Repository: ambari Description --- Code clean; Documentation; Add more features about Docker networking and image building Diffs (updated) - contrib/agent-simulator/Docker/Dockerfile d22435a contrib/agent-simulator/Docker/Raw_Dockerfile PRE-CREATION contrib/agent-simulator/Docker/Yum_Dockerfile PRE-CREATION contrib/agent-simulator/Docker/ambari_agent_start.sh 4ba2361 contrib/agent-simulator/Docker/launcher_agent.py 5ff008d contrib/agent-simulator/Docker/package_list.txt PRE-CREATION contrib/agent-simulator/Linux/CentOS7/docker_install.sh 033c2b9 contrib/agent-simulator/Linux/CentOS7/set_docker_partition.sh PRE-CREATION contrib/agent-simulator/Linux/CentOS7/weave_install.sh 6788184 contrib/agent-simulator/Linux/Ubuntu12/docker_install.sh 220f1a4 contrib/agent-simulator/Linux/Ubuntu12/weave_install.sh 332488d contrib/agent-simulator/README.md PRE-CREATION contrib/agent-simulator/cluster.py 55c3c44 contrib/agent-simulator/config.py 20cc8de contrib/agent-simulator/config/config.ini a3afa33 contrib/agent-simulator/docker.py e397c4b contrib/agent-simulator/example/config.ini PRE-CREATION contrib/agent-simulator/launcher_cluster.py 0a7cbe0 contrib/agent-simulator/launcher_docker.py 48e8fac contrib/agent-simulator/log.py PRE-CREATION contrib/agent-simulator/network/DNS_editor.py PRE-CREATION contrib/agent-simulator/network/set_ambari_server_network.sh PRE-CREATION contrib/agent-simulator/network/set_host_network.sh PRE-CREATION contrib/agent-simulator/server/ambari_server_install.sh PRE-CREATION contrib/agent-simulator/server/ambari_server_reset_data.sh PRE-CREATION contrib/agent-simulator/server_setup.sh 3b499aa contrib/agent-simulator/tips.txt 207177d contrib/agent-simulator/vm.py 90de4de Diff: https://reviews.apache.org/r/36649/diff/ Testing --- Manually tested on Google Compute Thanks, Pengcheng Xu
[jira] [Commented] (AMBARI-12609) Host Checks: Rerun checks doesn't work properly
[ https://issues.apache.org/jira/browse/AMBARI-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649562#comment-14649562 ] Hudson commented on AMBARI-12609: - SUCCESS: Integrated in Ambari-trunk-Commit #3204 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3204/]) AMBARI-12609. Host Checks: Rerun checks doesn't work properly (alexantonenko) (hiveww: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=03bad617aac82e16b00bfdc3e6dbaa634b7f) * ambari-web/app/controllers/wizard/step3_controller.js Host Checks: Rerun checks doesn't work properly - Key: AMBARI-12609 URL: https://issues.apache.org/jira/browse/AMBARI-12609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.2.0 Attachments: AMBARI-12609.patch Since we have started use custom commands for checking hosts after registering Rerun checks doesn't work properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12610) AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649564#comment-14649564 ] Hudson commented on AMBARI-12610: - SUCCESS: Integrated in Ambari-trunk-Commit #3204 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3204/]) AMBARI-12610 AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=52ee2ffef96db0f6fade15c8786280cbca93f913) * ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode -- Key: AMBARI-12610 URL: https://issues.apache.org/jira/browse/AMBARI-12610 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12610.patch AMS shows a validation error that hbase_regionserver_heapsize should not be below 12GB. Though this is correct, it does not apply when HBase is used in embedded mode - so this validation error should not show up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12593) Enable Kerberos: Config values should be trimmed
[ https://issues.apache.org/jira/browse/AMBARI-12593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649563#comment-14649563 ] Hudson commented on AMBARI-12593: - SUCCESS: Integrated in Ambari-trunk-Commit #3204 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3204/]) AMBARI-12593. Enable Kerberos: Config values should be trimmed v2 (alexantonenko) (hiveww: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=10409b3d8a1f747d5e2ee7a9b2c0cbe93ccddd71) * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * ambari-web/app/utils/config.js * ambari-web/test/controllers/main/admin/kerberos/step2_controller_test.js * ambari-web/app/models/configs/objects/service_config_property.js * ambari-web/app/assets/test/tests.js * ambari-web/app/data/HDP2/site_properties.js Enable Kerberos: Config values should be trimmed Key: AMBARI-12593 URL: https://issues.apache.org/jira/browse/AMBARI-12593 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.2.0 Attachments: AMBARI-12593.patch, AMBARI-12593_v2.patch Configurations on Configure Kerberos step in Kerberos wizard should be trimmed. For example if hostname will contain spaces, it's not so obvious and will fail wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12611) Ambari upgrade to 2.1 fails (thinks hbase is installed)
[
https://issues.apache.org/jira/browse/AMBARI-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649586#comment-14649586
]
Hadoop QA commented on AMBARI-12611:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748197/AMBARI-12611.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3506//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3506//console
This message is automatically generated.
Ambari upgrade to 2.1 fails (thinks hbase is installed)
---
Key: AMBARI-12611
URL: https://issues.apache.org/jira/browse/AMBARI-12611
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12611.patch
Ambari upgrade to 2.1 fails (thinks hbase is installed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12483) Code clean; Documentation; Add more features about Docker networking and image building
[ https://issues.apache.org/jira/browse/AMBARI-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pengcheng Xu updated AMBARI-12483: -- Attachment: (was: AMBARI-12483.patch) Code clean; Documentation; Add more features about Docker networking and image building --- Key: AMBARI-12483 URL: https://issues.apache.org/jira/browse/AMBARI-12483 Project: Ambari Issue Type: Technical task Components: ambari-agent Reporter: Pengcheng Xu Assignee: Pengcheng Xu Fix For: 2.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
Robert Levas created AMBARI-12613: - Summary: Allow for granular authorization inorder to update User resource properties via Ambari's REST API Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1, 2.1.1 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11741) HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available
[ https://issues.apache.org/jira/browse/AMBARI-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649722#comment-14649722 ] Hudson commented on AMBARI-11741: - SUCCESS: Integrated in Ambari-trunk-Commit #3205 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3205/]) AMBARI-11741. HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available.(xiwang) (xiwang: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=1063607070ddc488952c5ff23f07eb6293f8bb64) * ambari-web/app/views/main/service/services/hdfs.js * ambari-web/app/models/service/hdfs.js HDFS Dashboard is incorrectly showing 'Upgrade not finalized' when NameNode JMX data not available -- Key: AMBARI-11741 URL: https://issues.apache.org/jira/browse/AMBARI-11741 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-11741-2.patch, AMBARI-11741.patch When Ambari is not able to get JMX metrics from the NameNode (this is a separate issue). It's showing n/a for most, except Upgrade status. It is incorrectly showing Upgrade not finalized. If data is not available, it should say n/a. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12611) Ambari upgrade to 2.1 fails (thinks hbase is installed)
[ https://issues.apache.org/jira/browse/AMBARI-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649692#comment-14649692 ] Hudson commented on AMBARI-12611: - SUCCESS: Integrated in Ambari-branch-2.1 #303 (See [https://builds.apache.org/job/Ambari-branch-2.1/303/]) AMBARI-12611 Ambari upgrade to 2.1 fails (thinks hbase is installed) (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d21cad5e4d89c506c0feca0dd7d881acd86ecf75) * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java Ambari upgrade to 2.1 fails (thinks hbase is installed) --- Key: AMBARI-12611 URL: https://issues.apache.org/jira/browse/AMBARI-12611 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12611.patch Ambari upgrade to 2.1 fails (thinks hbase is installed) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12607) Repo build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649691#comment-14649691 ] Hudson commented on AMBARI-12607: - SUCCESS: Integrated in Ambari-branch-2.1 #303 (See [https://builds.apache.org/job/Ambari-branch-2.1/303/]) AMBARI-12607. Repo build script not handling HDP-2.3 or HDP-2.4 stacks; part 2 (ncole) (ncole: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f133ec41ea09daf03226e2d5be04c88c2ed3317e) * ambari-server/set-hdp-repo-url.sh Repo build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Attachments: AMBARI-12607.patch Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12610) AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-12610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649693#comment-14649693 ] Hudson commented on AMBARI-12610: - SUCCESS: Integrated in Ambari-branch-2.1 #303 (See [https://builds.apache.org/job/Ambari-branch-2.1/303/]) AMBARI-12610 AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=2c155528d204ae32657b87016cc9ae83aa877dde) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py AMS: hbase_regionserver_heapsize validation error should not apply when HBase is used in embedded mode -- Key: AMBARI-12610 URL: https://issues.apache.org/jira/browse/AMBARI-12610 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12610.patch AMS shows a validation error that hbase_regionserver_heapsize should not be below 12GB. Though this is correct, it does not apply when HBase is used in embedded mode - so this validation error should not show up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649724#comment-14649724 ] Hudson commented on AMBARI-12598: - SUCCESS: Integrated in Ambari-trunk-Commit #3205 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3205/]) AMBARI-12598. kafka_client_jaas.conf not being managed by Ambari. (Sriharsha Chintalapani via jaimin) (jaimin: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=3a2381f589c291721cbc740ed68fce10d50f3a2c) * ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/templates/kafka_client_jaas.conf.j2 * ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka.py kafka_client_jaas.conf not being managed by Ambari -- Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.1 Attachments: AMBARI-12598.patch when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12607) Repo build script not handling HDP-2.3 or HDP-2.4 stacks
[ https://issues.apache.org/jira/browse/AMBARI-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649721#comment-14649721 ] Hudson commented on AMBARI-12607: - SUCCESS: Integrated in Ambari-trunk-Commit #3205 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3205/]) AMBARI-12607. Repo build script not handling HDP-2.3 or HDP-2.4 stacks; part 2 (ncole) (ncole: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=69a29494c375a24e895f3d363073a3bc0952ee18) * ambari-server/set-hdp-repo-url.sh Repo build script not handling HDP-2.3 or HDP-2.4 stacks Key: AMBARI-12607 URL: https://issues.apache.org/jira/browse/AMBARI-12607 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.1.1 Attachments: AMBARI-12607.patch Need the repo replacement script to handle HDP-2.3 and HDP-2.4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12611) Ambari upgrade to 2.1 fails (thinks hbase is installed)
[ https://issues.apache.org/jira/browse/AMBARI-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649723#comment-14649723 ] Hudson commented on AMBARI-12611: - SUCCESS: Integrated in Ambari-trunk-Commit #3205 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3205/]) AMBARI-12611 Ambari upgrade to 2.1 fails (thinks hbase is installed) (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=ffc45f57a83006493f4c763cddd71e879e5bbe6b) * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java Ambari upgrade to 2.1 fails (thinks hbase is installed) --- Key: AMBARI-12611 URL: https://issues.apache.org/jira/browse/AMBARI-12611 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12611.patch Ambari upgrade to 2.1 fails (thinks hbase is installed) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 36995: Simulate Ambari Agents to test 3k Node Cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36995/ --- Review request for Ambari and Alejandro Fernandez. Bugs: AMBARI-12339 https://issues.apache.org/jira/browse/AMBARI-12339 Repository: ambari Description --- add comments, document, add Weave DNS, add host network setup script, change cluster configuration, add new Docker image install methods add Ambari-agents inside VM, fix network issued, add SSH to Docker container, automatic network configuration, new command line interface Diffs - contrib/agent-simulator/Docker/Dockerfile d22435a contrib/agent-simulator/Docker/__init__.py 62aeca1 contrib/agent-simulator/Docker/ambari_agent_start.sh 4ba2361 contrib/agent-simulator/Docker/launcher_agent.py 5ff008d contrib/agent-simulator/Linux/CentOS7/docker_install.sh 033c2b9 contrib/agent-simulator/Linux/CentOS7/set_docker_partition.sh PRE-CREATION contrib/agent-simulator/Linux/CentOS7/weave_install.sh 6788184 contrib/agent-simulator/Linux/Ubuntu12/docker_install.sh 220f1a4 contrib/agent-simulator/Linux/Ubuntu12/weave_install.sh 332488d contrib/agent-simulator/README.md PRE-CREATION contrib/agent-simulator/cluster.py 55c3c44 contrib/agent-simulator/config.py 20cc8de contrib/agent-simulator/config/config.ini a3afa33 contrib/agent-simulator/data.py PRE-CREATION contrib/agent-simulator/docker.py e397c4b contrib/agent-simulator/docker_image/Yum_Dockerfile PRE-CREATION contrib/agent-simulator/docker_image/__init__.py PRE-CREATION contrib/agent-simulator/docker_image/ambari_agent_install.sh PRE-CREATION contrib/agent-simulator/docker_image/ambari_agent_start.sh PRE-CREATION contrib/agent-simulator/docker_image/launcher_agent.py PRE-CREATION contrib/agent-simulator/docker_image/package_list.txt PRE-CREATION contrib/agent-simulator/docker_image/ssh_service/run.sh PRE-CREATION contrib/agent-simulator/docker_image/ssh_service/set_root_pw.sh PRE-CREATION contrib/agent-simulator/example/config.ini PRE-CREATION contrib/agent-simulator/launcher_ambari_server.py PRE-CREATION contrib/agent-simulator/launcher_cluster.py 0a7cbe0 contrib/agent-simulator/launcher_docker.py 48e8fac contrib/agent-simulator/launcher_service_server.py PRE-CREATION contrib/agent-simulator/log.py PRE-CREATION contrib/agent-simulator/network/DNS_editor.py PRE-CREATION contrib/agent-simulator/network/set_ambari_server_network.sh PRE-CREATION contrib/agent-simulator/network/set_host_network.sh PRE-CREATION contrib/agent-simulator/server/ambari_server_install.sh PRE-CREATION contrib/agent-simulator/server/ambari_server_reset_data.sh PRE-CREATION contrib/agent-simulator/server/ambari_server_start.sh PRE-CREATION contrib/agent-simulator/server_setup.sh 3b499aa contrib/agent-simulator/tips.txt 207177d contrib/agent-simulator/vm.py 90de4de Diff: https://reviews.apache.org/r/36995/diff/ Testing --- Manually tested on Google Compute Thanks, Pengcheng Xu
[jira] [Updated] (AMBARI-12483) Code clean; Documentation; Add more features about Docker networking and image building
[ https://issues.apache.org/jira/browse/AMBARI-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pengcheng Xu updated AMBARI-12483: -- Attachment: AMBARI-12483.patch Code clean; Documentation; Add more features about Docker networking and image building --- Key: AMBARI-12483 URL: https://issues.apache.org/jira/browse/AMBARI-12483 Project: Ambari Issue Type: Technical task Components: ambari-agent Reporter: Pengcheng Xu Assignee: Pengcheng Xu Fix For: 2.2.0 Attachments: AMBARI-12483.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12483) Code clean; Documentation; Add more features about Docker networking and image building
[ https://issues.apache.org/jira/browse/AMBARI-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pengcheng Xu updated AMBARI-12483: -- Attachment: (was: AMBARI-12483.patch) Code clean; Documentation; Add more features about Docker networking and image building --- Key: AMBARI-12483 URL: https://issues.apache.org/jira/browse/AMBARI-12483 Project: Ambari Issue Type: Technical task Components: ambari-agent Reporter: Pengcheng Xu Assignee: Pengcheng Xu Fix For: 2.2.0 Attachments: AMBARI-12483.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12614) Ambari should provide defining optional client dependencies in metainfo.xml. Now all client dependencies defined in metainfo.xml are required.
Mahesh Kurapati created AMBARI-12614: Summary: Ambari should provide defining optional client dependencies in metainfo.xml. Now all client dependencies defined in metainfo.xml are required. Key: AMBARI-12614 URL: https://issues.apache.org/jira/browse/AMBARI-12614 Project: Ambari Issue Type: Bug Reporter: Mahesh Kurapati In Amabri 2.1.0 release, Ambari team added new client dependency check before adding/installing components based on JIRA https://issues.apache.org/jira/browse/AMBARI-10131. Based on this whenever we add new component to any hosts Ambari UI checks client dependencies defined in metainfo.xml file. If dependency clients not installed on same host then Ambari UI gives error and not allow install that component. Because of this even service for that client not installed, new Component not allowed to be installed. For example if HBase service not installed to the cluster and try to add custom component using Host Add action gives error that HBase client need to be installed prior to component install. This makes HBase client become a required client even though HBase service doesn't exist. Our custom component works without HBase we want to define HBase client as optional dependency. i.e if HBase service exist it should check for HBase client, other wise it should ignore HBase client exist check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12574) Add distributionManagement tag to ambari-metrics.
[ https://issues.apache.org/jira/browse/AMBARI-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649794#comment-14649794 ] Siddharth Wagle commented on AMBARI-12574: -- Pushed to branch-2.1 Add distributionManagement tag to ambari-metrics. - Key: AMBARI-12574 URL: https://issues.apache.org/jira/browse/AMBARI-12574 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.1.0 Environment: Deploy the ambari metrics artifacts to Nexus. Reporter: Ashish Singh Assignee: Ashish Singh Priority: Critical Fix For: 2.1.0, 2.1.1, 2.1.2, trunk Attachments: 0001-AMBARI-12574-Add-distributionManagement-tag-to-ambar.patch Add distributionManagement to ambari metrics. This is needed for Open Data Platform initiative. Currently, without this tag deploy build will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Summary: Add Data Visualization to Hive View (was: Data Visualization to Hive View) Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12503) Display a warning if Oozie is configured with Derby as the db store
[ https://issues.apache.org/jira/browse/AMBARI-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-12503: - Description: It would be good to display a warning if Derby is used as the database for Oozie. While it is useful for quick development or sandbox envs, for production we should advise users to use a supported DB like MySQL, Postgres or Oracle Embedded derby does not allow concurrent connections and is not supported for Oozie HA and will cause slow running of Oozie in action progress under heavier workloads. was: As discussed, it would be good to display a warning if Derby is used as the database for Oozie. While it is useful for quick development or sandbox envs, for production we should advise users to use a supported DB like MySQL, Postgres or Oracle Embedded derby does not allow concurrent connections and is not supported for Oozie HA and will cause slow running of Oozie in action progress under heavier workloads. Display a warning if Oozie is configured with Derby as the db store --- Key: AMBARI-12503 URL: https://issues.apache.org/jira/browse/AMBARI-12503 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12503.patch It would be good to display a warning if Derby is used as the database for Oozie. While it is useful for quick development or sandbox envs, for production we should advise users to use a supported DB like MySQL, Postgres or Oracle Embedded derby does not allow concurrent connections and is not supported for Oozie HA and will cause slow running of Oozie in action progress under heavier workloads. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-12613: - Affects Version/s: (was: 2.1.1) Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12597) Upgrade to Ambari 2.1 should support custom stack names
[
https://issues.apache.org/jira/browse/AMBARI-12597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yaolei updated AMBARI-12597:
Description:
When upgrading to Ambari 2.1.0, with a custom stack name and version that
contains letters, the Ambari Upgrade will fail, and most likely so will
starting services.
E.g.,
/var/lib/ambari-server/stacks/
2.2
2.2.MYNAME
If 2.2.MYNAME is a stack, then the upgrade to Ambari 2.1 will attempt to
insert a record in the stack table. The upgrade will then try to insert
appropriate repo_version items, and then fail when trying to compare versions.
First error,
{code}
1) Error injecting method, java.lang.NullPointerException
at
org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:242)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.class(AmbariMetaInfo.java:124)
while locating org.apache.ambari.server.api.services.AmbariMetaInfo
1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at
org.apache.ambari.server.upgrade.UpgradeCatalog210.executeStackPreDMLUpdates(UpgradeCatalog210.java:670)
at
org.apache.ambari.server.upgrade.UpgradeCatalog210.executePreDMLUpdates(UpgradeCatalog210.java:985)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.preUpgradeData(AbstractUpgradeCatalog.java:531)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executePreDMLUpdates(SchemaUpgradeHelper.java:205)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:295)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.stack.StackModule.processRepositories(StackModule.java:650)
at
org.apache.ambari.server.stack.StackModule.resolve(StackModule.java:159)
at
org.apache.ambari.server.stack.StackManager.fullyResolveStacks(StackManager.java:201)
at
org.apache.ambari.server.stack.StackManager.init(StackManager.java:119)
at
org.apache.ambari.server.stack.StackManager$$FastClassByGuice$$33e4ffe0.newInstance(generated)
at
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
at
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
at
com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
at com.sun.proxy.$Proxy26.create(Unknown Source)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:246)
at
org.apache.ambari.server.api.services.AmbariMetaInfo$$FastClassByGuice$$202844bc.invoke(generated)
at
com.google.inject.internal.cglib.reflect.$FastMethod.invoke(FastMethod.java:53)
at
com.google.inject.internal.SingleMethodInjector$1.invoke(SingleMethodInjector.java:56)
at
com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:90)
at
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
... 6 more
{code}
Next error,
{code}
java.lang.NumberFormatException: For input string: NEA
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at
[jira] [Updated] (AMBARI-12597) Upgrade to Ambari 2.1 should support custom stack names
[
https://issues.apache.org/jira/browse/AMBARI-12597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yaolei updated AMBARI-12597:
Description:
When upgrading to Ambari 2.1.0, with a custom stack name and version that
contains letters, the Ambari Upgrade will fail, and most likely so will
starting services.
E.g.,
/var/lib/ambari-server/stacks/HDP/
2.2
2.2.MYNAME
If 2.2.MYNAME is a stack, then the upgrade to Ambari 2.1 will attempt to
insert a record in the stack table. The upgrade will then try to insert
appropriate repo_version items, and then fail when trying to compare versions.
First error,
{code}
1) Error injecting method, java.lang.NullPointerException
at
org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:242)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.class(AmbariMetaInfo.java:124)
while locating org.apache.ambari.server.api.services.AmbariMetaInfo
1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at
org.apache.ambari.server.upgrade.UpgradeCatalog210.executeStackPreDMLUpdates(UpgradeCatalog210.java:670)
at
org.apache.ambari.server.upgrade.UpgradeCatalog210.executePreDMLUpdates(UpgradeCatalog210.java:985)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.preUpgradeData(AbstractUpgradeCatalog.java:531)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executePreDMLUpdates(SchemaUpgradeHelper.java:205)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:295)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.stack.StackModule.processRepositories(StackModule.java:650)
at
org.apache.ambari.server.stack.StackModule.resolve(StackModule.java:159)
at
org.apache.ambari.server.stack.StackManager.fullyResolveStacks(StackManager.java:201)
at
org.apache.ambari.server.stack.StackManager.init(StackManager.java:119)
at
org.apache.ambari.server.stack.StackManager$$FastClassByGuice$$33e4ffe0.newInstance(generated)
at
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
at
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
at
com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
at com.sun.proxy.$Proxy26.create(Unknown Source)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:246)
at
org.apache.ambari.server.api.services.AmbariMetaInfo$$FastClassByGuice$$202844bc.invoke(generated)
at
com.google.inject.internal.cglib.reflect.$FastMethod.invoke(FastMethod.java:53)
at
com.google.inject.internal.SingleMethodInjector$1.invoke(SingleMethodInjector.java:56)
at
com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:90)
at
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
... 6 more
{code}
Next error,
{code}
java.lang.NumberFormatException: For input string: NEA
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at
[jira] [Created] (AMBARI-12599) Tez View should make timezone configurable from Ambari
Sreenath Somarajapuram created AMBARI-12599: --- Summary: Tez View should make timezone configurable from Ambari Key: AMBARI-12599 URL: https://issues.apache.org/jira/browse/AMBARI-12599 Project: Ambari Issue Type: Bug Reporter: Sreenath Somarajapuram As a followup to TEZ-2211, like YARN Timeline Server URL YARN ResourceManager URL user must be abel to set timezone from Tez View. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12599) Tez View should make timezone configurable from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648861#comment-14648861 ] Sreenath Somarajapuram commented on AMBARI-12599: - \cc [~hitesh] [~pramachandran] Tez View should make timezone configurable from Ambari -- Key: AMBARI-12599 URL: https://issues.apache.org/jira/browse/AMBARI-12599 Project: Ambari Issue Type: Bug Reporter: Sreenath Somarajapuram As a followup to TEZ-2211, like YARN Timeline Server URL YARN ResourceManager URL user must be abel to set timezone from Tez View. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12538) Attempting to access the Ambari Dashboard results in an HTTP 500 Error after changing cluster name and restarting the Ambari server
[
https://issues.apache.org/jira/browse/AMBARI-12538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated AMBARI-12538:
---
Fix Version/s: 2.1.1
Attempting to access the Ambari Dashboard results in an HTTP 500 Error after
changing cluster name and restarting the Ambari server
---
Key: AMBARI-12538
URL: https://issues.apache.org/jira/browse/AMBARI-12538
Project: Ambari
Issue Type: Bug
Affects Versions: 2.1.0
Environment: SLES11 SP3
Reporter: Zack Marsh
Priority: Critical
Fix For: 2.1.1
Steps to reproduce:
* Login to Ambari Web UI
* Rename cluster (Admin - Manage Ambari - Rename Cluister - Enter new
name )
* Restart Ambari Server via CLI (ambari-server restart)
* Login to Ambari Web UI again
* When attempting to access the Ambari Dashboard an HTTP 500 Error will occur:
{code}
Error
500 status code received on GET method for API:
/api/v1/clusters/CLUSTERNAME/requests?to=endpage_size=10fields=Requests
Error message: Server Error
{code}
Excerpt from the Ambari Server log:
{code}
24 Jul 2015 16:40:41,013 ERROR [qtp-client-25] ReadHandler:91 - Caught a
runtime exception executing a query
java.lang.RuntimeException: Failed to construct logical request during
replay: org.apache.ambari.server.ClusterNotFoundException: Cluster not found,
clusterName=PIRIPIRI
at
org.apache.ambari.server.topology.PersistedStateImpl.getAllRequests(PersistedStateImpl.java:167)
at
org.apache.ambari.server.topology.TopologyManager.ensureInitialized(TopologyManager.java:91)
at
org.apache.ambari.server.topology.TopologyManager.getRequests(TopologyManager.java:198)
at
org.apache.ambari.server.actionmanager.ActionManager.getRequestsByStatus(ActionManager.java:232)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider.getRequestResources(RequestResourceProvider.java:414)
at
org.apache.ambari.server.controller.internal.RequestResourceProvider.getResources(RequestResourceProvider.java:200)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
at
org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:482)
at
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:381)
at
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
at
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:105)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
at
org.apache.ambari.server.api.services.RequestService.getRequests(RequestService.java:95)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
[jira] [Assigned] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-12598: --- Assignee: Sriharsha Chintalapani kafka_client_jaas.conf not being managed by Ambari -- Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.0 when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-9776) Ambari server 1.7 installation issue
[ https://issues.apache.org/jira/browse/AMBARI-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648873#comment-14648873 ] David Zhu commented on AMBARI-9776: --- I can reproduce this error on v. 2.1.0 and the master branch. and the method suggested by [~wael.emam] did not work for me. Ambari server 1.7 installation issue Key: AMBARI-9776 URL: https://issues.apache.org/jira/browse/AMBARI-9776 Project: Ambari Issue Type: Bug Environment: RHEL 6.6 64-bit Reporter: Wael Emam after installing ambari-server 1.7 on my box, for some reason I can not access ambari's portal on 8080. My browser just keeps trying to connect. I have no firewall or selinux running. I made sure that postgresql and ambari-server are running. In ambari-server.out, I can see some warning on A HTTP GET method eb 24, 2015 1:06:10 PM com.sun.jersey.spi.inject.Errors processErrorMessages WARNING: The following warnings have been detected with resource and/or provider classes: WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.BlueprintService.getBlueprints(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.BlueprintService.getBlueprint(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RequestService.getRequests(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RequestService.getRequest(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.FeedService.getFeeds(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.FeedService.getFeed(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.ActionService.getActionDefinitions(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.ActionService.getActionDefinition(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.UserService.getUsers(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.UserService.getUser(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.ClusterService.getClusters(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.ClusterService.getCluster(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.TargetClusterService.getTargetClusters(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.TargetClusterService.getTargetCluster(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getServices(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response
[jira] [Updated] (AMBARI-12597) Upgrade to Ambari 2.1 should support custom stack names
[
https://issues.apache.org/jira/browse/AMBARI-12597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yaolei updated AMBARI-12597:
Description:
When upgrading to Ambari 2.1.0, with a custom stack name and version that
contains letters, the Ambari Upgrade will fail, and most likely so will
starting services.
E.g.,
/var/lib/ambari-server/stacks/H
2.2
2.2.MYNAME
If 2.2.MYNAME is a stack, then the upgrade to Ambari 2.1 will attempt to
insert a record in the stack table. The upgrade will then try to insert
appropriate repo_version items, and then fail when trying to compare versions.
First error,
{code}
1) Error injecting method, java.lang.NullPointerException
at
org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:242)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.class(AmbariMetaInfo.java:124)
while locating org.apache.ambari.server.api.services.AmbariMetaInfo
1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at
org.apache.ambari.server.upgrade.UpgradeCatalog210.executeStackPreDMLUpdates(UpgradeCatalog210.java:670)
at
org.apache.ambari.server.upgrade.UpgradeCatalog210.executePreDMLUpdates(UpgradeCatalog210.java:985)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.preUpgradeData(AbstractUpgradeCatalog.java:531)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executePreDMLUpdates(SchemaUpgradeHelper.java:205)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:295)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.stack.StackModule.processRepositories(StackModule.java:650)
at
org.apache.ambari.server.stack.StackModule.resolve(StackModule.java:159)
at
org.apache.ambari.server.stack.StackManager.fullyResolveStacks(StackManager.java:201)
at
org.apache.ambari.server.stack.StackManager.init(StackManager.java:119)
at
org.apache.ambari.server.stack.StackManager$$FastClassByGuice$$33e4ffe0.newInstance(generated)
at
com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
at
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
at
com.google.inject.assistedinject.FactoryProvider2.invoke(FactoryProvider2.java:632)
at com.sun.proxy.$Proxy26.create(Unknown Source)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:246)
at
org.apache.ambari.server.api.services.AmbariMetaInfo$$FastClassByGuice$$202844bc.invoke(generated)
at
com.google.inject.internal.cglib.reflect.$FastMethod.invoke(FastMethod.java:53)
at
com.google.inject.internal.SingleMethodInjector$1.invoke(SingleMethodInjector.java:56)
at
com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:90)
at
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at
com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
... 6 more
{code}
Next error,
{code}
java.lang.NumberFormatException: For input string: NEA
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at
[jira] [Created] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
Sriharsha Chintalapani created AMBARI-12598: --- Summary: kafka_client_jaas.conf not being managed by Ambari Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Fix For: 2.1.0 when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-12598: --- Fix Version/s: (was: 2.1.0) 2.1.1 kafka_client_jaas.conf not being managed by Ambari -- Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.1 when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-12598: Attachment: AMBARI-12598.patch kafka_client_jaas.conf not being managed by Ambari -- Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.1 Attachments: AMBARI-12598.patch when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648830#comment-14648830 ] Sriharsha Chintalapani commented on AMBARI-12598: - [~u39kun] [~jaimin] here is the patch https://reviews.apache.org/r/36976/ kafka_client_jaas.conf not being managed by Ambari -- Key: AMBARI-12598 URL: https://issues.apache.org/jira/browse/AMBARI-12598 Project: Ambari Issue Type: Bug Affects Versions: 2.1.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.1.1 when kafka gets kerberized we need 2 jaas files kafka_jaas.conf used by server kafka_client_jaas.conf used by kafka command line tools to connect to kafka server. Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw kerberos exception UNKNOWN_SERVER. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12606) Add ZooKeeper Server action is disabled after filtering on hosts page
[
https://issues.apache.org/jira/browse/AMBARI-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649108#comment-14649108
]
Hadoop QA commented on AMBARI-12606:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748156/AMBARI-12606.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3505//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3505//console
This message is automatically generated.
Add ZooKeeper Server action is disabled after filtering on hosts page
-
Key: AMBARI-12606
URL: https://issues.apache.org/jira/browse/AMBARI-12606
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.1.1
Attachments: AMBARI-12606.patch
STR:
1. Install cluster with at least 2 hosts and install only 1 ZooKeeper Server.
2. Go to Hosts page and apply some filter to get No hosts to display as a
result.
3. Without clearing filters go to ZooKeeper service page.
Add ZooKeeper Server will be disabled, but we still have available hosts to
install ZooKeeper Server on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12606) Add ZooKeeper Server action is disabled after filtering on hosts page
[ https://issues.apache.org/jira/browse/AMBARI-12606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649112#comment-14649112 ] Andrii Tkach commented on AMBARI-12606: --- committed to trunk and branch-2.1 Add ZooKeeper Server action is disabled after filtering on hosts page - Key: AMBARI-12606 URL: https://issues.apache.org/jira/browse/AMBARI-12606 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.1 Attachments: AMBARI-12606.patch STR: 1. Install cluster with at least 2 hosts and install only 1 ZooKeeper Server. 2. Go to Hosts page and apply some filter to get No hosts to display as a result. 3. Without clearing filters go to ZooKeeper service page. Add ZooKeeper Server will be disabled, but we still have available hosts to install ZooKeeper Server on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12615) Add Data Visualization to Hive View
[
https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650139#comment-14650139
]
Hadoop QA commented on AMBARI-12615:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748289/AMBARI-12615.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3510//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3510//console
This message is automatically generated.
Add Data Visualization to Hive View
---
Key: AMBARI-12615
URL: https://issues.apache.org/jira/browse/AMBARI-12615
Project: Ambari
Issue Type: New Feature
Components: ambari-views
Affects Versions: 2.2.0
Reporter: Vivek Ratnavel Subramanian
Assignee: Vivek Ratnavel Subramanian
Fix For: 2.2.0
Attachments: AMBARI-12615.patch
There is no existing visualization tool to visualize the result set data in
Hive View.
Hive view should support a visualization tool with the following features.
1) Ability to visualize result set data in Hive View.
2) Ability to visualize multiple dimensions in the result set with different
types of charts
3) Support all modern browsers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12141) Kerberos configs aren't restored when moving back from Review to the Configure Identities step
[ https://issues.apache.org/jira/browse/AMBARI-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650140#comment-14650140 ] Hudson commented on AMBARI-12141: - FAILURE: Integrated in Ambari-trunk-Commit #3207 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3207/]) AMBARI-12141. Kerberos configs aren't restored when moving back from Review to the Configure Identities step (rzang) (rzang: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=49b47c354fae80b3c0f748d756f439d5553d8e7e) * ambari-web/app/routes/add_kerberos_routes.js * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * ambari-web/test/controllers/main/admin/kerberos/step4_controller_test.js * ambari-web/app/routes/add_service_routes.js * ambari-web/app/utils/config.js Kerberos configs aren't restored when moving back from Review to the Configure Identities step -- Key: AMBARI-12141 URL: https://issues.apache.org/jira/browse/AMBARI-12141 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.2.0, 2.1.1 Attachments: AMBARI-12141.patch, AMBARI-12141_v2.patch, AMBARI-12141_v3.patch * Enable Kerberos on the cluster * Open Add Service Wizard * Proceed to the step Configure Identities * Input Admin principal, Admin password * Click Next * Click Back * Fields Admin principal, Admin password are empty, but should be filed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12141) Kerberos configs aren't restored when moving back from Review to the Configure Identities step
[ https://issues.apache.org/jira/browse/AMBARI-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650144#comment-14650144 ] Hudson commented on AMBARI-12141: - SUCCESS: Integrated in Ambari-branch-2.1 #306 (See [https://builds.apache.org/job/Ambari-branch-2.1/306/]) AMBARI-12141. Kerberos configs aren't restored when moving back from Review to the Configure Identities step (rzang) (rzang: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=1b3f6f781392cba405d56a2669cac64ab51b3494) * ambari-web/app/routes/add_service_routes.js * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js * ambari-web/app/utils/config.js * ambari-web/test/controllers/main/admin/kerberos/step4_controller_test.js * ambari-web/app/routes/add_kerberos_routes.js Kerberos configs aren't restored when moving back from Review to the Configure Identities step -- Key: AMBARI-12141 URL: https://issues.apache.org/jira/browse/AMBARI-12141 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.2.0, 2.1.1 Attachments: AMBARI-12141.patch, AMBARI-12141_v2.patch, AMBARI-12141_v3.patch * Enable Kerberos on the cluster * Open Add Service Wizard * Proceed to the step Configure Identities * Input Admin principal, Admin password * Click Next * Click Back * Fields Admin principal, Admin password are empty, but should be filed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-12613: -- Fix Version/s: (was: 2.1.1) Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2 Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-12613: -- Attachment: AMBARI-12613_trunk_01.patch AMBARI-12613_branch-2.1_01.patch AMBARI-12613_branch-2.0.maint_01.patch Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1, 2.1.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Attachments: AMBARI-12613_branch-2.0.maint_01.patch, AMBARI-12613_branch-2.1_01.patch, AMBARI-12613_trunk_01.patch Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14650034#comment-14650034 ] Hudson commented on AMBARI-12613: - FAILURE: Integrated in Ambari-trunk-Commit #3206 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3206/]) AMBARI-12613. Allow for granular authorization inorder to update User resource properties via Ambari's REST API (rlevas) (rlevas: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=7c1f7a803b18f8384800cc9ca52ac34a42eee18b) * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1, 2.1.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Attachments: AMBARI-12613_branch-2.0.maint_01.patch, AMBARI-12613_branch-2.1_01.patch, AMBARI-12613_trunk_01.patch Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 35866: Kerberos configs aren't restored when moving back from Review to the Configure Identities step
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35866/ --- (Updated July 31, 2015, 11:54 p.m.) Review request for Ambari, Jaimin Jetly and Yusaku Sako. Changes --- Do not overrride configs in Service Configs step onto Configure Identities step. Kerberos related configs will be removed from Service Configs step in future. Bugs: AMBARI-12141 https://issues.apache.org/jira/browse/AMBARI-12141 Repository: ambari Description --- Kerberos configs aren't restored when moving back from Review to the Configure Identities step Diffs (updated) - ambari-web/app/controllers/main/admin/kerberos/step2_controller.js 1ffab0d ambari-web/app/controllers/main/admin/kerberos/step4_controller.js 08f4e10 ambari-web/app/routes/add_kerberos_routes.js e3a40f8 ambari-web/app/routes/add_service_routes.js 262049e ambari-web/app/utils/config.js 11df7ee ambari-web/test/controllers/main/admin/kerberos/step4_controller_test.js af0650c Diff: https://reviews.apache.org/r/35866/diff/ Testing --- Unit test passed. 6419 tests complete (9 seconds) 86 tests pending Thanks, Richard Zang
[jira] [Updated] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-12613: -- Affects Version/s: 2.1.0 Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1, 2.1.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12613) Allow for granular authorization inorder to update User resource properties via Ambari's REST API
[ https://issues.apache.org/jira/browse/AMBARI-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-12613: -- Fix Version/s: 2.1.1 Allow for granular authorization inorder to update User resource properties via Ambari's REST API - Key: AMBARI-12613 URL: https://issues.apache.org/jira/browse/AMBARI-12613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 1.7.0, 2.0.0, 2.0.1, 2.1.0 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.2.0, 2.0.2, 2.1.1 Allow for granular authorization inorder to update User resource properties via Ambari's REST API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
