[jira] [Resolved] (AMBARI-24344) Upgrade Infra Solr client operation fails for Ubuntu while running migration script for solr upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jasmeen Kaur resolved AMBARI-24344.
---
Resolution: Fixed
> Upgrade Infra Solr client operation fails for Ubuntu while running migration
> script for solr upgrade
>
>
> Key: AMBARI-24344
> URL: https://issues.apache.org/jira/browse/AMBARI-24344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Jasmeen Kaur
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> While running the infra solr upgrade helper script (see command below) on
> Ubuntu cluster , The upgrade infra solr clients operation fails with error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 60, in
> InfraSolrClient().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 56, in upgrade_solr_client
> pkg_provider.remove_package('ambari-infra-solr-client', context,
> ignore_dependencies=True)
> TypeError: wrapper() got an unexpected keyword argument 'ignore_dependencies'
> {code}
> Command -
> {code:java}
> /usr/lib/ambari-infra-solr-client/ambariSolrMigration.sh --ini-file
> --mode backup | tee backup_output.txt
> {code}
> The script works fine on Centos7 though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24335) Update service metainfo to declare Kerberos is required for SSO integration support
[
https://issues.apache.org/jira/browse/AMBARI-24335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556379#comment-16556379
]
Hudson commented on AMBARI-24335:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9682 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9682/])
AMBARI-24335. Updating service metainfo to declare if Kerberos is (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=0b7e8d0b0c9fc0e24e21a8de61ea1eb6e682092f])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceResponse.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/SingleSignOnInfo.java
> Update service metainfo to declare Kerberos is required for SSO integration
> support
> ---
>
> Key: AMBARI-24335
> URL: https://issues.apache.org/jira/browse/AMBARI-24335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Update service metainfo to declare Kerberos is required for SSO integration
> support.
> The metainfo file allow for a service to indicate that is supports SSO
> integration.
> {code:java|title=Example}
>
> true
>
> service-site/knox.sso.enabled
>
> {code}
> However, some services required that Kerberos is enabled to support SSO. This
> needs to be indicated in the metainfo so that Ambari knows how to behave
> properly.
> {code:java|title=Example}
>
> true
>
> service-site/knox.sso.enabled
> true
>
> {code}
> Along with this change, the following API request needs to be updated to
> supply the relevant data:
> {noformat:title=Get stack service details}
> GET /api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME",
> {
> "href" : ":URL",
> "StackServices" : {
> ...
> "sso_integration_supported": "true",
> "sso_integration_requires_kerberos": "true",
> ...
> },
> ...
> {noformat}
> {noformat:title=Get installed service information}
> GET /api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME
> {
> "href" : ":URL",
> "ServiceInfo" : {
> "cluster_name" : ":CLUSTER_NAME",
> ...
> "sso_integration_supported": "true",
> "sso_integration_requires_kerberos": "true",
> "sso_integration_enabled": "false",
> "sso_integration_desired": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=List installed services that support SSO integration only
> when Kerberos to be enabled}
> GET
> /api/v1/clusters/:CLUSTER_NAME/services?ServiceInfo/sso_integration_supported=true/sso_integration_requires_kerberos=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
> {noformat:title=List stack services that support SSO integration only when
> Kerberos is enabed}
> GET
> /api/v1/stacks/:STACK_NAME/versions/:VERSION/services?StackServices/sso_integration_supported=true/sso_integration_requires_kerberos=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24304) convert hive table upgrade step fails with hive db priv issue
[ https://issues.apache.org/jira/browse/AMBARI-24304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556814#comment-16556814 ] Hudson commented on AMBARI-24304: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #75 (See [https://builds.apache.org/job/Ambari-branch-2.7/75/]) AMBARI-24304 Fix convert table classpath (asutosh) (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=492e93314e9b83d5d68d10fdc5758a6edbd48ca8]) * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/pre_upgrade.py > convert hive table upgrade step fails with hive db priv issue > - > > Key: AMBARI-24304 > URL: https://issues.apache.org/jira/browse/AMBARI-24304 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > convert hive table step fails due to improper classpath, hadoop-hdfs should > be added, and conf/conf.server should be used -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24276) Upgrade failed at ConvertTable, container mode, with data deployed
[
https://issues.apache.org/jira/browse/AMBARI-24276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556815#comment-16556815
]
Hudson commented on AMBARI-24276:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #75 (See
[https://builds.apache.org/job/Ambari-branch-2.7/75/])
AMBARI-24276 include derby jars for Hive convert table step (ashutosh)
(ishanbhatt.1989:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9fb4764c1d265a535174903fe9fe9dcda9b32ddc])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/pre_upgrade.py
> Upgrade failed at ConvertTable, container mode, with data deployed
> --
>
> Key: AMBARI-24276
> URL: https://issues.apache.org/jira/browse/AMBARI-24276
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Ishan Bhatt
>Assignee: Miklos Gergely
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Upgrade failed for cluster where pre-upgrade data deploy was done, container
> mode.
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError: Could not
> initialize class org.apache.derby.jdbc.AutoloadedDriver40
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at java.sql.DriverManager.isDriverAllowed(DriverManager.java:556)
> at java.sql.DriverManager.getConnection(DriverManager.java:661)
> at java.sql.DriverManager.getConnection(DriverManager.java:247)
> at com.jolbox.bonecp.BoneCP.obtainRawInternalConnection(BoneCP.java:351)
> at com.jolbox.bonecp.BoneCP.(BoneCP.java:416)
> at
> com.jolbox.bonecp.BoneCPDataSource.getConnection(BoneCPDataSource.java:120)
> at
> org.apache.hadoop.hive.metastore.txn.TxnHandler.getDbConn(TxnHandler.java:1935)
> at
> org.apache.hadoop.hive.metastore.txn.TxnHandler.getDbConn(TxnHandler.java:1928)
> at
> org.apache.hadoop.hive.metastore.txn.TxnHandler.setConf(TxnHandler.java:270)
> at
> org.apache.hadoop.hive.metastore.txn.TxnUtils.getTxnStore(TxnUtils.java:115)
> at
> org.apache.hadoop.hive.upgrade.acid.PreUpgradeTool.prepareAcidUpgradeInternal(PreUpgradeTool.java:229)
> at
> org.apache.hadoop.hive.upgrade.acid.PreUpgradeTool.main(PreUpgradeTool.java:148)
> Command failed after 1 tries{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24333) User is able to set the same short URLs for different view instances
[
https://issues.apache.org/jira/browse/AMBARI-24333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar resolved AMBARI-24333.
Resolution: Fixed
> User is able to set the same short URLs for different view instances
>
>
> Key: AMBARI-24333
> URL: https://issues.apache.org/jira/browse/AMBARI-24333
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Let's say the user has CAPACITY-SCHEDULER view instance with
> {{/main/view/CAPACITY-SCHEDULER/auto_cs_instance}} short URL set
> # Clone this instance or create another CAPACITY-SCHEDULER instance manually
> # Set the same short URL as for the first instance
> *Result*
> - If 'Name' property is the same, request for adding new URL fails
> request:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response:
> {noformat}
> {
> "status" : 500,
> "message" : "An internal system exception occurred: This view URL name
> exists, URL names should be unique"
> }
> {noformat}
> - If name is different, the REST call succeeds even if URL itself is
> duplicate:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance1
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance1",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response is 201 in this case; URL is created
> - As result there are two view instances with the same URL, and the first
> one is no longer accessible by this URL
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24320) SET_KEYTABS is preformed twice per host during Kerberos operations
[
https://issues.apache.org/jira/browse/AMBARI-24320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar resolved AMBARI-24320.
Resolution: Fixed
> SET_KEYTABS is preformed twice per host during Kerberos operations
> --
>
> Key: AMBARI-24320
> URL: https://issues.apache.org/jira/browse/AMBARI-24320
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> *STR*
> * Enable Kerberos and check the DB after the 'Test Kerberos' step, or
> * Regenerate keytabs on a secure cluster with the option 'Only regenerate
> keytabs for missing hosts and components' enabled (this is important,
> otherwise the issue is not reproducible)
> *Result:*
> {noformat}
> SELECT hrc.task_id, hrc.request_id, hrc.host_id, hrc.stage_id,
> st.request_context, hrc.status, hrc.role, hrc.role_command,
> hrc.custom_command_name FROM host_role_command hrc, stage st WHERE
> hrc.stage_id = st.stage_id AND hrc.request_id = st.request_id AND
> hrc.custom_command_name = 'SET_KEYTAB' ORDER BY request_id, host_id,
> stage_id;{noformat}
> ||task_id||request_id||host_id||stage_id||request_context||status||role||role_command||custom_command_name||
> |63|17|1|1|Checking
> keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |68|17|1|4|Distribute
> Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |64|17|2|1|Checking
> keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |69|17|2|4|Distribute
> Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |65|17|3|1|Checking
> keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |70|17|3|4|Distribute
> Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |83|19|1|1|Checking
> keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |88|19|1|4|Distribute
> Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |84|19|2|1|Checking
> keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |89|19|2|4|Distribute
> Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |85|19|3|1|Checking
> keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |90|19|3|4|Distribute
> Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> *Expected result:*
> only one SET_KEYTAB command should be recorded
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24351) Logic and declaration used to determine if SSO is enabled for a service needs to be able to handle more than a boolean property
Sandor Molnar created AMBARI-24351:
--
Summary: Logic and declaration used to determine if SSO is enabled
for a service needs to be able to handle more than a boolean property
Key: AMBARI-24351
URL: https://issues.apache.org/jira/browse/AMBARI-24351
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.1
Logic and declaration used to determine if SSO is enabled for a service needs
to be able to handle more than a boolean property.
The current way Ambari determines whether SSO is enabled for a service or not
is by getting the value of the property indicated in
{{sso/enabledConfiguration}} property in the service's metadata:
{code:java|title=Example}
true
service-properties/sso.knox.enabled
{code}
Using the above example, the {{service-properties/sso.knox.enabled}} is checked
to see if its value is "true" or "false".
This method works for a few services, but other services require more elaborate
checks. For example Oozie relies on the value of
{{oozie-site/oozie.authentication.type}}. If the value is
"org.apache.hadoop.security.authentication.server.JWTRedirectAuthenticationHandler",
then SSO is enabled; otherwise it is not. This is different that just a
Boolean value.
*Solution*
To support a more robust method to determine whether SSO is enabled or not, a
new attribute should be added - {{ssoEnabledTest}}. The existing attribute,
{{enabledConfiguration}}, should be available for backward compatibility - but
converted on the backend.
The {{ssoEnabledTest}} attribute is to contain a JSON document that can be
_compiled_ into a {{org.apache.commons.collections.Predicate}} (ideally using
{{org.apache.ambari.server.collections.PredicateUtils#fromJSON}}). For example
{code:java}
true
{
"equals": [
"service-properties/sso.knox.enabled",
"true"
]
}
{code}
{code:java}
true
{
"equals": [
"oozie-site/oozie.authentication.type",
"org.apache.hadoop.security.authentication.server.JWTRedirectAuthenticationHandler"
]
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24332) PERF 1.0 package not installed in the cluster at deploy time
[ https://issues.apache.org/jira/browse/AMBARI-24332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555217#comment-16555217 ] Hudson commented on AMBARI-24332: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #68 (See [https://builds.apache.org/job/Ambari-branch-2.7/68/]) AMBARI-24332 - PERF 1.0 package not installed in the cluster at deploy (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=c26bd81eb516e6fecbfeddeea2899e18da0dae98]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-INSTALL/scripts/distro-select.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/hooks/before-INSTALL/scripts/hook.py > PERF 1.0 package not installed in the cluster at deploy time > > > Key: AMBARI-24332 > URL: https://issues.apache.org/jira/browse/AMBARI-24332 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0, 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24344) Upgrade Infra Solr client operation fails for Ubuntu while running migration script for solr upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jasmeen Kaur updated AMBARI-24344:
--
Fix Version/s: 2.7.1
> Upgrade Infra Solr client operation fails for Ubuntu while running migration
> script for solr upgrade
>
>
> Key: AMBARI-24344
> URL: https://issues.apache.org/jira/browse/AMBARI-24344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Jasmeen Kaur
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> While running the infra solr upgrade helper script (see command below) on
> Ubuntu cluster , The upgrade infra solr clients operation fails with error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 60, in
> InfraSolrClient().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 56, in upgrade_solr_client
> pkg_provider.remove_package('ambari-infra-solr-client', context,
> ignore_dependencies=True)
> TypeError: wrapper() got an unexpected keyword argument 'ignore_dependencies'
> {code}
> Command -
> {code:java}
> /usr/lib/ambari-infra-solr-client/ambariSolrMigration.sh --ini-file
> --mode backup | tee backup_output.txt
> {code}
> The script works fine on Centos7 though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
Mugdha Varadkar created AMBARI-24352:
Summary: Updating Ranger and Ranger KMS configs during Ambari
upgrade
Key: AMBARI-24352
URL: https://issues.apache.org/jira/browse/AMBARI-24352
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.7.1
*For Ranger*
Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
directory configs in stack.
*For Ranger KMS*
Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
Test Connection button for verify communication to selected database using
database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Affects Version/s: 2.70
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.7.1
>
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24289) Log Feeder: use Log Feeder in client mode only (index selected files then stop)
[ https://issues.apache.org/jira/browse/AMBARI-24289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó reassigned AMBARI-24289: - Assignee: Krisztian Kasa (was: Olivér Szabó) > Log Feeder: use Log Feeder in client mode only (index selected files then > stop) > --- > > Key: AMBARI-24289 > URL: https://issues.apache.org/jira/browse/AMBARI-24289 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Krisztian Kasa >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24353) Log Feeder: generate solr id from specific fields
Olivér Szabó created AMBARI-24353: - Summary: Log Feeder: generate solr id from specific fields Key: AMBARI-24353 URL: https://issues.apache.org/jira/browse/AMBARI-24353 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24312) [LogSearch UI] Audit screen sub tab changes clear the Summary charts.
[ https://issues.apache.org/jira/browse/AMBARI-24312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24312: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [LogSearch UI] Audit screen sub tab changes clear the Summary charts. > - > > Key: AMBARI-24312 > URL: https://issues.apache.org/jira/browse/AMBARI-24312 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 25h 20m > Remaining Estimate: 0h > > * Select 'Audit logs' tab > * Change from Summary sub tab to Logs sub tab > * Change back to Summary sub tab > * The charts disappear > The charts should be visible when the user selects the Summary tab any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24260) Ambari shows success when Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk reassigned AMBARI-24260: - Assignee: Andrii Babiichuk (was: Dmytro Sen) > Ambari shows success when Decommission/Recommission operations fail > --- > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > Ambari shows success when Decommission/Recommission operations fail > If Decommission/Recommission operation fails with non zero exit code, that > component still gets decommissioned/recommissioned. We need to handle this > failure and not transition the state to Decommissioned/Recommissioned when > the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24260) Ambari shows success when HBase Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24260: -- Description: If HBase Decommission/Recommission operation fails with non zero exit code, that component still gets decommissioned/recommissioned. We need to handle this failure and not transition the state to Decommissioned/Recommissioned when the respective operation fails (was: Ambari shows success when Decommission/Recommission operations fail If Decommission/Recommission operation fails with non zero exit code, that component still gets decommissioned/recommissioned. We need to handle this failure and not transition the state to Decommissioned/Recommissioned when the respective operation fails) > Ambari shows success when HBase Decommission/Recommission operations fail > - > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > If HBase Decommission/Recommission operation fails with non zero exit code, > that component still gets decommissioned/recommissioned. We need to handle > this failure and not transition the state to Decommissioned/Recommissioned > when the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24260) Ambari shows success when HBase Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24260: -- Status: Patch Available (was: In Progress) > Ambari shows success when HBase Decommission/Recommission operations fail > - > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 50m > Remaining Estimate: 0h > > If HBase Decommission/Recommission operation fails with non zero exit code, > that component still gets decommissioned/recommissioned. We need to handle > this failure and not transition the state to Decommissioned/Recommissioned > when the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24354) [Log Search UI] wrong filter label on open log tab
Istvan Tobias created AMBARI-24354: -- Summary: [Log Search UI] wrong filter label on open log tab Key: AMBARI-24354 URL: https://issues.apache.org/jira/browse/AMBARI-24354 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Fix For: 2.7.1 Steps to reproduce: - Set date (Like Today) on filter tab - go to the logs table and click on open log tab - on the new tab, the date filer shows a NaN value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24354) [Log Search UI] wrong filter label on open log tab
[ https://issues.apache.org/jira/browse/AMBARI-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24354: --- Status: Patch Available (was: In Progress) > [Log Search UI] wrong filter label on open log tab > -- > > Key: AMBARI-24354 > URL: https://issues.apache.org/jira/browse/AMBARI-24354 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 10m > Remaining Estimate: 23h 50m > > Steps to reproduce: > - Set date (Like Today) on filter tab > - go to the logs table and click on open log tab > - on the new tab, the date filer shows a NaN value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24338) [Log Search UI] Add application routing information to README.md
[ https://issues.apache.org/jira/browse/AMBARI-24338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24338: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] Add application routing information to README.md > > > Key: AMBARI-24338 > URL: https://issues.apache.org/jira/browse/AMBARI-24338 > Project: Ambari > Issue Type: Documentation > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 1.5h > Remaining Estimate: 22.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23075) Log Search: Zookeeper tick time is too low for Config API
[ https://issues.apache.org/jira/browse/AMBARI-23075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23075. --- Resolution: Won't Fix > Log Search: Zookeeper tick time is too low for Config API > - > > Key: AMBARI-23075 > URL: https://issues.apache.org/jira/browse/AMBARI-23075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24325) [Log Search UI] Unaccessible query filter type ahead element in small window
[ https://issues.apache.org/jira/browse/AMBARI-24325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias resolved AMBARI-24325. Resolution: Fixed > [Log Search UI] Unaccessible query filter type ahead element in small window > > > Key: AMBARI-24325 > URL: https://issues.apache.org/jira/browse/AMBARI-24325 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 12h > Time Spent: 1h 20m > Remaining Estimate: 10h 40m > > * Click into the query filter bar input field > * A type ahead dropdown will appear > * When the user's screen is small the bottom of the dropdown is not visible > Expected behaviour: All the dropdown element should be available for > selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24356) Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor
Rohith Sharma K S created AMBARI-24356: -- Summary: Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor Key: AMBARI-24356 URL: https://issues.apache.org/jira/browse/AMBARI-24356 Project: Ambari Issue Type: Bug Reporter: Rohith Sharma K S Timeline_Reader is new daemon added in Hadoop-3 on-wards. This component information need to be added in BlueprintConfigurationProcessor cc:/ [~jluniya] [~jonathan.hurley] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24356) Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor
[ https://issues.apache.org/jira/browse/AMBARI-24356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated AMBARI-24356: --- Status: Patch Available (was: Open) > Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor > --- > > Key: AMBARI-24356 > URL: https://issues.apache.org/jira/browse/AMBARI-24356 > Project: Ambari > Issue Type: Bug >Reporter: Rohith Sharma K S >Priority: Major > Attachments: AMBARI-24356.01.patch > > > Timeline_Reader is new daemon added in Hadoop-3 on-wards. This component > information need to be added in BlueprintConfigurationProcessor > cc:/ [~jluniya] [~jonathan.hurley] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24356) Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor
[ https://issues.apache.org/jira/browse/AMBARI-24356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated AMBARI-24356: --- Affects Version/s: 2.7.0 trunk > Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor > --- > > Key: AMBARI-24356 > URL: https://issues.apache.org/jira/browse/AMBARI-24356 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.7.0 >Reporter: Rohith Sharma K S >Priority: Major > Attachments: AMBARI-24356.01.patch > > > Timeline_Reader is new daemon added in Hadoop-3 on-wards. This component > information need to be added in BlueprintConfigurationProcessor > cc:/ [~jluniya] [~jonathan.hurley] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Attachment: AMBARI-24352.patch
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352.patch
>
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24333) User is able to set the same short URLs for different view instances
[
https://issues.apache.org/jira/browse/AMBARI-24333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555642#comment-16555642
]
Hudson commented on AMBARI-24333:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #71 (See
[https://builds.apache.org/job/Ambari-branch-2.7/71/])
AMBARI-24333. Raising an error when user is trying to create a view URL
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1a67af59eb948f0d3c129a3691084806a132a803])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewURLResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ViewURLDAO.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewURLResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewURLEntity.java
> User is able to set the same short URLs for different view instances
>
>
> Key: AMBARI-24333
> URL: https://issues.apache.org/jira/browse/AMBARI-24333
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Let's say the user has CAPACITY-SCHEDULER view instance with
> {{/main/view/CAPACITY-SCHEDULER/auto_cs_instance}} short URL set
> # Clone this instance or create another CAPACITY-SCHEDULER instance manually
> # Set the same short URL as for the first instance
> *Result*
> - If 'Name' property is the same, request for adding new URL fails
> request:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response:
> {noformat}
> {
> "status" : 500,
> "message" : "An internal system exception occurred: This view URL name
> exists, URL names should be unique"
> }
> {noformat}
> - If name is different, the REST call succeeds even if URL itself is
> duplicate:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance1
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance1",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response is 201 in this case; URL is created
> - As result there are two view instances with the same URL, and the first
> one is no longer accessible by this URL
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24319) Multiple alerts after HDFS service only regenerate keytabs, as keytabs are out of sync
[ https://issues.apache.org/jira/browse/AMBARI-24319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555643#comment-16555643 ] Hudson commented on AMBARI-24319: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #71 (See [https://builds.apache.org/job/Ambari-branch-2.7/71/]) AMBARI-24319. Regenerating keytabs for the given service(s) only (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ee68d7cf49a50942cfc7685a5d3219a046da1157]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java > Multiple alerts after HDFS service only regenerate keytabs, as keytabs are > out of sync > -- > > Key: AMBARI-24319 > URL: https://issues.apache.org/jira/browse/AMBARI-24319 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > *STR* > # Install Ambari 2.7.0 > # Deploy a cluster with some services > # Execute to HDFS / Actions / Regenerate Keytabs > # Restart all required components > *Result* > Multiple alerts have been shown saying they receive 403 when trying to > connect to different web UIs > *Expected result* > No alerts; everything should work as expected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24352:
Labels: pull-request-available (was: )
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352.patch
>
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24260) Ambari shows success when HBase Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24260: -- Summary: Ambari shows success when HBase Decommission/Recommission operations fail (was: Ambari shows success when Decommission/Recommission operations fail) > Ambari shows success when HBase Decommission/Recommission operations fail > - > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > Ambari shows success when Decommission/Recommission operations fail > If Decommission/Recommission operation fails with non zero exit code, that > component still gets decommissioned/recommissioned. We need to handle this > failure and not transition the state to Decommissioned/Recommissioned when > the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24353:
--
Description:
usage (in output.json configs)
{code:json}
{
outputs: [
{
"id_fields" : [
"log_message", "logtime", "type", "path"
]
}
]
{code}
was:
usage (in output.json configs)
{code:json}
{
outputs: [
"id_fields" : [
"log_message", "logtime", "type", "path"
]
]
{code}
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> usage (in output.json configs)
> {code:json}
> {
> outputs: [
> {
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Status: Patch Available (was: In Progress)
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24356) Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor
[ https://issues.apache.org/jira/browse/AMBARI-24356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24356: Labels: pull-request-available (was: ) > Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor > --- > > Key: AMBARI-24356 > URL: https://issues.apache.org/jira/browse/AMBARI-24356 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.7.0 >Reporter: Rohith Sharma K S >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-24356.01.patch > > > Timeline_Reader is new daemon added in Hadoop-3 on-wards. This component > information need to be added in BlueprintConfigurationProcessor > cc:/ [~jluniya] [~jonathan.hurley] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24354) [Log Search UI] wrong filter label on open log tab
[ https://issues.apache.org/jira/browse/AMBARI-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24354: Labels: pull-request-available (was: ) > [Log Search UI] wrong filter label on open log tab > -- > > Key: AMBARI-24354 > URL: https://issues.apache.org/jira/browse/AMBARI-24354 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Remaining Estimate: 24h > > Steps to reproduce: > - Set date (Like Today) on filter tab > - go to the logs table and click on open log tab > - on the new tab, the date filer shows a NaN value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24338) [Log Search UI] Add application routing information to README.md
[ https://issues.apache.org/jira/browse/AMBARI-24338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1623#comment-1623 ] Hudson commented on AMBARI-24338: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #69 (See [https://builds.apache.org/job/Ambari-branch-2.7/69/]) [AMBARI-24338] [Log Search UI] Add application routing information to (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=db1d2566f0c4e2abf14a1c088a7cd5a134bbfb83]) * (edit) ambari-logsearch/ambari-logsearch-web/README.md > [Log Search UI] Add application routing information to README.md > > > Key: AMBARI-24338 > URL: https://issues.apache.org/jira/browse/AMBARI-24338 > Project: Ambari > Issue Type: Documentation > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 1.5h > Remaining Estimate: 22.5h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24353:
--
Description:
usage (in output.json configs:)
{code:json}
{
outputs: [
"id_fields" : [
"log_message", "logtime", "type", "path"
]
]
{code}
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Fix For: 2.7.1
>
>
> usage (in output.json configs:)
> {code:json}
> {
> outputs: [
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24353:
--
Description:
usage (in output.json configs)
{code:json}
{
outputs: [
"id_fields" : [
"log_message", "logtime", "type", "path"
]
]
{code}
was:
usage (in output.json configs:)
{code:json}
{
outputs: [
"id_fields" : [
"log_message", "logtime", "type", "path"
]
]
{code}
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Fix For: 2.7.1
>
>
> usage (in output.json configs)
> {code:json}
> {
> outputs: [
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24353:
Labels: pull-request-available (was: )
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> usage (in output.json configs)
> {code:json}
> {
> outputs: [
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555770#comment-16555770
]
Hudson commented on AMBARI-24353:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #72 (See
[https://builds.apache.org/job/Ambari-branch-2.7/72/])
AMBARI-24353. Log Feeder: generate solr id from specific fields. (#1882)
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f82827b98faa9746abb9ea5feca8e390778843e4])
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputManagerImpl.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/output/Output.java
* (add)
ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/common/IdGeneratorHelperTest.java
* (add)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/IdGeneratorHelper.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> usage (in output.json configs)
> {code:json}
> {
> outputs: [
> {
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555782#comment-16555782
]
Hudson commented on AMBARI-24353:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9678 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9678/])
AMBARI-24353. Log Feeder: generate solr id from specific fields. (#1881)
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5bd906b741d9247b2bea6ac2d9de57b5209dba1e])
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/output/Output.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputManagerImpl.java
* (add)
ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/common/IdGeneratorHelperTest.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java
* (add)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/IdGeneratorHelper.java
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> usage (in output.json configs)
> {code:json}
> {
> outputs: [
> {
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24355) Logfeeder: use 1 file / db to store checkpoints
Olivér Szabó created AMBARI-24355: - Summary: Logfeeder: use 1 file / db to store checkpoints Key: AMBARI-24355 URL: https://issues.apache.org/jira/browse/AMBARI-24355 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24355) Logfeeder: use 1 file / db to store checkpoints
[ https://issues.apache.org/jira/browse/AMBARI-24355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24355: -- Fix Version/s: (was: 2.7.0) 3.0.0 > Logfeeder: use 1 file / db to store checkpoints > --- > > Key: AMBARI-24355 > URL: https://issues.apache.org/jira/browse/AMBARI-24355 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24344) Upgrade Infra Solr client operation fails for Ubuntu while running migration script for solr upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1680#comment-1680
]
Hudson commented on AMBARI-24344:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #70 (See
[https://builds.apache.org/job/Ambari-branch-2.7/70/])
AMBARI-24344: Upgrade Infra Solr client operation fails for Ubuntu while
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=dc1d5ccac4677175b89dcdd4b7dd99d2a481e337])
* (edit)
ambari-common/src/main/python/ambari_commons/repo_manager/apt_manager.py
> Upgrade Infra Solr client operation fails for Ubuntu while running migration
> script for solr upgrade
>
>
> Key: AMBARI-24344
> URL: https://issues.apache.org/jira/browse/AMBARI-24344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Jasmeen Kaur
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> While running the infra solr upgrade helper script (see command below) on
> Ubuntu cluster , The upgrade infra solr clients operation fails with error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 60, in
> InfraSolrClient().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 56, in upgrade_solr_client
> pkg_provider.remove_package('ambari-infra-solr-client', context,
> ignore_dependencies=True)
> TypeError: wrapper() got an unexpected keyword argument 'ignore_dependencies'
> {code}
> Command -
> {code:java}
> /usr/lib/ambari-infra-solr-client/ambariSolrMigration.sh --ini-file
> --mode backup | tee backup_output.txt
> {code}
> The script works fine on Centos7 though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24353) Log Feeder: generate solr id from specific fields
[
https://issues.apache.org/jira/browse/AMBARI-24353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-24353.
---
Resolution: Fixed
> Log Feeder: generate solr id from specific fields
> -
>
> Key: AMBARI-24353
> URL: https://issues.apache.org/jira/browse/AMBARI-24353
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> usage (in output.json configs)
> {code:json}
> {
> outputs: [
> {
> "id_fields" : [
> "log_message", "logtime", "type", "path"
> ]
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24344) Upgrade Infra Solr client operation fails for Ubuntu while running migration script for solr upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555891#comment-16555891
]
Hudson commented on AMBARI-24344:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9679 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9679/])
AMBARI-24344: Upgrade Infra Solr client operation fails for Ubuntu while
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=37e7352c442eebf25e3d249e40a36400f9182eaa])
* (edit)
ambari-common/src/main/python/ambari_commons/repo_manager/apt_manager.py
> Upgrade Infra Solr client operation fails for Ubuntu while running migration
> script for solr upgrade
>
>
> Key: AMBARI-24344
> URL: https://issues.apache.org/jira/browse/AMBARI-24344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Jasmeen Kaur
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> While running the infra solr upgrade helper script (see command below) on
> Ubuntu cluster , The upgrade infra solr clients operation fails with error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 60, in
> InfraSolrClient().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr_client.py",
> line 56, in upgrade_solr_client
> pkg_provider.remove_package('ambari-infra-solr-client', context,
> ignore_dependencies=True)
> TypeError: wrapper() got an unexpected keyword argument 'ignore_dependencies'
> {code}
> Command -
> {code:java}
> /usr/lib/ambari-infra-solr-client/ambariSolrMigration.sh --ini-file
> --mode backup | tee backup_output.txt
> {code}
> The script works fine on Centos7 though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24357) Revision Control Host Rack Changes
Hari Sekhon created AMBARI-24357: Summary: Revision Control Host Rack Changes Key: AMBARI-24357 URL: https://issues.apache.org/jira/browse/AMBARI-24357 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2, 2.6.0 Reporter: Hari Sekhon Improvement Request to revision control host rack location changes. Right now this appears to not be captured when rack location is changed on the Hosts page. If an admin were to set this wrong (for example Action -> All Hosts -> Set Rack instead or Selected Hosts), then it would be difficult to get back to the correct configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24356) Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor
[ https://issues.apache.org/jira/browse/AMBARI-24356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated AMBARI-24356: --- Attachment: AMBARI-24356.01.patch > Add TIMELINE_READER into Ambari BlueprintConfigurationProcessor > --- > > Key: AMBARI-24356 > URL: https://issues.apache.org/jira/browse/AMBARI-24356 > Project: Ambari > Issue Type: Bug >Reporter: Rohith Sharma K S >Priority: Major > Attachments: AMBARI-24356.01.patch > > > Timeline_Reader is new daemon added in Hadoop-3 on-wards. This component > information need to be added in BlueprintConfigurationProcessor > cc:/ [~jluniya] [~jonathan.hurley] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Attachment: AMBARI-24352-UT.patch
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352-UT.patch, AMBARI-24352.patch
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24260) Ambari shows success when HBase Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24260: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk and branch-2.7 > Ambari shows success when HBase Decommission/Recommission operations fail > - > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > If HBase Decommission/Recommission operation fails with non zero exit code, > that component still gets decommissioned/recommissioned. We need to handle > this failure and not transition the state to Decommissioned/Recommissioned > when the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24260) Ambari shows success when HBase Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556012#comment-16556012 ] Hudson commented on AMBARI-24260: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #73 (See [https://builds.apache.org/job/Ambari-branch-2.7/73/]) AMBARI-24260 Ambari shows success when HBase Decommission/Recommission (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9303409f70be58eeb9cb53b71a60c8c73b3c35a6]) * (edit) ambari-web/app/views/main/host/details/host_component_views/regionserver_view.js * (edit) ambari-web/test/views/main/host/details/host_component_views/regionserver_view_test.js * (edit) ambari-web/app/utils/ajax/ajax.js > Ambari shows success when HBase Decommission/Recommission operations fail > - > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > If HBase Decommission/Recommission operation fails with non zero exit code, > that component still gets decommissioned/recommissioned. We need to handle > this failure and not transition the state to Decommissioned/Recommissioned > when the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24260) Ambari shows success when HBase Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556055#comment-16556055 ] Hudson commented on AMBARI-24260: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9680 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9680/]) AMBARI-24260 Ambari shows success when HBase Decommission/Recommission (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=24c1a6eab620445266fa2af3737f081fbebe7959]) * (edit) ambari-web/app/views/main/host/details/host_component_views/regionserver_view.js * (edit) ambari-web/test/views/main/host/details/host_component_views/regionserver_view_test.js * (edit) ambari-web/app/utils/ajax/ajax.js > Ambari shows success when HBase Decommission/Recommission operations fail > - > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > If HBase Decommission/Recommission operation fails with non zero exit code, > that component still gets decommissioned/recommissioned. We need to handle > this failure and not transition the state to Decommissioned/Recommissioned > when the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24358) Ambari Metrics + Grafana - add graphs for HDFS under-replicated, over-replicated, missing and corrupt blocks
Hari Sekhon created AMBARI-24358: Summary: Ambari Metrics + Grafana - add graphs for HDFS under-replicated, over-replicated, missing and corrupt blocks Key: AMBARI-24358 URL: https://issues.apache.org/jira/browse/AMBARI-24358 Project: Ambari Issue Type: Improvement Components: ambari-metrics, metrics Affects Versions: 2.5.2 Reporter: Hari Sekhon Request to add graphs for under-replicate, over-replicated, missing and corrupt blocks so that we can see the data resilience over time as things change in the cluster, nodes are lost or re-added, replication factors are changed in HDFS etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24358) Ambari Metrics + Grafana - add graphs for HDFS under-replicated, over-replicated, missing and corrupt blocks
[ https://issues.apache.org/jira/browse/AMBARI-24358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24358: - Description: Request to add graphs for under-replicated, over-replicated, missing and corrupt blocks so that we can see the data resilience over time as things change in the cluster, nodes are lost or re-added, replication factors are changed in HDFS etc. (was: Request to add graphs for under-replicate, over-replicated, missing and corrupt blocks so that we can see the data resilience over time as things change in the cluster, nodes are lost or re-added, replication factors are changed in HDFS etc.) > Ambari Metrics + Grafana - add graphs for HDFS under-replicated, > over-replicated, missing and corrupt blocks > > > Key: AMBARI-24358 > URL: https://issues.apache.org/jira/browse/AMBARI-24358 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, metrics >Affects Versions: 2.5.2 >Reporter: Hari Sekhon >Priority: Major > > Request to add graphs for under-replicated, over-replicated, missing and > corrupt blocks so that we can see the data resilience over time as things > change in the cluster, nodes are lost or re-added, replication factors are > changed in HDFS etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24350) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24350.
--
Resolution: Fixed
> UI service configs page hangs.
> --
>
> Key: AMBARI-24350
> URL: https://issues.apache.org/jira/browse/AMBARI-24350
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> UI code fails :
> {code:java}
> app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
> at Class. (app.js:1898)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
> at *line 6* while processing the response:
> {code:java}
> 1 loadConfigProperties: function loadConfigProperties() {
> 2var self = this;
> 3
> App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
> () {
> 4 App.config.loadClusterConfigsFromStack().always(function () {
> 5
> App.router.get('configurationController').updateConfigTags().always(function
> () {
> 6
> App.router.get('updateController').updateClusterEnv().always(function () {
> 7self.set('isConfigsPropertiesLoaded', true);
> 8 });
> });
> });
> });
> },
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24342) PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for service.
[
https://issues.apache.org/jira/browse/AMBARI-24342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24342.
--
Resolution: Fixed
> PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for
> service.
> -
>
> Key: AMBARI-24342
> URL: https://issues.apache.org/jira/browse/AMBARI-24342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> *ISSUE:*
> Post Trunk merge, deploy fails at Step 7.
> *Console O/P:*
> {code:java}
> app.js:67915 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.updateAttributesFromTheme
> (http://172.22.107.63:8080/javascripts/app.js:67915:90)
> at http://172.22.107.63:8080/javascripts/app.js:44914:21
> at Array.forEach (native)
> at Class.updateConfigAttributesFromThemes
> (http://172.22.107.63:8080/javascripts/app.js:44913:41)
> at Class.applyServicesConfigs
> (http://172.22.107.63:8080/javascripts/app.js:43405:10)
> at Class.loadStep (http://172.22.107.63:8080/javascripts/app.js:43345:12)
> at Class.willInsertElement
> (http://172.22.107.63:8080/javascripts/app.js:249561:30)
> at Class.newFunc [as willInsertElement]
> (http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
> at Class.trigger
> (http://172.22.107.63:8080/javascripts/vendor.js:25526:21)
> at Class.newFunc [as trigger]
> (http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
> {code}
> Code line:
> {code:java}
> updateAttributesFromTheme: function updateAttributesFromTheme(serviceName) {
> this.prepareSectionsConfigProperties(serviceName);
> var serviceConfigs = this.get('stepConfigs').findProperty('serviceName',
> serviceName).get('configs'), <-- Issue LINE
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24341.
--
Resolution: Duplicate
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Ishan Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-07-23 at 3.29.26 PM.png, Screen Shot
> 2018-07-23 at 3.29.42 PM.png
>
>
> *ISSUE:*
> UI Service Config page hangs when clicked post deploy.
> Below is the calls made:
> -
> http://172.27.56.18:8080/api/v1/clusters/cl1?fields=Clusters/desired_configs&_=1532384868506
>
> which succeeds.
> !Screen Shot 2018-07-23 at 3.29.26 PM.png! !Screen Shot 2018-07-23 at
> 3.29.42 PM.png!
> And then the UI code fails :
> {code}
> app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
> at Class. (app.js:1898)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
> at *line 6* while processing the response:
> {code}
> 1 loadConfigProperties: function loadConfigProperties() {
> 2var self = this;
> 3
> App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
> () {
> 4 App.config.loadClusterConfigsFromStack().always(function () {
> 5
> App.router.get('configurationController').updateConfigTags().always(function
> () {
> 6
> App.router.get('updateController').updateClusterEnv().always(function () {
> 7self.set('isConfigsPropertiesLoaded', true);
> 8 });
> });
> });
> });
> },
> {code}
> .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24354) [Log Search UI] wrong filter label on open log tab
[ https://issues.apache.org/jira/browse/AMBARI-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556278#comment-16556278 ] Hudson commented on AMBARI-24354: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9681 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9681/]) [AMBARI-24354] [Log Search UI] wrong filter label on open log tab (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e5160dfc2201d104f84e59edced76c9b0575527b]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-filtering-utils.service.ts > [Log Search UI] wrong filter label on open log tab > -- > > Key: AMBARI-24354 > URL: https://issues.apache.org/jira/browse/AMBARI-24354 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 1h 20m > Remaining Estimate: 22h 40m > > Steps to reproduce: > - Set date (Like Today) on filter tab > - go to the logs table and click on open log tab > - on the new tab, the date filer shows a NaN value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24354) [Log Search UI] wrong filter label on open log tab
[ https://issues.apache.org/jira/browse/AMBARI-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556280#comment-16556280 ] Hudson commented on AMBARI-24354: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #74 (See [https://builds.apache.org/job/Ambari-branch-2.7/74/]) [AMBARI-24354] [Log Search UI] wrong filter label on open log tab (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b8461bf951fc9175f95ac2a434ef03d4ff534325]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-filtering-utils.service.ts > [Log Search UI] wrong filter label on open log tab > -- > > Key: AMBARI-24354 > URL: https://issues.apache.org/jira/browse/AMBARI-24354 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 1h 20m > Remaining Estimate: 22h 40m > > Steps to reproduce: > - Set date (Like Today) on filter tab > - go to the logs table and click on open log tab > - on the new tab, the date filer shows a NaN value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
