[jira] [Updated] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[ https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22679: - Attachment: AMBARI-22679.trunk.patch > RU: Service action failed with NullPointer on Downgrade after RU > > > Key: AMBARI-22679 > URL: https://issues.apache.org/jira/browse/AMBARI-22679 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22679.branch-2.6.patch, AMBARI-22679.trunk.patch > > > STR: > - Install Ambari > - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK > - Install HDP 2.6 stack > - Upgrade stack, on finalization initiate downgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22689) Restart agent command sent by server
[ https://issues.apache.org/jira/browse/AMBARI-22689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated AMBARI-22689: - Labels: patch (was: ) Affects Version/s: trunk Status: Patch Available (was: Open) > Restart agent command sent by server > > > Key: AMBARI-22689 > URL: https://issues.apache.org/jira/browse/AMBARI-22689 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Xianghao Lu > Labels: patch > Attachments: AMBARI-22689.patch > > > When ambari agent get a heartbeat response from ambari server, agent will > convert the string data to JSON object, and, response['restartAgent'] will be > a bool value not string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22690) Registering existing hdp version failed with sql exception
[
https://issues.apache.org/jira/browse/AMBARI-22690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22690:
-
Description:
While trying to register existing HDP version below sql exception were noticed.
STR:
- Register HDP version 2.6.4 via manage versions screen of Ambari.
- Try re-registering the same version again. Below exception is thrown.
{code}
ERROR [ambari-client-thread-3696] AmbariJpaLocalTxnInterceptor:180 - [DETAILED
ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key
value violates unique constraint "uq_repo_version_stack_id"
Error Code: 0
Call: INSERT INTO repo_version (repo_version_id, display_name, hidden, legacy,
repositories, resolved, repo_type, version, version_url, version_xml,
version_xsd, parent_id, stack_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [13 parameters bound]
at
org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1620)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
{code}
was:
While trying to register existing HDP version below sql exception were noticed.
Attached is the complete ambari logs.
Register HDP version 2.6.4 via manage versions screen of Ambari.
Try re-registering the same version again. Below exception is thrown.
Looks like the issue is not reproducible everytime and intermittent.
{code}
ERROR [ambari-client-thread-3696] AmbariJpaLocalTxnInterceptor:180 - [DETAILED
ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key
value violates unique constraint "uq_repo_version_stack_id"
Error Code: 0
Call: INSERT INTO repo_version (repo_version_id, display_name, hidden, legacy,
repositories, resolved, repo_type, version, version_url, version_xml,
version_xsd, parent_id, stack_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [13 parameters bound]
at
org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1620)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
{code}
> Registering existing hdp version failed with sql exception
> --
>
> Key: AMBARI-22690
> URL: https://issues.apache.org/jira/browse/AMBARI-22690
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
>
> While trying to register existing HDP version below sql exception were
> noticed.
> STR:
> - Register HDP version 2.6.4 via manage versions screen of Ambari.
> - Try re-registering the same version again. Below exception is thrown.
> {code}
> ERROR [ambari-client-thread-3696] AmbariJpaLocalTxnInterceptor:180 -
> [DETAILED ERROR] Rollback reason:
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key
> value violates unique constraint "uq_repo_version_stack_id"
> Error Code: 0
> Call: INSERT INTO repo_version (repo_version_id, display_name, hidden,
> legacy, repositories, resolved, repo_type,
[jira] [Created] (AMBARI-22690) Registering existing hdp version failed with sql exception
Dmytro Grinenko created AMBARI-22690:
Summary: Registering existing hdp version failed with sql exception
Key: AMBARI-22690
URL: https://issues.apache.org/jira/browse/AMBARI-22690
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Fix For: 2.6.2
While trying to register existing HDP version below sql exception were noticed.
Attached is the complete ambari logs.
Register HDP version 2.6.4 via manage versions screen of Ambari.
Try re-registering the same version again. Below exception is thrown.
Looks like the issue is not reproducible everytime and intermittent.
{code}
ERROR [ambari-client-thread-3696] AmbariJpaLocalTxnInterceptor:180 - [DETAILED
ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key
value violates unique constraint "uq_repo_version_stack_id"
Error Code: 0
Call: INSERT INTO repo_version (repo_version_id, display_name, hidden, legacy,
repositories, resolved, repo_type, version, version_url, version_xml,
version_xsd, parent_id, stack_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [13 parameters bound]
at
org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1620)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[ https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301001#comment-16301001 ] Akhil S Naik commented on AMBARI-22625: --- send for review : https://reviews.apache.org/r/64714/ as review is successfull can you please assign this jira to myself : [~atkach] And commit the issue on my behalf > Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different > --- > > Key: AMBARI-22625 > URL: https://issues.apache.org/jira/browse/AMBARI-22625 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Priority: Minor > Fix For: 2.6.0 > > Attachments: ambari-2.png, namenode.png, release2.5.2.patch, > trunk.patch > > > 'NON DFS Used' value in Services -> HDFS -> Summary if different from the > Value shown in NameNode UI (see Picture). > in NAMENODE UI --> > !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png! > In Services -> HDFS -> Summary > !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png! > In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from > REST API call : > http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo > Where host1 is the Name Node Server FQDN > but in Ambari we are calculating the same value from (Total Allocated - DFS > USed - DFS Remaining) . > due to which this issue is happening. > as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in > NameNode metrics > 'FSNamesystem > CapacityNonDFSUsed' > attached the patch in the JIRA. > Please fix this bug -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[ https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22679: - Attachment: AMBARI-22679.branch-2.6.patch > RU: Service action failed with NullPointer on Downgrade after RU > > > Key: AMBARI-22679 > URL: https://issues.apache.org/jira/browse/AMBARI-22679 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22679.branch-2.6.patch > > > STR: > - Install Ambari > - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK > - Install HDP 2.6 stack > - Upgrade stack, on finalization initiate downgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[ https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22679: - Attachment: (was: AMBARI-22679.patch) > RU: Service action failed with NullPointer on Downgrade after RU > > > Key: AMBARI-22679 > URL: https://issues.apache.org/jira/browse/AMBARI-22679 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22679.branch-2.6.patch > > > STR: > - Install Ambari > - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK > - Install HDP 2.6 stack > - Upgrade stack, on finalization initiate downgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22689) Restart agent command sent by server
[ https://issues.apache.org/jira/browse/AMBARI-22689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated AMBARI-22689: - Description: When ambari agent get a heartbeat response from ambari server, agent will convert the string data to JSON object, and, response['restartAgent'] will be a bool value not string. (was: When ambari agent get a heartbeat response from ambari server, agent will convert the string data to JSON object, so, response['restartAgent'] will be a bool value not string.) > Restart agent command sent by server > > > Key: AMBARI-22689 > URL: https://issues.apache.org/jira/browse/AMBARI-22689 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Xianghao Lu > Attachments: AMBARI-22689.patch > > > When ambari agent get a heartbeat response from ambari server, agent will > convert the string data to JSON object, and, response['restartAgent'] will be > a bool value not string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22689) Restart agent command sent by server
[ https://issues.apache.org/jira/browse/AMBARI-22689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated AMBARI-22689: - Attachment: AMBARI-22689.patch > Restart agent command sent by server > > > Key: AMBARI-22689 > URL: https://issues.apache.org/jira/browse/AMBARI-22689 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Reporter: Xianghao Lu > Attachments: AMBARI-22689.patch > > > When ambari agent get a heartbeat response from ambari server, agent will > convert the string data to JSON object, so, response['restartAgent'] will be > a bool value not string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22689) Restart agent command sent by server
Xianghao Lu created AMBARI-22689: Summary: Restart agent command sent by server Key: AMBARI-22689 URL: https://issues.apache.org/jira/browse/AMBARI-22689 Project: Ambari Issue Type: Bug Components: ambari-agent Reporter: Xianghao Lu When ambari agent get a heartbeat response from ambari server, agent will convert the string data to JSON object, so, response['restartAgent'] will be a bool value not string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
[ https://issues.apache.org/jira/browse/AMBARI-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300862#comment-16300862 ] Hudson commented on AMBARI-22676: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8547 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8547/]) AMBARI-22676. [Patch Hive]webhcat: test_sqoop fails with (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=98356b36b5556735b99248d89b907d957ebef5db]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json > [Patch Hive]webhcat: test_sqoop fails with > hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist > --- > > Key: AMBARI-22676 > URL: https://issues.apache.org/jira/browse/AMBARI-22676 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22676.patch > > > Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets > uploaded on the new version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
[ https://issues.apache.org/jira/browse/AMBARI-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300844#comment-16300844 ] Hudson commented on AMBARI-22676: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #554 (See [https://builds.apache.org/job/Ambari-branch-2.6/554/]) AMBARI-22676. [Patch Hive]webhcat: test_sqoop fails with (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=953e59af1117e88235e24fb8a7649937fd78622a]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json > [Patch Hive]webhcat: test_sqoop fails with > hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist > --- > > Key: AMBARI-22676 > URL: https://issues.apache.org/jira/browse/AMBARI-22676 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22676.patch > > > Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets > uploaded on the new version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22687) Bulk host delete and component add & delete scenarios
[
https://issues.apache.org/jira/browse/AMBARI-22687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300817#comment-16300817
]
Hadoop QA commented on AMBARI-22687:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903321/AMBARI-22687.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12882//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12882//console
This message is automatically generated.
> Bulk host delete and component add & delete scenarios
> -
>
> Key: AMBARI-22687
> URL: https://issues.apache.org/jira/browse/AMBARI-22687
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: 3.0.0
>
> Attachments: AMBARI-22687.patch
>
>
> Implement various scenarios under which Bulk Deletion of Hosts and bulk
> addition and deletion of host components is allowed and display the related
> messages
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22688) Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded
[ https://issues.apache.org/jira/browse/AMBARI-22688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22688: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-3.0-ams > Fix AMS compilation issues and unit test with hbase,hadoop and phoenix > upgraded > --- > > Key: AMBARI-22688 > URL: https://issues.apache.org/jira/browse/AMBARI-22688 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: branch-3.0-ams > > Attachments: AMBARI-22688.patch > > > - Build AMS with HBase 2.0 and fix resulting compilation problems and unit > tests. > - Also removed a bunch of unused code from YARN ATS > - Fix compatibility issues with new HBaseAdmin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22249) Add service group dependencies
[ https://issues.apache.org/jira/browse/AMBARI-22249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22249: --- Attachment: AMBARI-22249_part3.patch > Add service group dependencies > -- > > Key: AMBARI-22249 > URL: https://issues.apache.org/jira/browse/AMBARI-22249 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 3.0.0 > > Attachments: AMBARI-22249.patch, AMBARI-22249_part2.patch, > AMBARI-22249_part3.patch > > > Add table servicegroupdependencies -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22249) Add service group dependencies
[ https://issues.apache.org/jira/browse/AMBARI-22249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22249: --- Attachment: (was: AMBARI-22249_part3.patch) > Add service group dependencies > -- > > Key: AMBARI-22249 > URL: https://issues.apache.org/jira/browse/AMBARI-22249 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 3.0.0 > > Attachments: AMBARI-22249.patch, AMBARI-22249_part2.patch > > > Add table servicegroupdependencies -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300678#comment-16300678 ] Hudson commented on AMBARI-22686: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8546 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8546/]) AMBARI-22686. Disabled stack still appears in the UI if VDF is (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e404100b99ffac8f14e36b46770466deeb5760d7]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java > Disabled stack still appears in the UI if VDF is available > -- > > Key: AMBARI-22686 > URL: https://issues.apache.org/jira/browse/AMBARI-22686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22686.patch > > > Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active > although the stack definition marks this as disabled. > Seems like the UI does not make any calls to check stack active/in-active. > The stacks returned from VDF endpoint are then used to get the repo URLs > because the VDF returns the stack def as sub-resource which included the > in-active stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22687) Bulk host delete and component add & delete scenarios
[ https://issues.apache.org/jira/browse/AMBARI-22687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-22687: - Status: Patch Available (was: Open) > Bulk host delete and component add & delete scenarios > - > > Key: AMBARI-22687 > URL: https://issues.apache.org/jira/browse/AMBARI-22687 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 3.0.0 > > Attachments: AMBARI-22687.patch > > > Implement various scenarios under which Bulk Deletion of Hosts and bulk > addition and deletion of host components is allowed and display the related > messages -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22687) Bulk host delete and component add & delete scenarios
[ https://issues.apache.org/jira/browse/AMBARI-22687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-22687: - Attachment: AMBARI-22687.patch > Bulk host delete and component add & delete scenarios > - > > Key: AMBARI-22687 > URL: https://issues.apache.org/jira/browse/AMBARI-22687 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 3.0.0 > > Attachments: AMBARI-22687.patch > > > Implement various scenarios under which Bulk Deletion of Hosts and bulk > addition and deletion of host components is allowed and display the related > messages -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22688) Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded
[ https://issues.apache.org/jira/browse/AMBARI-22688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22688: - Status: Patch Available (was: Open) > Fix AMS compilation issues and unit test with hbase,hadoop and phoenix > upgraded > --- > > Key: AMBARI-22688 > URL: https://issues.apache.org/jira/browse/AMBARI-22688 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: branch-3.0-ams > > Attachments: AMBARI-22688.patch > > > - Build AMS with HBase 2.0 and fix resulting compilation problems and unit > tests. > - Also removed a bunch of unused code from YARN ATS > - Fix compatibility issues with new HBaseAdmin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22688) Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded
[ https://issues.apache.org/jira/browse/AMBARI-22688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22688: - Attachment: AMBARI-22688.patch > Fix AMS compilation issues and unit test with hbase,hadoop and phoenix > upgraded > --- > > Key: AMBARI-22688 > URL: https://issues.apache.org/jira/browse/AMBARI-22688 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: branch-3.0-ams > > Attachments: AMBARI-22688.patch > > > - Build AMS with HBase 2.0 and fix resulting compilation problems and unit > tests. > - Also removed a bunch of unused code from YARN ATS > - Fix compatibility issues with new HBaseAdmin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22688) Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded
[ https://issues.apache.org/jira/browse/AMBARI-22688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22688: - Fix Version/s: (was: 3.0.0) branch-3.0-ams > Fix AMS compilation issues and unit test with hbase,hadoop and phoenix > upgraded > --- > > Key: AMBARI-22688 > URL: https://issues.apache.org/jira/browse/AMBARI-22688 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: branch-3.0-ams > > > - Build AMS with HBase 2.0 and fix resulting compilation problems and unit > tests. > - Also removed a bunch of unused code from YARN ATS > - Fix compatibility issues with new HBaseAdmin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22688) Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded
Siddharth Wagle created AMBARI-22688: Summary: Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded Key: AMBARI-22688 URL: https://issues.apache.org/jira/browse/AMBARI-22688 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 3.0.0 - Build AMS with HBase 2.0 and fix resulting compilation problems and unit tests. - Also removed a bunch of unused code from YARN ATS - Fix compatibility issues with new HBaseAdmin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22687) Bulk host delete and component add & delete scenarios
Ishan Bhatt created AMBARI-22687: Summary: Bulk host delete and component add & delete scenarios Key: AMBARI-22687 URL: https://issues.apache.org/jira/browse/AMBARI-22687 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 Implement various scenarios under which Bulk Deletion of Hosts and bulk addition and deletion of host components is allowed and display the related messages -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22653) Infra Manager: s3 upload support for archiving Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300601#comment-16300601 ] Hudson commented on AMBARI-22653: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8545 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8545/]) AMBARI-22514, AMBARI-22653. Ambari Infra Manager: solr data exporting (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=36d0271f74a70f5cfeca0e5ca0ebeb795fab6138]) * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/SolrQueryBuilderTest.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/S3Properties.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDocumentIterator.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraManagerStories.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportConfiguration.java * (add) ambari-infra/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentItemReader.java * (edit) ambari-infra/pom.xml * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/ExportJobsSteps.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/OffsetDateTimeConverter.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/LocalDocumentItemWriter.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/S3Uploader.java * (edit) ambari-infra/ambari-infra-manager/docker/Dockerfile * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportJobListener.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportPropertyMap.java * (add) ambari-infra/ambari-infra-manager-it/pom.xml * (edit) ambari-infra/ambari-infra-manager/src/main/resources/infra-manager.properties * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentSource.java * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/DocumentItemReaderTest.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrQueryBuilder.java * (add) ambari-infra/ambari-infra-manager/docker/docker-compose.yml * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/CompositeFileAction.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/ObjectSource.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/Document.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/FileAction.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentIterator.java * (delete) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportStepListener.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrQueryProperties.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDocumentSource.java * (add) ambari-infra/ambari-infra-manager-it/src/test/resources/log4j.properties * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportProperties.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/TarGzCompressor.java * (add) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/DocumentExportPropertiesTest.java * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/LocalDocumentItemWriterTest.java * (add) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/SolrQueryPropertiesTest.java * (add) ambari-infra/ambari-infra-manager/docker/infra-manager-docker-compose.sh * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/AbstractFileAction.java > Infra Manager: s3 upload support for archiving Infra Solr > - > > Key: AMBARI-22653 > URL: https://issues.apache.org/jira/browse/AMBARI-22653 > Project: Ambari >
[jira] [Commented] (AMBARI-22514) Infra Manager: Schedulable document deletion & archiving for Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300600#comment-16300600 ] Hudson commented on AMBARI-22514: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8545 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8545/]) AMBARI-22514, AMBARI-22653. Ambari Infra Manager: solr data exporting (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=36d0271f74a70f5cfeca0e5ca0ebeb795fab6138]) * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/SolrQueryBuilderTest.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/S3Properties.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDocumentIterator.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraManagerStories.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportConfiguration.java * (add) ambari-infra/ambari-infra-manager-it/src/test/resources/stories/infra_api_tests.story * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentItemReader.java * (edit) ambari-infra/pom.xml * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/ExportJobsSteps.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/OffsetDateTimeConverter.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/LocalDocumentItemWriter.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/S3Uploader.java * (edit) ambari-infra/ambari-infra-manager/docker/Dockerfile * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportJobListener.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportPropertyMap.java * (add) ambari-infra/ambari-infra-manager-it/pom.xml * (edit) ambari-infra/ambari-infra-manager/src/main/resources/infra-manager.properties * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentSource.java * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/DocumentItemReaderTest.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/InfraClient.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrQueryBuilder.java * (add) ambari-infra/ambari-infra-manager/docker/docker-compose.yml * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/CompositeFileAction.java * (add) ambari-infra/ambari-infra-manager-it/src/test/java/org/apache/ambari/infra/steps/AbstractInfraSteps.java * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/ObjectSource.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/Document.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/FileAction.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentIterator.java * (delete) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportStepListener.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrQueryProperties.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/SolrDocumentSource.java * (add) ambari-infra/ambari-infra-manager-it/src/test/resources/log4j.properties * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/DocumentExportProperties.java * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/TarGzCompressor.java * (add) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/DocumentExportPropertiesTest.java * (edit) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/LocalDocumentItemWriterTest.java * (add) ambari-infra/ambari-infra-manager/src/test/java/org/apache/ambari/infra/job/archive/SolrQueryPropertiesTest.java * (add) ambari-infra/ambari-infra-manager/docker/infra-manager-docker-compose.sh * (add) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/job/archive/AbstractFileAction.java > Infra Manager: Schedulable document deletion & archiving for Infra Solr > --- > > Key: AMBARI-22514 > URL: https://issues.apache.org/jira/browse/AMBARI-22514 >
[jira] [Commented] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300594#comment-16300594 ] Hudson commented on AMBARI-22686: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #553 (See [https://builds.apache.org/job/Ambari-branch-2.6/553/]) AMBARI-22686. Disabled stack still appears in the UI if VDF is (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e04470dc54c30ab0a637f1bb243a95999cfb5b0a]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java > Disabled stack still appears in the UI if VDF is available > -- > > Key: AMBARI-22686 > URL: https://issues.apache.org/jira/browse/AMBARI-22686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22686.patch > > > Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active > although the stack definition marks this as disabled. > Seems like the UI does not make any calls to check stack active/in-active. > The stacks returned from VDF endpoint are then used to get the repo URLs > because the VDF returns the stack def as sub-resource which included the > in-active stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22686: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.6 and trunk. > Disabled stack still appears in the UI if VDF is available > -- > > Key: AMBARI-22686 > URL: https://issues.apache.org/jira/browse/AMBARI-22686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22686.patch > > > Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active > although the stack definition marks this as disabled. > Seems like the UI does not make any calls to check stack active/in-active. > The stacks returned from VDF endpoint are then used to get the repo URLs > because the VDF returns the stack def as sub-resource which included the > in-active stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22653) Infra Manager: s3 upload support for archiving Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle resolved AMBARI-22653. -- Resolution: Fixed Pushed to trunk. > Infra Manager: s3 upload support for archiving Infra Solr > - > > Key: AMBARI-22653 > URL: https://issues.apache.org/jira/browse/AMBARI-22653 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa > Fix For: 3.0.0 > > > Upload exported document from infa solr to a specified s3 server. > s3 configuration should be defined in a property file and a property should > be added to ambari-infra-manager.properties file for each jobs referencing > the s3 property file. > s3 upload should be optional, If s3 configuration reference presents upload > the files into the specified s3 server and delete them from temporary folder, > if not leave the files in the filesystem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300560#comment-16300560 ] Hudson commented on AMBARI-22680: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8544 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8544/]) AMBARI-22680 Ambari web UI does not fail an invalid repo base URL during (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a15fc7fc1ac70d3399a1b4046c3124dcc8cdbb11]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryResourceProviderTest.java > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[
https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300561#comment-16300561
]
Hadoop QA commented on AMBARI-22686:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903311/AMBARI-22686.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12881//console
This message is automatically generated.
> Disabled stack still appears in the UI if VDF is available
> --
>
> Key: AMBARI-22686
> URL: https://issues.apache.org/jira/browse/AMBARI-22686
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22686.patch
>
>
> Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active
> although the stack definition marks this as disabled.
> Seems like the UI does not make any calls to check stack active/in-active.
> The stacks returned from VDF endpoint are then used to get the repo URLs
> because the VDF returns the stack def as sub-resource which included the
> in-active stack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[ https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22685: --- Status: Patch Available (was: In Progress) > Stack OS/repos removed from cluster installation UI showed up on the Versions > tab after cluster is installed > > > Key: AMBARI-22685 > URL: https://issues.apache.org/jira/browse/AMBARI-22685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22685.patch > > > Even when a user had remove say Diebian , SLES OS/repos from cluster > installation UI after selecting a stack, they still showed up on the Versions > tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[ https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22685: --- Status: In Progress (was: Patch Available) > Stack OS/repos removed from cluster installation UI showed up on the Versions > tab after cluster is installed > > > Key: AMBARI-22685 > URL: https://issues.apache.org/jira/browse/AMBARI-22685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22685.patch > > > Even when a user had remove say Diebian , SLES OS/repos from cluster > installation UI after selecting a stack, they still showed up on the Versions > tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22686: - Status: Patch Available (was: Open) > Disabled stack still appears in the UI if VDF is available > -- > > Key: AMBARI-22686 > URL: https://issues.apache.org/jira/browse/AMBARI-22686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22686.patch > > > Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active > although the stack definition marks this as disabled. > Seems like the UI does not make any calls to check stack active/in-active. > The stacks returned from VDF endpoint are then used to get the repo URLs > because the VDF returns the stack def as sub-resource which included the > in-active stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22686: - Attachment: AMBARI-22686.patch > Disabled stack still appears in the UI if VDF is available > -- > > Key: AMBARI-22686 > URL: https://issues.apache.org/jira/browse/AMBARI-22686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22686.patch > > > Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active > although the stack definition marks this as disabled. > Seems like the UI does not make any calls to check stack active/in-active. > The stacks returned from VDF endpoint are then used to get the repo URLs > because the VDF returns the stack def as sub-resource which included the > in-active stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-22686: - Description: Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active although the stack definition marks this as disabled. Seems like the UI does not make any calls to check stack active/in-active. The stacks returned from VDF endpoint are then used to get the repo URLs because the VDF returns the stack def as sub-resource which included the in-active stack. was:Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active although the stack definition marks this as disabled. > Disabled stack still appears in the UI if VDF is available > -- > > Key: AMBARI-22686 > URL: https://issues.apache.org/jira/browse/AMBARI-22686 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.2 > > > Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active > although the stack definition marks this as disabled. > Seems like the UI does not make any calls to check stack active/in-active. > The stacks returned from VDF endpoint are then used to get the repo URLs > because the VDF returns the stack def as sub-resource which included the > in-active stack. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
Siddharth Wagle created AMBARI-22686: Summary: Disabled stack still appears in the UI if VDF is available Key: AMBARI-22686 URL: https://issues.apache.org/jira/browse/AMBARI-22686 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 2.6.2 Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active although the stack definition marks this as disabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[
https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300550#comment-16300550
]
Hadoop QA commented on AMBARI-22679:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903295/AMBARI-22679.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12880//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12880//console
This message is automatically generated.
> RU: Service action failed with NullPointer on Downgrade after RU
>
>
> Key: AMBARI-22679
> URL: https://issues.apache.org/jira/browse/AMBARI-22679
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.6.2
>
> Attachments: AMBARI-22679.patch
>
>
> STR:
> - Install Ambari
> - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK
> - Install HDP 2.6 stack
> - Upgrade stack, on finalization initiate downgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-20945) Configuration parameter 'hdfs-site' was not found error when AMS rootdir is on s3a
[
https://issues.apache.org/jira/browse/AMBARI-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-20945:
Description:
When I specify AMS rootdir to be on s3a and restart AMS, I would get the
following error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 86, in
AmsCollector().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 315, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 817, in restart
self.start(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 48, in start
self.configure(env, action = 'start') # for security
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 118, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 43, in configure
hbase('master', action)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
line 222, in hbase
dfs_type=params.dfs_type
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 119, in run_action
provider = provider_class(resource)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 503, in __init__
self.assert_parameter_is_set('hdfs_site')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 575, in assert_parameter_is_set
if not getattr(self.resource, parameter_name):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'hdfs-site'
was not found in configurations dictionary!
{code}
was:
When I specify AMS rootdir to be on s3a and restart AMS, I would get the
following error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 86, in
AmsCollector().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 315, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 817, in restart
self.start(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 48, in start
self.configure(env, action = 'start') # for security
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 118, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 43, in configure
hbase('master', action)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
line 222, in hbase
dfs_type=params.dfs_type
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 119, in run_action
provider = provider_class(resource)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 503, in __init__
self.assert_parameter_is_set('hdfs_site')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 575, in assert_parameter_is_set
if not getattr(self.resource, parameter_name):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300542#comment-16300542 ] Di Li commented on AMBARI-22680: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=a15fc7fc1ac70d3399a1b4046c3124dcc8cdbb11 > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22680: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[ https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22685: --- Attachment: (was: AMBARI-22685.patch) > Stack OS/repos removed from cluster installation UI showed up on the Versions > tab after cluster is installed > > > Key: AMBARI-22685 > URL: https://issues.apache.org/jira/browse/AMBARI-22685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22685.patch > > > Even when a user had remove say Diebian , SLES OS/repos from cluster > installation UI after selecting a stack, they still showed up on the Versions > tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[ https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22685: --- Attachment: AMBARI-22685.patch > Stack OS/repos removed from cluster installation UI showed up on the Versions > tab after cluster is installed > > > Key: AMBARI-22685 > URL: https://issues.apache.org/jira/browse/AMBARI-22685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22685.patch > > > Even when a user had remove say Diebian , SLES OS/repos from cluster > installation UI after selecting a stack, they still showed up on the Versions > tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[ https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22685: --- Status: Patch Available (was: Open) > Stack OS/repos removed from cluster installation UI showed up on the Versions > tab after cluster is installed > > > Key: AMBARI-22685 > URL: https://issues.apache.org/jira/browse/AMBARI-22685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22685.patch > > > Even when a user had remove say Diebian , SLES OS/repos from cluster > installation UI after selecting a stack, they still showed up on the Versions > tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
Di Li created AMBARI-22685: -- Summary: Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed Key: AMBARI-22685 URL: https://issues.apache.org/jira/browse/AMBARI-22685 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Di Li Assignee: Di Li Fix For: trunk Even when a user had remove say Diebian , SLES OS/repos from cluster installation UI after selecting a stack, they still showed up on the Versions tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[ https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22685: --- Attachment: AMBARI-22685.patch > Stack OS/repos removed from cluster installation UI showed up on the Versions > tab after cluster is installed > > > Key: AMBARI-22685 > URL: https://issues.apache.org/jira/browse/AMBARI-22685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22685.patch > > > Even when a user had remove say Diebian , SLES OS/repos from cluster > installation UI after selecting a stack, they still showed up on the Versions > tab after cluster was installed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300492#comment-16300492
]
Hudson commented on AMBARI-22306:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8543 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8543/])
AMBARI-22306. Set VersionAdvertised as false for superset in (nishant:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6a37985bcdab81a9c5f48b7275b951662856fa91])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
* (edit)
ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300457#comment-16300457
]
Nishant Bangarwa commented on AMBARI-22306:
---
committed to trunk 6a37985bcdab81a9c5f48b7275b951662856fa91
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300457#comment-16300457
]
Nishant Bangarwa edited comment on AMBARI-22306 at 12/21/17 7:10 PM:
-
committed to trunk
was (Author: nishantbangarwa):
committed to trunk 6a37985bcdab81a9c5f48b7275b951662856fa91
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[ https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22679: - Status: Patch Available (was: In Progress) > RU: Service action failed with NullPointer on Downgrade after RU > > > Key: AMBARI-22679 > URL: https://issues.apache.org/jira/browse/AMBARI-22679 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22679.patch > > > STR: > - Install Ambari > - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK > - Install HDP 2.6 stack > - Upgrade stack, on finalization initiate downgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[ https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-22679: - Attachment: AMBARI-22679.patch > RU: Service action failed with NullPointer on Downgrade after RU > > > Key: AMBARI-22679 > URL: https://issues.apache.org/jira/browse/AMBARI-22679 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22679.patch > > > STR: > - Install Ambari > - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK > - Install HDP 2.6 stack > - Upgrade stack, on finalization initiate downgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22681) Ambari web UI failed to update stack repo directly from the Versions tab.
[
https://issues.apache.org/jira/browse/AMBARI-22681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300352#comment-16300352
]
Di Li commented on AMBARI-22681:
The following error reported by Jenkins is not related to the changes to the
installation logic as HA UI does not touch registering stacks/repos.
21401 passing (37s)
50 pending
1 failing
1) Ambari Web Unit tests
test/controllers/main/admin/highAvailability/nameNode/step3_controller_test
App.HighAvailabilityWizardStep3Controller #renderServiceConfigs selectedService
should be set:
expected
'{"serviceName":"S1","displayName":"s1","configCategories":[{"name":"C1","errorCount":0}],"showConfig":true,"configs":[],"dependentServiceNames":[],"changedConfigProperties":[]}'
to equal
'{"serviceName":"S1","displayName":"s1","configCategories":[{"name":"C1"}],"showConfig":true,"configs":[],"dependentServiceNames":[]}'
+ expected - actual
-{"serviceName":"S1","displayName":"s1","configCategories":[{"name":"C1","errorCount":0}],"showConfig":true,"configs":[],"dependentServiceNames":[],"changedConfigProperties":[]}
+{"serviceName":"S1","displayName":"s1","configCategories":[{"name":"C1"}],"showConfig":true,"configs":[],"dependentServiceNames":[]}
Also, local run of the trunk ambari-web unit tests as well the patch tests run
by Jenkins did not reproduce the error...
Metrics with name "m1-m2" not found to compute expression
Load stack upgrade history
Error loading resource
file:///api/v1/clusters/c1/upgrades?fields=Upgrade&_=1513878095648 (203).
Details: Error opening /api/v1/clusters/c1/upgrades: No such file or directory
Missing translation: dashboard.services.hdfs.clients
21402 passing (32s)
50 pending
JQMIGRATE: jQuery.support.boxModel is deprecated
> Ambari web UI failed to update stack repo directly from the Versions tab.
> -
>
> Key: AMBARI-22681
> URL: https://issues.apache.org/jira/browse/AMBARI-22681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22681.patch
>
>
> REST API calls from the web got rejected by the ambari server with a missing
> property error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22394) Store and retrieve the ambari repo urls for os family during bootstrap
[
https://issues.apache.org/jira/browse/AMBARI-22394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300339#comment-16300339
]
Hadoop QA commented on AMBARI-22394:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903272/AMBARI-22394.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12878//console
This message is automatically generated.
> Store and retrieve the ambari repo urls for os family during bootstrap
> --
>
> Key: AMBARI-22394
> URL: https://issues.apache.org/jira/browse/AMBARI-22394
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server, ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22394.patch
>
>
> ambari configuration will have list of repo urls for each os type
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[
https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300336#comment-16300336
]
Hadoop QA commented on AMBARI-22680:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903099/AMBARI-22680.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12877//console
This message is automatically generated.
> Ambari web UI does not fail an invalid repo base URL during cluster
> installation
>
>
> Key: AMBARI-22680
> URL: https://issues.apache.org/jira/browse/AMBARI-22680
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22680.patch
>
>
> This is because the Ambari server backend never validated anything. It just
> simply sent back HTTP 200 as a dummy response.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22681) Ambari web UI failed to update stack repo directly from the Versions tab.
[ https://issues.apache.org/jira/browse/AMBARI-22681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300316#comment-16300316 ] Hudson commented on AMBARI-22681: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8542 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8542/]) AMBARI-22681 Ambari web UI failed to update stack repo directly from the (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=26bcc97bcb4016948fd28d76943eb9ad23c7a4e6]) * (edit) ambari-web/app/utils/ajax/ajax.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js > Ambari web UI failed to update stack repo directly from the Versions tab. > - > > Key: AMBARI-22681 > URL: https://issues.apache.org/jira/browse/AMBARI-22681 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22681.patch > > > REST API calls from the web got rejected by the ambari server with a missing > property error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22684) Ambari Infra Solr should use DocValues by default
[ https://issues.apache.org/jira/browse/AMBARI-22684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300294#comment-16300294 ] Kevin Risden commented on AMBARI-22684: --- RANGER-1938 is the same issue to fix in the Ranger project. This ticket is to fix this for all Ambari Infra Solr deployments. > Ambari Infra Solr should use DocValues by default > - > > Key: AMBARI-22684 > URL: https://issues.apache.org/jira/browse/AMBARI-22684 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.4.0, 2.5.0, 2.6.0 >Reporter: Kevin Risden > > Ranger uses Ambari Infra Solr (or another Apache Solr install) for storing > Ranger Audit events for displaying in Ranger Admin. In our case, we have > noticed quite a few Ambari Infra Solr OOM due to Ranger. I've talked with a > few other people who are having very similar problems with OOM errors. > I've typed up some details about how the way Ranger is using Solr requires a > lot of heap. I've also outlined the fix for this which significantly reduced > the amount of heap memory required. I'm an Apache Lucene/Solr committer so > this optimization/usage might not be immediately obvious to those using Solr > especially version 5.x. > https://risdenk.github.io/2017/12/18/ambari-infra-solr-ranger.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22684) Ambari Infra Solr should use DocValues by default
Kevin Risden created AMBARI-22684: - Summary: Ambari Infra Solr should use DocValues by default Key: AMBARI-22684 URL: https://issues.apache.org/jira/browse/AMBARI-22684 Project: Ambari Issue Type: Improvement Components: ambari-infra Reporter: Kevin Risden -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22684) Ambari Infra Solr should use DocValues by default
[ https://issues.apache.org/jira/browse/AMBARI-22684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated AMBARI-22684: -- Description: Ranger uses Ambari Infra Solr (or another Apache Solr install) for storing Ranger Audit events for displaying in Ranger Admin. In our case, we have noticed quite a few Ambari Infra Solr OOM due to Ranger. I've talked with a few other people who are having very similar problems with OOM errors. I've typed up some details about how the way Ranger is using Solr requires a lot of heap. I've also outlined the fix for this which significantly reduced the amount of heap memory required. I'm an Apache Lucene/Solr committer so this optimization/usage might not be immediately obvious to those using Solr especially version 5.x. https://risdenk.github.io/2017/12/18/ambari-infra-solr-ranger.html > Ambari Infra Solr should use DocValues by default > - > > Key: AMBARI-22684 > URL: https://issues.apache.org/jira/browse/AMBARI-22684 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.4.0, 2.5.0, 2.6.0 >Reporter: Kevin Risden > > Ranger uses Ambari Infra Solr (or another Apache Solr install) for storing > Ranger Audit events for displaying in Ranger Admin. In our case, we have > noticed quite a few Ambari Infra Solr OOM due to Ranger. I've talked with a > few other people who are having very similar problems with OOM errors. > I've typed up some details about how the way Ranger is using Solr requires a > lot of heap. I've also outlined the fix for this which significantly reduced > the amount of heap memory required. I'm an Apache Lucene/Solr committer so > this optimization/usage might not be immediately obvious to those using Solr > especially version 5.x. > https://risdenk.github.io/2017/12/18/ambari-infra-solr-ranger.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22684) Ambari Infra Solr should use DocValues by default
[ https://issues.apache.org/jira/browse/AMBARI-22684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated AMBARI-22684: -- Affects Version/s: 2.6.0 2.5.0 2.4.0 > Ambari Infra Solr should use DocValues by default > - > > Key: AMBARI-22684 > URL: https://issues.apache.org/jira/browse/AMBARI-22684 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 2.4.0, 2.5.0, 2.6.0 >Reporter: Kevin Risden > > Ranger uses Ambari Infra Solr (or another Apache Solr install) for storing > Ranger Audit events for displaying in Ranger Admin. In our case, we have > noticed quite a few Ambari Infra Solr OOM due to Ranger. I've talked with a > few other people who are having very similar problems with OOM errors. > I've typed up some details about how the way Ranger is using Solr requires a > lot of heap. I've also outlined the fix for this which significantly reduced > the amount of heap memory required. I'm an Apache Lucene/Solr committer so > this optimization/usage might not be immediately obvious to those using Solr > especially version 5.x. > https://risdenk.github.io/2017/12/18/ambari-infra-solr-ranger.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22345) Add service dependencies
[
https://issues.apache.org/jira/browse/AMBARI-22345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-22345:
---
Attachment: AMBARI-22345_part3.patch
> Add service dependencies
>
>
> Key: AMBARI-22345
> URL: https://issues.apache.org/jira/browse/AMBARI-22345
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-22345.patch, AMBARI-22345_part2.patch,
> AMBARI-22345_part3.patch
>
>
> API:
> {code}
> POST
> http://SERVER:8080/api/v2/clusters/{cluster-id}/servicegroups/{sgId}/services
> Request
> {
> "ServiceInfo" : {
> "service_name" : "{service-name}",
> "service_display_name" : "{service-display-name}",
> "service_version" : "{service-version}",
> "stack_id" : "{stack-id}",
> "hosting_platform" : "Ambari|Yarn"
> }
> "dependencies" : [
> {
> "ServiceInfo" : {
> "service_id" : "{dependent-service-id}",
> "cluster_id" : "{dependent-cluster-id}",
> "service_group_id" : "{dependent-service-group-id}",
>}
> }
> ]
> }
> {code}
> DB:
> Add table {{servicedependencies}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22681) Ambari web UI failed to update stack repo directly from the Versions tab.
[ https://issues.apache.org/jira/browse/AMBARI-22681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-22681: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari web UI failed to update stack repo directly from the Versions tab. > - > > Key: AMBARI-22681 > URL: https://issues.apache.org/jira/browse/AMBARI-22681 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22681.patch > > > REST API calls from the web got rejected by the ambari server with a missing > property error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22681) Ambari web UI failed to update stack repo directly from the Versions tab.
[ https://issues.apache.org/jira/browse/AMBARI-22681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300262#comment-16300262 ] Di Li commented on AMBARI-22681: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=26bcc97bcb4016948fd28d76943eb9ad23c7a4e6 > Ambari web UI failed to update stack repo directly from the Versions tab. > - > > Key: AMBARI-22681 > URL: https://issues.apache.org/jira/browse/AMBARI-22681 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22681.patch > > > REST API calls from the web got rejected by the ambari server with a missing > property error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22681) Ambari web UI failed to update stack repo directly from the Versions tab.
[
https://issues.apache.org/jira/browse/AMBARI-22681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300260#comment-16300260
]
Hadoop QA commented on AMBARI-22681:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903103/AMBARI-22681.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12876//console
This message is automatically generated.
> Ambari web UI failed to update stack repo directly from the Versions tab.
> -
>
> Key: AMBARI-22681
> URL: https://issues.apache.org/jira/browse/AMBARI-22681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22681.patch
>
>
> REST API calls from the web got rejected by the ambari server with a missing
> property error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22530) Refactor internal code of handling info between kerberos wizard actions
[ https://issues.apache.org/jira/browse/AMBARI-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300255#comment-16300255 ] Hudson commented on AMBARI-22530: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8541 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8541/]) AMBARI-22530. Refactor internal code of handling info between kerberos (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=67fc4a3785da0a7c39dcb27f220c8573a59ab63d]) * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (delete) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/KerberosPrincipalHostEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostGroupComponentEntityPK.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/ConfigureAmbariIdentitiesServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareKerberosIdentitiesServerAction.java * (edit) ambari-server/src/main/resources/META-INF/persistence.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/ConfigureAmbariIdentitiesServerActionTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/KerberosKeytabServiceMappingEntity.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/KerberosPrincipalHostEntityPK.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/KerberosKeytabDAO.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/kerberos/FinalizeKerberosServerActionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/DestroyPrincipalsServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/PreconfigureKerberosAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/KerberosKeytabEntity.java * (add) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/KerberosKeytabPrincipalEntity.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/CreatePrincipalsServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/stageutils/ResolvedKerberosKeytab.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/PreconfigureKerberosActionTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/orm/db/DDLTests.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/CleanupServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostKerberosIdentityResourceProvider.java * (add) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/KerberosKeytabPrincipalDAO.java * (delete) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/KerberosPrincipalHostDAO.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/HostKerberosIdentityResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/DeleteIdentityHandler.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/CreateKeytabFilesServerAction.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/KerberosPrincipalEntity.java * (add) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/stageutils/KerberosKeytabController.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300225#comment-16300225
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903182/AMBARI-22656.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-agent ambari-server ambari-web:
org.apache.ambari.server.utils.StageUtilsTest
org.apache.ambari.server.controller.KerberosHelperTest
org.apache.ambari.server.serveraction.upgrades.PreconfigureKerberosActionTest
org.apache.ambari.server.orm.db.DDLTests
org.apache.ambari.server.controller.internal.HostResourceProviderTest
The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12875//artifact/patch-work/testrun_ambari-web.txt]
[ambari-agent|https://builds.apache.org/job/Ambari-trunk-test-patch/12875//artifact/patch-work/testrun_ambari-agent.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12875//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22530) Refactor internal code of handling info between kerberos wizard actions
[ https://issues.apache.org/jira/browse/AMBARI-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-22530: --- Attachment: AMBARI-22530.4.patch > Refactor internal code of handling info between kerberos wizard actions > --- > > Key: AMBARI-22530 > URL: https://issues.apache.org/jira/browse/AMBARI-22530 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-22530.4.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22530) Refactor internal code of handling info between kerberos wizard actions
[ https://issues.apache.org/jira/browse/AMBARI-22530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy resolved AMBARI-22530. Resolution: Fixed 81c0454..67fc4a3 trunk -> trunk > Refactor internal code of handling info between kerberos wizard actions > --- > > Key: AMBARI-22530 > URL: https://issues.apache.org/jira/browse/AMBARI-22530 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-22530.4.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22406) UI for verifying if repo exist for new OS family and user prompt for entering HDP and HDP-UTILs repo URLs
[
https://issues.apache.org/jira/browse/AMBARI-22406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300169#comment-16300169
]
Hadoop QA commented on AMBARI-22406:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903226/AMBARI-22406.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12874//console
This message is automatically generated.
> UI for verifying if repo exist for new OS family and user prompt for entering
> HDP and HDP-UTILs repo URLs
> -
>
> Key: AMBARI-22406
> URL: https://issues.apache.org/jira/browse/AMBARI-22406
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22406.patch
>
>
> This will include UI changes in ambari-web to check if the repo is selected
> or provide prompt to the user to enter the HDP and HDP-utils repo URL's.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300148#comment-16300148 ] Hudson commented on AMBARI-22682: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8540 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8540/]) AMBARI-22682 Ambari 3.0 Admin View: Add visual-search box to all pages. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=81c045452e37adc6e68379a125026ac98f8ed103]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/usersList.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/SideNavCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/remoteClusters/list.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js * (add) ambari-admin/src/main/resources/ui/admin-web/test/unit/services/Pagination_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js * (add) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Filters.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/userManagement/UsersListCtrl_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/userManagement/GroupsListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/viewsList.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/directives/comboSearch.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/groupsList.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/index.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/userManagement/UsersListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/directives/comboSearch_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/remoteClusters/RemoteClustersListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Group.js * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/ambariViews/ViewsListCtrl_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/RemoteCluster.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js * (add) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Pagination.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/ambariViews/ViewsListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/User.js * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/userManagement/GroupsListCtrl_test.js * (add) ambari-admin/src/main/resources/ui/admin-web/test/unit/services/Filters_test.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/user-management.css > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22394) Store and retrieve the ambari repo urls for os family during bootstrap
[ https://issues.apache.org/jira/browse/AMBARI-22394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22394: --- Attachment: AMBARI-22394.patch > Store and retrieve the ambari repo urls for os family during bootstrap > -- > > Key: AMBARI-22394 > URL: https://issues.apache.org/jira/browse/AMBARI-22394 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22394.patch > > > ambari configuration will have list of repo urls for each os type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22394) Store and retrieve the ambari repo urls for os family during bootstrap
[ https://issues.apache.org/jira/browse/AMBARI-22394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22394: --- Status: Patch Available (was: In Progress) > Store and retrieve the ambari repo urls for os family during bootstrap > -- > > Key: AMBARI-22394 > URL: https://issues.apache.org/jira/browse/AMBARI-22394 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server, ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22394.patch > > > ambari configuration will have list of repo urls for each os type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22404) Set java.home. in ambari-server setup script for server OS family
[
https://issues.apache.org/jira/browse/AMBARI-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300133#comment-16300133
]
Hadoop QA commented on AMBARI-22404:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903227/AMBARI-22404.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12873//console
This message is automatically generated.
> Set java.home. in ambari-server setup script for server OS family
>
>
> Key: AMBARI-22404
> URL: https://issues.apache.org/jira/browse/AMBARI-22404
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22404.patch
>
>
> Changes to ambari-server setup script for accepting user values for java_home
> for OS type.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[
https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300130#comment-16300130
]
Hadoop QA commented on AMBARI-22680:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903099/AMBARI-22680.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12872//console
This message is automatically generated.
> Ambari web UI does not fail an invalid repo base URL during cluster
> installation
>
>
> Key: AMBARI-22680
> URL: https://issues.apache.org/jira/browse/AMBARI-22680
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22680.patch
>
>
> This is because the Ambari server backend never validated anything. It just
> simply sent back HTTP 200 as a dummy response.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22682: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300100#comment-16300100 ] Andrii Tkach commented on AMBARI-22682: --- committed to trunk > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300076#comment-16300076 ] Aleksandr Kovalenko commented on AMBARI-22682: -- +1 for the patch > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[
https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300069#comment-16300069
]
Hadoop QA commented on AMBARI-22682:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903236/AMBARI-22682.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12871//console
This message is automatically generated.
> Ambari 3.0 Admin View: Add visual-search box to all pages
> -
>
> Key: AMBARI-22682
> URL: https://issues.apache.org/jira/browse/AMBARI-22682
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22682.patch
>
>
> Add visual-search box to Users, Groups, Remote Clusters and Versions page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22683) Custom username setting is not propagated
Raffaele Saggino created AMBARI-22683: - Summary: Custom username setting is not propagated Key: AMBARI-22683 URL: https://issues.apache.org/jira/browse/AMBARI-22683 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.5.2, 2.6.0 Environment: HDF 3.0.2.0 Reporter: Raffaele Saggino Priority: Critical Hello, I am using Ambari to install registry on a HDF platform. I customized "registry" username to a different one in the "Misc." settings, this setting leads to a fail during the installation process. My current workaround is to manually edit the file "/etc/registry/conf/registry-env.sh" and add: export REGISTRY_USER= new_registry_name P.S. This happens also while installing the streamline component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22682: -- Attachment: AMBARI-22682.patch > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22682: -- Attachment: (was: AMBARI-22682.patch) > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1635#comment-1635 ] Andrii Tkach commented on AMBARI-22682: --- PhantomJS 1.9.8 (Linux): Executed 57 of 57 SUCCESS (0.348 secs / 0.344 secs) > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22682: -- Status: Patch Available (was: Open) > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[ https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22682: -- Attachment: AMBARI-22682.patch > Ambari 3.0 Admin View: Add visual-search box to all pages > - > > Key: AMBARI-22682 > URL: https://issues.apache.org/jira/browse/AMBARI-22682 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22682.patch > > > Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
Andrii Tkach created AMBARI-22682: - Summary: Ambari 3.0 Admin View: Add visual-search box to all pages Key: AMBARI-22682 URL: https://issues.apache.org/jira/browse/AMBARI-22682 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Add visual-search box to Users, Groups, Remote Clusters and Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22404) Set java.home. in ambari-server setup script for server OS family
[ https://issues.apache.org/jira/browse/AMBARI-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22404: --- Attachment: AMBARI-22404.patch > Set java.home. in ambari-server setup script for server OS family > > > Key: AMBARI-22404 > URL: https://issues.apache.org/jira/browse/AMBARI-22404 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22404.patch > > > Changes to ambari-server setup script for accepting user values for java_home > for OS type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22404) Set java.home. in ambari-server setup script for server OS family
[ https://issues.apache.org/jira/browse/AMBARI-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22404: --- Attachment: (was: AMBARI-22404.patch) > Set java.home. in ambari-server setup script for server OS family > > > Key: AMBARI-22404 > URL: https://issues.apache.org/jira/browse/AMBARI-22404 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22404.patch > > > Changes to ambari-server setup script for accepting user values for java_home > for OS type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22404) Set java.home. in ambari-server setup script for server OS family
[ https://issues.apache.org/jira/browse/AMBARI-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22404: --- Attachment: (was: AMBARI-22404_branch-feature-AMBARI-21674_01.patch) > Set java.home. in ambari-server setup script for server OS family > > > Key: AMBARI-22404 > URL: https://issues.apache.org/jira/browse/AMBARI-22404 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22404.patch > > > Changes to ambari-server setup script for accepting user values for java_home > for OS type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22406) UI for verifying if repo exist for new OS family and user prompt for entering HDP and HDP-UTILs repo URLs
[ https://issues.apache.org/jira/browse/AMBARI-22406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22406: --- Status: Patch Available (was: In Progress) > UI for verifying if repo exist for new OS family and user prompt for entering > HDP and HDP-UTILs repo URLs > - > > Key: AMBARI-22406 > URL: https://issues.apache.org/jira/browse/AMBARI-22406 > Project: Ambari > Issue Type: Sub-task > Components: ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22406.patch > > > This will include UI changes in ambari-web to check if the repo is selected > or provide prompt to the user to enter the HDP and HDP-utils repo URL's. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22406) UI for verifying if repo exist for new OS family and user prompt for entering HDP and HDP-UTILs repo URLs
[ https://issues.apache.org/jira/browse/AMBARI-22406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated AMBARI-22406: --- Attachment: AMBARI-22406.patch > UI for verifying if repo exist for new OS family and user prompt for entering > HDP and HDP-UTILs repo URLs > - > > Key: AMBARI-22406 > URL: https://issues.apache.org/jira/browse/AMBARI-22406 > Project: Ambari > Issue Type: Sub-task > Components: ambari-web >Reporter: Yussuf Shaikh >Assignee: Yussuf Shaikh > Attachments: AMBARI-22406.patch > > > This will include UI changes in ambari-web to check if the repo is selected > or provide prompt to the user to enter the HDP and HDP-utils repo URL's. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22512) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/AMBARI-22512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299872#comment-16299872 ] Sebb commented on AMBARI-22512: --- There are now 5 releases on the ASF mirror system. Please remove all but the current one. It's not fair to expect 3rd party mirrors to carry all the old releases. > Please delete old releases from mirroring system > > > Key: AMBARI-22512 > URL: https://issues.apache.org/jira/browse/AMBARI-22512 > Project: Ambari > Issue Type: Bug >Reporter: Sebb > > The ASF relies on volunteers to provide its mirror download service, so it is > important that only current releases served via the ASF mirror system. Older > releases should be archived. > Please can you remove all non-current releases? > It's unfair to expect the 3rd party mirrors to carry old releases. > Note that older releases can still be linked from the download page, but such > links should use the archive server at: > https://archive.apache.org/dist/ambari/ > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22512) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/AMBARI-22512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated AMBARI-22512: -- Description: The ASF relies on volunteers to provide its mirror download service, so it is important that only current releases served via the ASF mirror system. Older releases should be archived. Please can you remove all non-current releases? It's unfair to expect the 3rd party mirrors to carry old releases. Note that older releases can still be linked from the download page, but such links should use the archive server at: https://archive.apache.org/dist/ambari/ Thanks! [1] http://www.apache.org/dev/release.html#when-to-archive was: The ASF relies on volunteers to provide its mirror download service, so it is important that only current releases served via the ASF mirror system. Older releases should be archived. Please can you remove all non-current releases? It's unfair to expect the 3rd party mirrors to carry old releases. Note that older releases can still be linked from the download page, but such links should use the archive server at: https://archive.apache.org/dist/incubator/mxnet/ Thanks! [1] http://www.apache.org/dev/release.html#when-to-archive > Please delete old releases from mirroring system > > > Key: AMBARI-22512 > URL: https://issues.apache.org/jira/browse/AMBARI-22512 > Project: Ambari > Issue Type: Bug >Reporter: Sebb > > The ASF relies on volunteers to provide its mirror download service, so it is > important that only current releases served via the ASF mirror system. Older > releases should be archived. > Please can you remove all non-current releases? > It's unfair to expect the 3rd party mirrors to carry old releases. > Note that older releases can still be linked from the download page, but such > links should use the archive server at: > https://archive.apache.org/dist/ambari/ > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: AMBARI-22656.patch > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
