[jira] [Updated] (AMBARI-20975) Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhuvanthi Radhakrishnan updated AMBARI-20975:
---
Attachment: AMBARI-20975.patch
> Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
> -
>
> Key: AMBARI-20975
> URL: https://issues.apache.org/jira/browse/AMBARI-20975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
> Attachments: AMBARI-20975.patch
>
>
> Add to HDP stack_features.json
> {noformat}
> {
>"name": "admin_toolkit_support",
>"description": "Supports the nifi admin toolkit",
>"min_version": "3.0.0.0"
> },
> {
> "name": "tls_toolkit_san",
> "description": "Support subject alternative name flag",
> "min_version": "3.0.0.0"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20975) Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhuvanthi Radhakrishnan updated AMBARI-20975:
---
Status: Patch Available (was: Open)
> Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
> -
>
> Key: AMBARI-20975
> URL: https://issues.apache.org/jira/browse/AMBARI-20975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
> Attachments: AMBARI-20975.patch
>
>
> Add to HDP stack_features.json
> {noformat}
> {
>"name": "admin_toolkit_support",
>"description": "Supports the nifi admin toolkit",
>"min_version": "3.0.0.0"
> },
> {
> "name": "tls_toolkit_san",
> "description": "Support subject alternative name flag",
> "min_version": "3.0.0.0"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20975) Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-20975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhuvanthi Radhakrishnan updated AMBARI-20975:
---
Description:
Add to HDP stack_features.json
{noformat}
{
"name": "admin_toolkit_support",
"description": "Supports the nifi admin toolkit",
"min_version": "3.0.0.0"
},
{
"name": "tls_toolkit_san",
"description": "Support subject alternative name flag",
"min_version": "3.0.0.0"
}
{noformat}
was:
Add to HDP stack_features.json
{
"name": "admin_toolkit_support",
"description": "Supports the nifi admin toolkit",
"min_version": "3.0.0.0"
}
{
"name": "tls_toolkit_san",
"description": "Support subject alternative name flag",
"min_version": "3.0.0.0"
}
> Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
> -
>
> Key: AMBARI-20975
> URL: https://issues.apache.org/jira/browse/AMBARI-20975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
>
> Add to HDP stack_features.json
> {noformat}
> {
>"name": "admin_toolkit_support",
>"description": "Supports the nifi admin toolkit",
>"min_version": "3.0.0.0"
> },
> {
> "name": "tls_toolkit_san",
> "description": "Support subject alternative name flag",
> "min_version": "3.0.0.0"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20975) Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
Madhuvanthi Radhakrishnan created AMBARI-20975:
--
Summary: Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
Key: AMBARI-20975
URL: https://issues.apache.org/jira/browse/AMBARI-20975
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Madhuvanthi Radhakrishnan
Assignee: Madhuvanthi Radhakrishnan
Fix For: 2.5.1
Add to HDP stack_features.json
{
"name": "admin_toolkit_support",
"description": "Supports the nifi admin toolkit",
"min_version": "3.0.0.0"
}
{
"name": "tls_toolkit_san",
"description": "Support subject alternative name flag",
"min_version": "3.0.0.0"
}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack
[ https://issues.apache.org/jira/browse/AMBARI-20974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20974: --- Status: Patch Available (was: Open) > Ambari fails to start due to NPE after installation of HDF mpack > > > Key: AMBARI-20974 > URL: https://issues.apache.org/jira/browse/AMBARI-20974 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > Attachments: AMBARI-20974_trunk.patch > > > when we install HDF mpack we do the following steps > yum install ambari-server > ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose > ambari-server setup > The permissions and ownership for stacks , common-services etc is set > correctly during ambari-server setup > Ambari-server daemon is configured to run under user 'slava'. Change this > setting [y/n] (n)? n > Adjusting ambari-server permissions and ownership... > However, to add HDF services to HDP cluster we install the mpack after > deploying the HDP cluster and hence when running Ambari as non-root and with > umask = 0027, the permissions and ownerships don't get updated. > Workaround: > Re-run ambari-server setup command after installing the HDF mpack but don't > really make any config changes. Run this step only to update the permissions. > ambari-server setup -s -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack
[ https://issues.apache.org/jira/browse/AMBARI-20974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-20974: --- Attachment: AMBARI-20974_trunk.patch > Ambari fails to start due to NPE after installation of HDF mpack > > > Key: AMBARI-20974 > URL: https://issues.apache.org/jira/browse/AMBARI-20974 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > Attachments: AMBARI-20974_trunk.patch > > > when we install HDF mpack we do the following steps > yum install ambari-server > ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose > ambari-server setup > The permissions and ownership for stacks , common-services etc is set > correctly during ambari-server setup > Ambari-server daemon is configured to run under user 'slava'. Change this > setting [y/n] (n)? n > Adjusting ambari-server permissions and ownership... > However, to add HDF services to HDP cluster we install the mpack after > deploying the HDP cluster and hence when running Ambari as non-root and with > umask = 0027, the permissions and ownerships don't get updated. > Workaround: > Re-run ambari-server setup command after installing the HDF mpack but don't > really make any config changes. Run this step only to update the permissions. > ambari-server setup -s -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20961) RBAC: Service Operator/Administrator Role don't have HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons on Web UI
[ https://issues.apache.org/jira/browse/AMBARI-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003592#comment-16003592 ] Yao Lei commented on AMBARI-20961: -- [~u39kun] Thank you > RBAC: Service Operator/Administrator Role don't have > HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons > on Web UI > -- > > Key: AMBARI-20961 > URL: https://issues.apache.org/jira/browse/AMBARI-20961 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20961.patch > > > Steps to reproduce: > 1.Create a user named test and assign Service Operator(Administrator) Role to > this user. > 2.Login with this user and open Services -> Hive -> Service Actions, the > menu include highlight items : Add Hive Metastore and Add HiveServer2. > Zookeeper,Hbase and other service also have the above issue. > Because Service Operator(Administrator) Role don't have > HOST.ADD_DELETE_COMPONENTS permission at all , we 'd better hide these buttons -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20971) Repository Resource Providers Should Expose the Repository ID by Default on Minimal Responses
[
https://issues.apache.org/jira/browse/AMBARI-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20971:
-
Attachment: AMBARI-20971.patch
> Repository Resource Providers Should Expose the Repository ID by Default on
> Minimal Responses
> -
>
> Key: AMBARI-20971
> URL: https://issues.apache.org/jira/browse/AMBARI-20971
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-20971.patch
>
>
> There are 3 resource providers which should begin exposed the repository ID
> by default on all responses, even minimal responses:
> - {{RepositoryResourceProvider}}
> - {{RespositoryVersionResourceProvider}}
> - {{CompatibleRepositoryVersionResourceProvider}}
> This will allow anyone querying these endpoints to reference a repository
> uniquely, instead of by version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20958) Host Version on Finalization Must Be Scoped Correctly Based on Upgrade Type
[
https://issues.apache.org/jira/browse/AMBARI-20958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-20958.
--
Resolution: Fixed
> Host Version on Finalization Must Be Scoped Correctly Based on Upgrade Type
> ---
>
> Key: AMBARI-20958
> URL: https://issues.apache.org/jira/browse/AMBARI-20958
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
>
> During a {{PATCH}} or {{SERVICE}} upgrade, finalization will either fail or
> be incorrect based on the topology of the cluster. In cases where the
> upgraded service has components on every host, the {{host_version}} table is
> moved incorrectly to reflect the stack of the upgraded component.
> h6. Topology (HDP 2.4.2.0-236)
> - c6401 - ZooKeeper Server, ZooKeeper Client, Storm Nimbus
> - c6402 - ZooKeeper Server, ZooKeeper Client, Storm Supervisor
> - c6403 - ZooKeeper Server, ZooKeeper Client, Storm Supervisor
> h6. {{SERVICE}} upgrade from to HDP-2.5.4.0-121 for {{STORM}} only:
> {noformat}
> Begin finalizing the upgrade of cluster c1 to version 2.5.4.0-121
> Finalizing the upgraded state of host components in 3 host(s).
> Finalizing the version for 3 host(s).
> Finalizing the version for cluster c1.
> Creating upgrade history.
> Upgrade was successful!
> {noformat}
> {code}
> ambari=# SELECT host_version.host_id, repo_version.version, state FROM
> host_version, repo_version WHERE host_version.repo_version_id =
> repo_version.repo_version_id ORDER BY version, host_id;
> host_id | version | state
> -+-+---
>1 | 2.4.2.0-236 | INSTALLED
>2 | 2.4.2.0-236 | INSTALLED
>3 | 2.4.2.0-236 | INSTALLED
>1 | 2.5.4.0-121 | CURRENT
>2 | 2.5.4.0-121 | CURRENT
>3 | 2.5.4.0-121 | CURRENT
> (6 rows)
> {code}
> In the event that {{STORM}} is not installed on all hosts, finalization fails:
> h6. Topology (HDP 2.4.2.0-236)
> - c6401 - ZooKeeper Server, ZooKeeper Client, Storm Nimbus
> - c6402 - ZooKeeper Server, ZooKeeper Client, Storm Supervisor
> - c6403 - ZooKeeper Server, ZooKeeper Client
> {noformat}
> Begin finalizing the upgrade of cluster c1 to version 2.5.4.0-121
> The following 1 host(s) have not been upgraded to version 2.5.4.0-121. Please
> install and upgrade the Stack Version on those hosts and try again.
> Hosts: c6403.ambari.apache.org
> {noformat}
> The {{host_version}} table must allow for multiple {{CURRENT}} versions.
> Finalization must be allowed to occur when not all hosts are targeted for
> upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20973) Review the use/need of host clean up script
[ https://issues.apache.org/jira/browse/AMBARI-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20973: - Attachment: AMBARI-20973.patch > Review the use/need of host clean up script > --- > > Key: AMBARI-20973 > URL: https://issues.apache.org/jira/browse/AMBARI-20973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-20973.patch, no_host_cleanup_script.png > > > Host cleanup is not kept up to date but is recommended as something that > users can run. Either we should > retire the cleanup script, or > reduce its functionality to a set of operations that is safe to perform, or > update the script in light of multi-stack support > With MPack approach, Ambari can no longer assume what cleaning up means for > various SKUs - which packages HDP or EDW installs that should not be there > when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20973) Review the use/need of host clean up script
[ https://issues.apache.org/jira/browse/AMBARI-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20973: - Attachment: (was: AMBARI-20973.patch) > Review the use/need of host clean up script > --- > > Key: AMBARI-20973 > URL: https://issues.apache.org/jira/browse/AMBARI-20973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 3.0.0 > > Attachments: no_host_cleanup_script.png > > > Host cleanup is not kept up to date but is recommended as something that > users can run. Either we should > retire the cleanup script, or > reduce its functionality to a set of operations that is safe to perform, or > update the script in light of multi-stack support > With MPack approach, Ambari can no longer assume what cleaning up means for > various SKUs - which packages HDP or EDW installs that should not be there > when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20916) Run new heartbeatThread and statusCommand executor instead of old
[
https://issues.apache.org/jira/browse/AMBARI-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003511#comment-16003511
]
Hadoop QA commented on AMBARI-20916:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12867180/AMBARI-20916.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/11576//console
This message is automatically generated.
> Run new heartbeatThread and statusCommand executor instead of old
> --
>
> Key: AMBARI-20916
> URL: https://issues.apache.org/jira/browse/AMBARI-20916
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20916.patch, AMBARI-20916.patch
>
>
> We have these threads running only in scope of UT. Need to start them on
> ambari-agent start for so testing with ambari-server can be done.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20916) Run new heartbeatThread and statusCommand executor instead of old
[ https://issues.apache.org/jira/browse/AMBARI-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-20916: - Attachment: AMBARI-20916.patch > Run new heartbeatThread and statusCommand executor instead of old > -- > > Key: AMBARI-20916 > URL: https://issues.apache.org/jira/browse/AMBARI-20916 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-20916.patch, AMBARI-20916.patch > > > We have these threads running only in scope of UT. Need to start them on > ambari-agent start for so testing with ambari-server can be done. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20973) Review the use/need of host clean up script
[ https://issues.apache.org/jira/browse/AMBARI-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20973: - Status: Patch Available (was: Open) > Review the use/need of host clean up script > --- > > Key: AMBARI-20973 > URL: https://issues.apache.org/jira/browse/AMBARI-20973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-20973.patch, no_host_cleanup_script.png > > > Host cleanup is not kept up to date but is recommended as something that > users can run. Either we should > retire the cleanup script, or > reduce its functionality to a set of operations that is safe to perform, or > update the script in light of multi-stack support > With MPack approach, Ambari can no longer assume what cleaning up means for > various SKUs - which packages HDP or EDW installs that should not be there > when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20973) Review the use/need of host clean up script
[ https://issues.apache.org/jira/browse/AMBARI-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20973: - Fix Version/s: 3.0.0 > Review the use/need of host clean up script > --- > > Key: AMBARI-20973 > URL: https://issues.apache.org/jira/browse/AMBARI-20973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-20973.patch, no_host_cleanup_script.png > > > Host cleanup is not kept up to date but is recommended as something that > users can run. Either we should > retire the cleanup script, or > reduce its functionality to a set of operations that is safe to perform, or > update the script in light of multi-stack support > With MPack approach, Ambari can no longer assume what cleaning up means for > various SKUs - which packages HDP or EDW installs that should not be there > when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20973) Review the use/need of host clean up script
[ https://issues.apache.org/jira/browse/AMBARI-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20973: - Attachment: no_host_cleanup_script.png > Review the use/need of host clean up script > --- > > Key: AMBARI-20973 > URL: https://issues.apache.org/jira/browse/AMBARI-20973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-20973.patch, no_host_cleanup_script.png > > > Host cleanup is not kept up to date but is recommended as something that > users can run. Either we should > retire the cleanup script, or > reduce its functionality to a set of operations that is safe to perform, or > update the script in light of multi-stack support > With MPack approach, Ambari can no longer assume what cleaning up means for > various SKUs - which packages HDP or EDW installs that should not be there > when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20973) Review the use/need of host clean up script
[ https://issues.apache.org/jira/browse/AMBARI-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20973: - Attachment: AMBARI-20973.patch > Review the use/need of host clean up script > --- > > Key: AMBARI-20973 > URL: https://issues.apache.org/jira/browse/AMBARI-20973 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-20973.patch > > > Host cleanup is not kept up to date but is recommended as something that > users can run. Either we should > retire the cleanup script, or > reduce its functionality to a set of operations that is safe to perform, or > update the script in light of multi-stack support > With MPack approach, Ambari can no longer assume what cleaning up means for > various SKUs - which packages HDP or EDW installs that should not be there > when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack
Madhuvanthi Radhakrishnan created AMBARI-20974: -- Summary: Ambari fails to start due to NPE after installation of HDF mpack Key: AMBARI-20974 URL: https://issues.apache.org/jira/browse/AMBARI-20974 Project: Ambari Issue Type: Bug Components: ambari-sever Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.5.1 when we install HDF mpack we do the following steps yum install ambari-server ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose ambari-server setup The permissions and ownership for stacks , common-services etc is set correctly during ambari-server setup Ambari-server daemon is configured to run under user 'slava'. Change this setting [y/n] (n)? n Adjusting ambari-server permissions and ownership... However, to add HDF services to HDP cluster we install the mpack after deploying the HDP cluster and hence when running Ambari as non-root and with umask = 0027, the permissions and ownerships don't get updated. Workaround: Re-run ambari-server setup command after installing the HDF mpack but don't really make any config changes. Run this step only to update the permissions. ambari-server setup -s -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20973) Review the use/need of host clean up script
Ishan Bhatt created AMBARI-20973: Summary: Review the use/need of host clean up script Key: AMBARI-20973 URL: https://issues.apache.org/jira/browse/AMBARI-20973 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk Host cleanup is not kept up to date but is recommended as something that users can run. Either we should retire the cleanup script, or reduce its functionality to a set of operations that is safe to perform, or update the script in light of multi-stack support With MPack approach, Ambari can no longer assume what cleaning up means for various SKUs - which packages HDP or EDW installs that should not be there when you perform fresh install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20595) There is a syntax error in install script hence ambari doesn't pick the python 2.7 if system python path is not present
[
https://issues.apache.org/jira/browse/AMBARI-20595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003445#comment-16003445
]
Hudson commented on AMBARI-20595:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7447 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7447/])
AMBARI-20595. There is a syntax error in install script hence ambari (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=436c912844657347b5a80f89dedd6d537db82867])
* (edit) ambari-server/conf/unix/install-helper.sh
* (edit) ambari-agent/conf/unix/install-helper.sh
> There is a syntax error in install script hence ambari doesn't pick the
> python 2.7 if system python path is not present
> ---
>
> Key: AMBARI-20595
> URL: https://issues.apache.org/jira/browse/AMBARI-20595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: trunk
>Reporter: Aman Poonia
>Assignee: Aman Poonia
>Priority: Minor
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20595.patch
>
>
> This snippet of code
> {quote}
> python_binaries=( "/usr/bin/python" "/usr/bin/python2" "/usr/bin/python2.7",
> "/usr/bin/python2.6" )
> {quote}
> The comma after "/usr/bin/python2.7", causes this path to be always invalid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20961) RBAC: Service Operator/Administrator Role don't have HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons on Web UI
[ https://issues.apache.org/jira/browse/AMBARI-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003446#comment-16003446 ] Hudson commented on AMBARI-20961: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7447 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7447/]) AMBARI-20961. RBAC: Service Operator/Administrator Role don't have (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6e1367d0b0fe44a26f772218de19e92154597e7b]) * (edit) ambari-web/app/views/main/service/item.js > RBAC: Service Operator/Administrator Role don't have > HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons > on Web UI > -- > > Key: AMBARI-20961 > URL: https://issues.apache.org/jira/browse/AMBARI-20961 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20961.patch > > > Steps to reproduce: > 1.Create a user named test and assign Service Operator(Administrator) Role to > this user. > 2.Login with this user and open Services -> Hive -> Service Actions, the > menu include highlight items : Add Hive Metastore and Add HiveServer2. > Zookeeper,Hbase and other service also have the above issue. > Because Service Operator(Administrator) Role don't have > HOST.ADD_DELETE_COMPONENTS permission at all , we 'd better hide these buttons -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20961) RBAC: Service Operator/Administrator Role don't have HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons on Web UI
[ https://issues.apache.org/jira/browse/AMBARI-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003437#comment-16003437 ] Hudson commented on AMBARI-20961: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1518 (See [https://builds.apache.org/job/Ambari-branch-2.5/1518/]) AMBARI-20961. RBAC: Service Operator/Administrator Role don't have (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ea936070a5914731ed0e414533df4d2016f64d19]) * (edit) ambari-web/app/views/main/service/item.js > RBAC: Service Operator/Administrator Role don't have > HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons > on Web UI > -- > > Key: AMBARI-20961 > URL: https://issues.apache.org/jira/browse/AMBARI-20961 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20961.patch > > > Steps to reproduce: > 1.Create a user named test and assign Service Operator(Administrator) Role to > this user. > 2.Login with this user and open Services -> Hive -> Service Actions, the > menu include highlight items : Add Hive Metastore and Add HiveServer2. > Zookeeper,Hbase and other service also have the above issue. > Because Service Operator(Administrator) Role don't have > HOST.ADD_DELETE_COMPONENTS permission at all , we 'd better hide these buttons -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20595) There is a syntax error in install script hence ambari doesn't pick the python 2.7 if system python path is not present
[
https://issues.apache.org/jira/browse/AMBARI-20595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003436#comment-16003436
]
Hudson commented on AMBARI-20595:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1518 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1518/])
AMBARI-20595. There is a syntax error in install script hence ambari (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e12518654ef378232e5ae8e4d9b488df4703cc8d])
* (edit) ambari-agent/conf/unix/install-helper.sh
* (edit) ambari-server/conf/unix/install-helper.sh
> There is a syntax error in install script hence ambari doesn't pick the
> python 2.7 if system python path is not present
> ---
>
> Key: AMBARI-20595
> URL: https://issues.apache.org/jira/browse/AMBARI-20595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: trunk
>Reporter: Aman Poonia
>Assignee: Aman Poonia
>Priority: Minor
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20595.patch
>
>
> This snippet of code
> {quote}
> python_binaries=( "/usr/bin/python" "/usr/bin/python2" "/usr/bin/python2.7",
> "/usr/bin/python2.6" )
> {quote}
> The comma after "/usr/bin/python2.7", causes this path to be always invalid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard
[ https://issues.apache.org/jira/browse/AMBARI-20972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20972: -- Attachment: wfmSort.PNG > Workflow Designer View: Provide sorting of workflows on dashboard > - > > Key: AMBARI-20972 > URL: https://issues.apache.org/jira/browse/AMBARI-20972 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20972.patch, wfmSort.PNG > > > The workflows displayed on the worflow designer view dashboard are not > sortable. The ability to sort via Name, Status, User, Created Time, End Time > and jobId should be included -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard
[ https://issues.apache.org/jira/browse/AMBARI-20972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20972: -- Status: Patch Available (was: Open) > Workflow Designer View: Provide sorting of workflows on dashboard > - > > Key: AMBARI-20972 > URL: https://issues.apache.org/jira/browse/AMBARI-20972 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20972.patch > > > The workflows displayed on the worflow designer view dashboard are not > sortable. The ability to sort via Name, Status, User, Created Time, End Time > and jobId should be included -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard
[ https://issues.apache.org/jira/browse/AMBARI-20972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20972: -- Attachment: AMBARI-20972.patch > Workflow Designer View: Provide sorting of workflows on dashboard > - > > Key: AMBARI-20972 > URL: https://issues.apache.org/jira/browse/AMBARI-20972 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20972.patch > > > The workflows displayed on the worflow designer view dashboard are not > sortable. The ability to sort via Name, Status, User, Created Time, End Time > and jobId should be included -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard
Anita Gnanamalar Jebaraj created AMBARI-20972: - Summary: Workflow Designer View: Provide sorting of workflows on dashboard Key: AMBARI-20972 URL: https://issues.apache.org/jira/browse/AMBARI-20972 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Anita Gnanamalar Jebaraj Assignee: Anita Gnanamalar Jebaraj Fix For: trunk The workflows displayed on the worflow designer view dashboard are not sortable. The ability to sort via Name, Status, User, Created Time, End Time and jobId should be included -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20368: --- Resolution: Fixed Status: Resolved (was: Patch Available) It appears that the change has been made. > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.4.2, 2.5.1 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. > Maybe > there is no necessary to deal with hdfs-site about hadoop_conf_dir in > hbase.py. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"
[ https://issues.apache.org/jira/browse/AMBARI-20673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20673. Resolution: Fixed > For sort/partition operator, if there is only 1 reducer, display just "sort" > rather than "sort/partition" > - > > Key: AMBARI-20673 > URL: https://issues.apache.org/jira/browse/AMBARI-20673 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20673-trunk.01.patch, > AMBARI-20673-trunk.02.patch, AMBARI-20673-trunk.patch > > > For sort/partition operator, if there is only 1 reducer, display just "sort" > rather than "sort/partition" in visual explain graph -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20961) RBAC: Service Operator/Administrator Role don't have HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons on Web UI
[ https://issues.apache.org/jira/browse/AMBARI-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20961: - Resolution: Fixed Status: Resolved (was: Patch Available) +1'd on ReviewBoard. Committed to trunk and branch-2.5. > RBAC: Service Operator/Administrator Role don't have > HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons > on Web UI > -- > > Key: AMBARI-20961 > URL: https://issues.apache.org/jira/browse/AMBARI-20961 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20961.patch > > > Steps to reproduce: > 1.Create a user named test and assign Service Operator(Administrator) Role to > this user. > 2.Login with this user and open Services -> Hive -> Service Actions, the > menu include highlight items : Add Hive Metastore and Add HiveServer2. > Zookeeper,Hbase and other service also have the above issue. > Because Service Operator(Administrator) Role don't have > HOST.ADD_DELETE_COMPONENTS permission at all , we 'd better hide these buttons -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"
[ https://issues.apache.org/jira/browse/AMBARI-20673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20673: --- Priority: Blocker (was: Major) > For sort/partition operator, if there is only 1 reducer, display just "sort" > rather than "sort/partition" > - > > Key: AMBARI-20673 > URL: https://issues.apache.org/jira/browse/AMBARI-20673 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20673-trunk.01.patch, > AMBARI-20673-trunk.02.patch, AMBARI-20673-trunk.patch > > > For sort/partition operator, if there is only 1 reducer, display just "sort" > rather than "sort/partition" in visual explain graph -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20595) There is a syntax error in install script hence ambari doesn't pick the python 2.7 if system python path is not present
[
https://issues.apache.org/jira/browse/AMBARI-20595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20595:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> There is a syntax error in install script hence ambari doesn't pick the
> python 2.7 if system python path is not present
> ---
>
> Key: AMBARI-20595
> URL: https://issues.apache.org/jira/browse/AMBARI-20595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: trunk
>Reporter: Aman Poonia
>Assignee: Aman Poonia
>Priority: Minor
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20595.patch
>
>
> This snippet of code
> {quote}
> python_binaries=( "/usr/bin/python" "/usr/bin/python2" "/usr/bin/python2.7",
> "/usr/bin/python2.6" )
> {quote}
> The comma after "/usr/bin/python2.7", causes this path to be always invalid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20554) Fix minimum recommended value for slider and Tez AM for HSI.
[ https://issues.apache.org/jira/browse/AMBARI-20554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20554. Resolution: Fixed > Fix minimum recommended value for slider and Tez AM for HSI. > > > Key: AMBARI-20554 > URL: https://issues.apache.org/jira/browse/AMBARI-20554 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20554.branch2.5.patch, AMBARI-20554.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20615) HMS only deployment should not require mapred-site config files
[ https://issues.apache.org/jira/browse/AMBARI-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20615. Resolution: Fixed > HMS only deployment should not require mapred-site config files > --- > > Key: AMBARI-20615 > URL: https://issues.apache.org/jira/browse/AMBARI-20615 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > > HMS does not require map-red config so need a condition to skip it incase of > hive metastore installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20570) Remove property atlas.cluster.name from hive-site for fresh deployments
[ https://issues.apache.org/jira/browse/AMBARI-20570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20570. Resolution: Fixed > Remove property atlas.cluster.name from hive-site for fresh deployments > --- > > Key: AMBARI-20570 > URL: https://issues.apache.org/jira/browse/AMBARI-20570 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.1 > > Attachments: AMBARI-20570.patch > > > Property atlas.cluster.name is no longer expected in hive-site. It should > have been deleted in the stack definition, from HDP-2.5/hive-site onwards but > it was missed. > Presence of this property does not cause any problem either. > Now, if you deploy Hive and Atlas together (UI or BP) you will see this > property added and subsequently removed when Atlas is removed. > If you deploy just Hive and then add Atlas, the property will not get added > and thus it will not appear in the list of properties being removed. > This bug is only tracking fresh cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20556) Add SPARK_CONF_DIR in livy-env when upgrading from HDP 2.5 to 2.6
[ https://issues.apache.org/jira/browse/AMBARI-20556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20556: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add SPARK_CONF_DIR in livy-env when upgrading from HDP 2.5 to 2.6 > - > > Key: AMBARI-20556 > URL: https://issues.apache.org/jira/browse/AMBARI-20556 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Yesha Vora >Assignee: Jeff Zhang > Fix For: 2.5.1 > > Attachments: AMBARI-20556-1.patch, AMBARI-20556-2.patch > > > Thanks for [~yeshavora] for finding this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20612) Fetching running application logs results in 'java.io.IOException'
[ https://issues.apache.org/jira/browse/AMBARI-20612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20612. Resolution: Fixed > Fetching running application logs results in 'java.io.IOException' > -- > > Key: AMBARI-20612 > URL: https://issues.apache.org/jira/browse/AMBARI-20612 > Project: Ambari > Issue Type: Bug >Reporter: Sumana Sathish >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > > A new property called yarn.log.server.web-service.url was added in HDP 2.6 > It takes value from yarn.timeline-service.webapp.address if the > yarn.http.policy is HTTP_ONLY and takes value from > yarn.timeline-service.webapp.https.address if the yarn.http.policy is > HTTPS_ONLY. > The logic works on fresh installs but is not present during upgrades from > HDP2.x to HDP2.6 > Fix is to provide the upgrade packs for it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20568) Update hash aggregation settings for llap in hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20568: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update hash aggregation settings for llap in hdp stack > -- > > Key: AMBARI-20568 > URL: https://issues.apache.org/jira/browse/AMBARI-20568 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.1 > > Attachments: AMBARI-20568.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20702) User should be prompted for confirmation before closing the browser window
[ https://issues.apache.org/jira/browse/AMBARI-20702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20702: -- Assignee: Pallav Kulshreshtha > User should be prompted for confirmation before closing the browser window > -- > > Key: AMBARI-20702 > URL: https://issues.apache.org/jira/browse/AMBARI-20702 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Pallav Kulshreshtha > Labels: WFD, WFM > Fix For: 2.5.2 > > > User should be prompted for confirmation before closing the browser window. > If user is in designer page and in middle of workflow creation and he clicks > on closing browser window or browser instance, he should be prompted for > confirmation before actually closing the window. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20706) Workflow manager is not prompting for custom properties if its part of an expression
[ https://issues.apache.org/jira/browse/AMBARI-20706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20706: --- Fix Version/s: (was: 2.5.1) 2.5.2 > Workflow manager is not prompting for custom properties if its part of an > expression > > > Key: AMBARI-20706 > URL: https://issues.apache.org/jira/browse/AMBARI-20706 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Belliraj HB >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.2 > > > Workflow manager is not prompting for custom properties if its part of an > expression. > Workflow manager should identify all the properties and prompt them during > workflow submission. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20702) User should be prompted for confirmation before closing the browser window
[ https://issues.apache.org/jira/browse/AMBARI-20702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20702: --- Fix Version/s: (was: 2.5.1) 2.5.2 > User should be prompted for confirmation before closing the browser window > -- > > Key: AMBARI-20702 > URL: https://issues.apache.org/jira/browse/AMBARI-20702 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Pallav Kulshreshtha > Labels: WFD, WFM > Fix For: 2.5.2 > > > User should be prompted for confirmation before closing the browser window. > If user is in designer page and in middle of workflow creation and he clicks > on closing browser window or browser instance, he should be prompted for > confirmation before actually closing the window. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20701) Need to provide text editor for email subjec
[
https://issues.apache.org/jira/browse/AMBARI-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20701:
---
Fix Version/s: (was: 2.5.1)
trunk
> Need to provide text editor for email subjec
>
>
> Key: AMBARI-20701
> URL: https://issues.apache.org/jira/browse/AMBARI-20701
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
> Labels: WFD, WFM
> Fix For: trunk
>
>
> Below is the email body from a real world customer workflow.
> {code}
> Errors:
> import_MARA: ${wf:actionData("import_MARA")["errorMsg"]}
> import_T024: ${wf:actionData("import_T024")["errorMsg"]}
> import_ZE2E_PL_BU: ${wf:actionData("import_ZE2E_PL_BU")["errorMsg"]}
> import_ZE2E_AGINGEXCLUDE:
> ${wf:actionData("import_ZE2E_AGINGEXCLUDE")["errorMsg"]}
> import_ZE2E_MOVMT: ${wf:actionData("import_ZE2E_MOVMT")["errorMsg"]}
> import_MARD: ${wf:actionData("import_MARD")["errorMsg"]}
> import_MBEW: ${wf:actionData("import_MBEW")["errorMsg"]}
> import_MKPF: ${wf:actionData("import_MKPF")["errorMsg"]}
> import_MSEG: ${wf:actionData("import_MSEG")["errorMsg"]}
> import_MSSL: ${wf:actionData("import_MSSL")["errorMsg"]}
> import_LQUA: ${wf:actionData("import_LQUA")["errorMsg"]}
> import_ZWIPCOMPINVNT: ${wf:actionData("import_ZWIPCOMPINVNT")["errorMsg"]}
> The workflow proceeds after these errors have been detected.
> This is an automatically generated email. Please do not reply.
> {code}
> To draft appealing emails, its necessary to provide text editor for email
> subjects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20706) Workflow manager is not prompting for custom properties if its part of an expression
[ https://issues.apache.org/jira/browse/AMBARI-20706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20706: -- Assignee: Belliraj HB > Workflow manager is not prompting for custom properties if its part of an > expression > > > Key: AMBARI-20706 > URL: https://issues.apache.org/jira/browse/AMBARI-20706 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Belliraj HB >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.2 > > > Workflow manager is not prompting for custom properties if its part of an > expression. > Workflow manager should identify all the properties and prompt them during > workflow submission. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20707) Hive Visual explain is not working on IE browser
[ https://issues.apache.org/jira/browse/AMBARI-20707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20707: -- Assignee: Pallav Kulshreshtha > Hive Visual explain is not working on IE browser > > > Key: AMBARI-20707 > URL: https://issues.apache.org/jira/browse/AMBARI-20707 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Pallav Kulshreshtha >Priority: Critical > Labels: HiveView2.0 > Fix For: trunk > > > Hive Visual explain is not working on IE 10 browser . On running the visual > explain command, only start node is shown and other nodes are not being > rendered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20708) Need to show appropriate error when views are not able to read the encrypted file
[ https://issues.apache.org/jira/browse/AMBARI-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20708: --- Fix Version/s: (was: 2.5.1) 2.5.2 > Need to show appropriate error when views are not able to read the encrypted > file > - > > Key: AMBARI-20708 > URL: https://issues.apache.org/jira/browse/AMBARI-20708 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: DIPAYAN BHOWMICK >Priority: Critical > Labels: HiveView2.0 > Fix For: 2.5.2 > > > Need to show appropriate error message on the UI when ambari views are not > able to read the encrypted file. > Issue Scenario 1 : Try to upload/download file from encrypted zone using > 'Files view' > Issue Scenario 2 : Try to create a table from using a file from encrypted > zone using 'Hive View' > Issue Scenario 3 : Try to access workflows from encrypted zone in 'Workflow > Manager View' > Steps to reproduce : > 1) Encrypt a folder using the steps as defined in > https://github.com/abajwa-hw/security-workshops/blob/master/Setup-TDE-23.md > 2) Add a new file to this location. > 3) Now try to access this file from different views as described in above > scenario. > UI simply fails without showing any error message. Need to show appropriate > message to the user to indicating the cause of failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20708) Need to show appropriate error when views are not able to read the encrypted file
[ https://issues.apache.org/jira/browse/AMBARI-20708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20708: -- Assignee: DIPAYAN BHOWMICK > Need to show appropriate error when views are not able to read the encrypted > file > - > > Key: AMBARI-20708 > URL: https://issues.apache.org/jira/browse/AMBARI-20708 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: DIPAYAN BHOWMICK >Priority: Critical > Labels: HiveView2.0 > Fix For: 2.5.2 > > > Need to show appropriate error message on the UI when ambari views are not > able to read the encrypted file. > Issue Scenario 1 : Try to upload/download file from encrypted zone using > 'Files view' > Issue Scenario 2 : Try to create a table from using a file from encrypted > zone using 'Hive View' > Issue Scenario 3 : Try to access workflows from encrypted zone in 'Workflow > Manager View' > Steps to reproduce : > 1) Encrypt a folder using the steps as defined in > https://github.com/abajwa-hw/security-workshops/blob/master/Setup-TDE-23.md > 2) Add a new file to this location. > 3) Now try to access this file from different views as described in above > scenario. > UI simply fails without showing any error message. Need to show appropriate > message to the user to indicating the cause of failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20709) Incorrect job completion state for pig - Intermittent issue
[ https://issues.apache.org/jira/browse/AMBARI-20709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20709: --- Fix Version/s: (was: 2.5.1) 2.5.2 > Incorrect job completion state for pig - Intermittent issue > --- > > Key: AMBARI-20709 > URL: https://issues.apache.org/jira/browse/AMBARI-20709 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Nitiraj Singh Rathore > Labels: pig-view > Fix For: 2.5.2 > > > Job state is shown incorrectly after running the pig script. Even though job > has completed successfully and script has returned the result, job state is > being shown as SUBMIT_FAILED. > I dont see any error in pig logs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20595) There is a syntax error in install script hence ambari doesn't pick the python 2.7 if system python path is not present
[
https://issues.apache.org/jira/browse/AMBARI-20595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty reassigned AMBARI-20595:
--
Assignee: Aman Poonia
> There is a syntax error in install script hence ambari doesn't pick the
> python 2.7 if system python path is not present
> ---
>
> Key: AMBARI-20595
> URL: https://issues.apache.org/jira/browse/AMBARI-20595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: trunk
>Reporter: Aman Poonia
>Assignee: Aman Poonia
>Priority: Minor
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20595.patch
>
>
> This snippet of code
> {quote}
> python_binaries=( "/usr/bin/python" "/usr/bin/python2" "/usr/bin/python2.7",
> "/usr/bin/python2.6" )
> {quote}
> The comma after "/usr/bin/python2.7", causes this path to be always invalid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20709) Incorrect job completion state for pig - Intermittent issue
[ https://issues.apache.org/jira/browse/AMBARI-20709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20709: -- Assignee: Nitiraj Singh Rathore > Incorrect job completion state for pig - Intermittent issue > --- > > Key: AMBARI-20709 > URL: https://issues.apache.org/jira/browse/AMBARI-20709 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Nitiraj Singh Rathore > Labels: pig-view > Fix For: 2.5.1 > > > Job state is shown incorrectly after running the pig script. Even though job > has completed successfully and script has returned the result, job state is > being shown as SUBMIT_FAILED. > I dont see any error in pig logs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20728) Need more appropriate text in project management window
[ https://issues.apache.org/jira/browse/AMBARI-20728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20728. Resolution: Fixed > Need more appropriate text in project management window > --- > > Key: AMBARI-20728 > URL: https://issues.apache.org/jira/browse/AMBARI-20728 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: Belliraj HB > Labels: WFD, WFM > Fix For: 2.5.1 > > > Project management window is referring the text as 'My Workflows' and 'Type > Workflow Name and Path'. > Since this contains list of workflows, coordinators and bundles, just > specifying 'workflows' would be misleading. > So need more appropriate text to represent the group of entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20727) Small fixes in Log Search
[ https://issues.apache.org/jira/browse/AMBARI-20727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20727: --- Fix Version/s: (was: 2.5.1) trunk > Small fixes in Log Search > - > > Key: AMBARI-20727 > URL: https://issues.apache.org/jira/browse/AMBARI-20727 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 2.5.1 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20727.patch > > > Remove some unused codes, suppress some warnings with annotations, fix > generics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20534) Enable Ambari builds on ARM64 and PPC
[ https://issues.apache.org/jira/browse/AMBARI-20534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003309#comment-16003309 ] Sumit Mohanty commented on AMBARI-20534: [~rshaposhnik] is this committed? CC - [~jluniya] > Enable Ambari builds on ARM64 and PPC > - > > Key: AMBARI-20534 > URL: https://issues.apache.org/jira/browse/AMBARI-20534 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-web >Affects Versions: 2.4.2 >Reporter: Roman Shaposhnik >Assignee: Roman Shaposhnik > Fix For: 2.5.1 > > Attachments: AMBARI-20534.patch.txt > > > Currently Ambari fails to build on ARM64 and PPC in big part because of > dependency on the old version of com.github.eirslett:frontend-maven-plugin > Bumping the version to 1.3 solves this issue and doesn't seem to affect the > build in any other way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20728) Need more appropriate text in project management window
[ https://issues.apache.org/jira/browse/AMBARI-20728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20728: -- Assignee: Belliraj HB > Need more appropriate text in project management window > --- > > Key: AMBARI-20728 > URL: https://issues.apache.org/jira/browse/AMBARI-20728 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: Belliraj HB > Labels: WFD, WFM > Fix For: 2.5.1 > > > Project management window is referring the text as 'My Workflows' and 'Type > Workflow Name and Path'. > Since this contains list of workflows, coordinators and bundles, just > specifying 'workflows' would be misleading. > So need more appropriate text to represent the group of entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20730) Need capability to swipe designer windows within workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20730: -- Assignee: venkat > Need capability to swipe designer windows within workflow manager > - > > Key: AMBARI-20730 > URL: https://issues.apache.org/jira/browse/AMBARI-20730 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > > This has been an ask from the customer that workflow manager should have the > capability to swipe the designer windows as supported by browser windows. > Creating this jira to track the request and this feature addition would be an > enhancement for the user experience. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20730) Need capability to swipe designer windows within workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20730. Resolution: Fixed > Need capability to swipe designer windows within workflow manager > - > > Key: AMBARI-20730 > URL: https://issues.apache.org/jira/browse/AMBARI-20730 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > > This has been an ask from the customer that workflow manager should have the > capability to swipe the designer windows as supported by browser windows. > Creating this jira to track the request and this feature addition would be an > enhancement for the user experience. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20717) Need to disable upload file option from file browser window in workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20717: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Need to disable upload file option from file browser window in workflow > manager > --- > > Key: AMBARI-20717 > URL: https://issues.apache.org/jira/browse/AMBARI-20717 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20717-trunk.patch > > > Need to disable upload file option from file browser window in workflow > manager, as this should only be used to read the files from HDFS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20549) upgrade frontend-maven-plugin to latest >= 1.3 to make use of ignore proxy feature
[
https://issues.apache.org/jira/browse/AMBARI-20549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20549:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> upgrade frontend-maven-plugin to latest >= 1.3 to make use of ignore proxy
> feature
> --
>
> Key: AMBARI-20549
> URL: https://issues.apache.org/jira/browse/AMBARI-20549
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-views, ambari-web
>Affects Versions: 2.5.1
>Reporter: Jaimin Jetly
>Assignee: venkat
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20549.patch, AMBARI-20549-trunk.01.patch,
> AMBARI-20549-trunk.patch
>
>
> frontend-maven-plugin inherits maven settings.xml proxy values, in latest
> version >=1.3 proxy settings can be ignore by setting
> 'npmInheritsProxyConfigFromMaven' to 'false'
> REF: https://github.com/eirslett/frontend-maven-plugin/pull/387
> The following files contain the plugin
> {noformat}
> ambari-admin/pom.xml
> ambari-web/pom.xml
> contrib/views/capacity-scheduler/pom.xml
> contrib/views/files/pom.xml
> contrib/views/hawq/pom.xml
> contrib/views/hive-next/pom.xml
> contrib/views/hive20/pom.xml
> contrib/views/hueambarimigration/pom.xml
> contrib/views/jobs/pom.xml
> contrib/views/pig/pom.xml
> contrib/views/wfmanager/pom.xml
> contrib/views/wfmanager/src/main/resources/ui/pom.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20474) Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread Information
[ https://issues.apache.org/jira/browse/AMBARI-20474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20474: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Log4j Pattern for Storm cluster.xml and worker.xml Does Not Include Thread > Information > -- > > Key: AMBARI-20474 > URL: https://issues.apache.org/jira/browse/AMBARI-20474 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Hugo Louro >Assignee: Hugo Louro >Priority: Critical > Fix For: trunk, 2.5.1 > > Attachments: storm_log4j_updated_config.patch > > > Add thread information to make log patterns match Storm codebase -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20509) hbase master port or hbase rest port is not populated in advance-topology.xml
[
https://issues.apache.org/jira/browse/AMBARI-20509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20509:
---
Fix Version/s: (was: 2.5.1)
> hbase master port or hbase rest port is not populated in advance-topology.xml
> -
>
> Key: AMBARI-20509
> URL: https://issues.apache.org/jira/browse/AMBARI-20509
> Project: Ambari
> Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: trunk
>
> Attachments: AMBARI-20509.001.patch, AMBARI-20509.002.patch
>
>
> hbase master port or hbase rest port is not populated in
> advance-topology.xml, port is empty, that creates invalid webhbase url in
> default topology.
> {code}
>
> WEBHBASE
> http://myhost:
>
> {code}
> this is the topology from ambari:
> {code}
>
> WEBHBASE
> http://{{hbase_master_host}}:{{hbase_master_port}}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20775) VersionAdvertised should be set to False by default in stack_tool.py
[ https://issues.apache.org/jira/browse/AMBARI-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20775: --- Resolution: Won't Fix Status: Resolved (was: Patch Available) > VersionAdvertised should be set to False by default in stack_tool.py > > > Key: AMBARI-20775 > URL: https://issues.apache.org/jira/browse/AMBARI-20775 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > Attachments: AMBARI-20775.patch > > > All the commands.json files should always contain the versionAdvertised > field. If versionAdvertised is not set in command.json then we should assume > that versionAdvertised=False when calling stack_tools.py -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20522) Add Stack Upgrade support for Druid components
[ https://issues.apache.org/jira/browse/AMBARI-20522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20522. Resolution: Fixed > Add Stack Upgrade support for Druid components > -- > > Key: AMBARI-20522 > URL: https://issues.apache.org/jira/browse/AMBARI-20522 > Project: Ambari > Issue Type: Bug > Components: stacks >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-20522.patch > > > If you install HDP 2.6 with DRUID and upgrade to HDP 2.6.x, Druid will not be > upgraded as it is not versionable currently. > This task is to make Druid versionable so that we can do an upgrade from > Druid HDP-2.6.x.y to HDP-2.6.u.v -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20795) MYSQL server install failed with "TypeError: coercing to Unicode: need string or buffer, NoneType found"
[
https://issues.apache.org/jira/browse/AMBARI-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved AMBARI-20795.
Resolution: Fixed
> MYSQL server install failed with "TypeError: coercing to Unicode: need string
> or buffer, NoneType found"
>
>
> Key: AMBARI-20795
> URL: https://issues.apache.org/jira/browse/AMBARI-20795
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Shreya Bhat
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
>
> STR
> Deploy cluster using UI
> Result: MYSQL server install failed
> std.err
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/mysql_server.py\",
> line 64, in \nMysqlServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 315, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/mysql_server.py\",
> line 32, in install\nimport params\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params.py\",
> line 27, in \nfrom params_linux import *\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py\",
> line 83, in \nstack_version_formatted =
> functions.get_stack_version('hive-server2')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_stack_version.py\",
> line 70, in get_stack_version\nif not
> os.path.exists(stack_selector_path):\n File
> \"/usr/lib/python2.7/genericpath.py\", line 18, in exists\n
> os.stat(path)\nTypeError: coercing to Unicode: need string or buffer,
> NoneType found",
> Options
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20795) MYSQL server install failed with "TypeError: coercing to Unicode: need string or buffer, NoneType found"
[
https://issues.apache.org/jira/browse/AMBARI-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty reassigned AMBARI-20795:
--
Assignee: Madhuvanthi Radhakrishnan
> MYSQL server install failed with "TypeError: coercing to Unicode: need string
> or buffer, NoneType found"
>
>
> Key: AMBARI-20795
> URL: https://issues.apache.org/jira/browse/AMBARI-20795
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Shreya Bhat
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
>
> STR
> Deploy cluster using UI
> Result: MYSQL server install failed
> std.err
> "stderr" : "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/mysql_server.py\",
> line 64, in \nMysqlServer().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 315, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/mysql_server.py\",
> line 32, in install\nimport params\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params.py\",
> line 27, in \nfrom params_linux import *\n File
> \"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py\",
> line 83, in \nstack_version_formatted =
> functions.get_stack_version('hive-server2')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_stack_version.py\",
> line 70, in get_stack_version\nif not
> os.path.exists(stack_selector_path):\n File
> \"/usr/lib/python2.7/genericpath.py\", line 18, in exists\n
> os.stat(path)\nTypeError: coercing to Unicode: need string or buffer,
> NoneType found",
> Options
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20696) Skip calling stack selector, conf selector tools for Nifi, Streamline, Registry custom services in HDP cluster
[ https://issues.apache.org/jira/browse/AMBARI-20696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20696. Resolution: Fixed > Skip calling stack selector, conf selector tools for Nifi, Streamline, > Registry custom services in HDP cluster > -- > > Key: AMBARI-20696 > URL: https://issues.apache.org/jira/browse/AMBARI-20696 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.5.1 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > Attachments: AMBARI-20696_trunk.patch > > > The custom services do not advertise any version and hence will not > participate in the HDP upgrade process. So selectors need not be called. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20796) Adding services to an existing cluster always mandates oozie to be added
[ https://issues.apache.org/jira/browse/AMBARI-20796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20796. Resolution: Won't Fix > Adding services to an existing cluster always mandates oozie to be added > > > Key: AMBARI-20796 > URL: https://issues.apache.org/jira/browse/AMBARI-20796 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Shreya Bhat >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > > STR : > 1. Deploy a cluster without oozie. > 2. Delete smartsense from cluster > 3. Click on Add service to add smartsense > There is a popup saying oozie is required by service and will be auto added. > Checking service depency under : > http://:8080/api/v1/stacks/HDP/versions/2.6/services/SMARTSENSE, > "required_services" doesn't show oozie. > Same when trying to add atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20796) Adding services to an existing cluster always mandates oozie to be added
[ https://issues.apache.org/jira/browse/AMBARI-20796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20796: -- Assignee: Madhuvanthi Radhakrishnan > Adding services to an existing cluster always mandates oozie to be added > > > Key: AMBARI-20796 > URL: https://issues.apache.org/jira/browse/AMBARI-20796 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Shreya Bhat >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.1 > > > STR : > 1. Deploy a cluster without oozie. > 2. Delete smartsense from cluster > 3. Click on Add service to add smartsense > There is a popup saying oozie is required by service and will be auto added. > Checking service depency under : > http://:8080/api/v1/stacks/HDP/versions/2.6/services/SMARTSENSE, > "required_services" doesn't show oozie. > Same when trying to add atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20800) Need to change the arrangement of the action buttons in project manager
[ https://issues.apache.org/jira/browse/AMBARI-20800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20800: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Need to change the arrangement of the action buttons in project manager > --- > > Key: AMBARI-20800 > URL: https://issues.apache.org/jira/browse/AMBARI-20800 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20800-trunk.patch > > > Need to change the arrangement of the action buttons in project manager. > While asking for confirmation to delete the workflow from history, 'Delete' > button is placed at left and 'Close' is on the right. > But its a usual practice to keep the action button on the right and less > important 'Close' button on the left. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20729) Need way to explicitly ask for workflow name
[ https://issues.apache.org/jira/browse/AMBARI-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20729. Resolution: Fixed > Need way to explicitly ask for workflow name > - > > Key: AMBARI-20729 > URL: https://issues.apache.org/jira/browse/AMBARI-20729 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20729.trunk.01.patch, AMBARI-20729-trunk.patch > > > This is a ask from lot of users where they get confused between workflow name > and workflow xml file name. > Since workflow manager is auto populating workflow name, usually forgets to > enter this manually. > And once he saves the workflow at specific path, he expects the file name to > be workflow name. > This behaviour will also damage the user experience in project manager view. > To avoid this ambiguity, workflow manager should explicitly ask for workflow > name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20800) Need to change the arrangement of the action buttons in project manager
[ https://issues.apache.org/jira/browse/AMBARI-20800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20800: -- Assignee: Supreeth Sharma > Need to change the arrangement of the action buttons in project manager > --- > > Key: AMBARI-20800 > URL: https://issues.apache.org/jira/browse/AMBARI-20800 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20800-trunk.patch > > > Need to change the arrangement of the action buttons in project manager. > While asking for confirmation to delete the workflow from history, 'Delete' > button is placed at left and 'Close' is on the right. > But its a usual practice to keep the action button on the right and less > important 'Close' button on the left. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20793) Project manager window is not opening for the second time
[ https://issues.apache.org/jira/browse/AMBARI-20793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20793: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Project manager window is not opening for the second time > - > > Key: AMBARI-20793 > URL: https://issues.apache.org/jira/browse/AMBARI-20793 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20793-trunk.patch > > > Project manager window is not opening for the second time. > Steps to reproduce : > 1) Open the project manager(Recent) window by clicking on 'More' link. > 2) When modal is opened click 'esc' button or click outside the modal window > so that modal gets closed. > 3) Now try again to open the recent tab by clicking on 'More' link. Window is > not getting opened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20794) Need to show appropriate error message while deleting the workflow history in project manager
[ https://issues.apache.org/jira/browse/AMBARI-20794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20794: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Need to show appropriate error message while deleting the workflow history in > project manager > - > > Key: AMBARI-20794 > URL: https://issues.apache.org/jira/browse/AMBARI-20794 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20794-trunk.patch > > > Need to show appropriate error message while deleting the workflow history in > project manager. > Currently when user clicks on deleting the workflow history, he is shown with > the confirmation message "Do you want to delete the draft" and once deletion > is successful, he is shown the message "Workflow Successfully Deleted" > Since this operation is not deleting the workflow, instead just deletes the > workflow history, messages should be changed appropriately to convey the > meaning of his action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20794) Need to show appropriate error message while deleting the workflow history in project manager
[ https://issues.apache.org/jira/browse/AMBARI-20794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20794: -- Assignee: Supreeth Sharma > Need to show appropriate error message while deleting the workflow history in > project manager > - > > Key: AMBARI-20794 > URL: https://issues.apache.org/jira/browse/AMBARI-20794 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20794-trunk.patch > > > Need to show appropriate error message while deleting the workflow history in > project manager. > Currently when user clicks on deleting the workflow history, he is shown with > the confirmation message "Do you want to delete the draft" and once deletion > is successful, he is shown the message "Workflow Successfully Deleted" > Since this operation is not deleting the workflow, instead just deletes the > workflow history, messages should be changed appropriately to convey the > meaning of his action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20971) Repository Resource Providers Should Expose the Repository ID by Default on Minimal Responses
Jonathan Hurley created AMBARI-20971:
Summary: Repository Resource Providers Should Expose the
Repository ID by Default on Minimal Responses
Key: AMBARI-20971
URL: https://issues.apache.org/jira/browse/AMBARI-20971
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: trunk
There are 3 resource providers which should begin exposed the repository ID by
default on all responses, even minimal responses:
- {{RepositoryResourceProvider}}
- {{RespositoryVersionResourceProvider}}
- {{CompatibleRepositoryVersionResourceProvider}}
This will allow anyone querying these endpoints to reference a repository
uniquely, instead of by version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20703) Bulk action is not functional in workflow dashboard
[ https://issues.apache.org/jira/browse/AMBARI-20703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20703: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Bulk action is not functional in workflow dashboard > --- > > Key: AMBARI-20703 > URL: https://issues.apache.org/jira/browse/AMBARI-20703 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20703-trunk.patch > > > Bulk action is not functional in workflow dashboard. > Steps to reproduce : > 1) Submit couple of workflows. > 2) Navigate to dashboard. > 3) Select 2workflow using check box. > 4) Now try to perform bulk actions. > Issue 1 : Actions should be disabled based on the current state of the > workflow > Issue 2 : Rerun option is not available in the action list > Issue 3 : Even after suspending, workflow state is still SUCCESS instead in > suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20880) Storm Log4J Regex Replacement on Upgrade Fails
[
https://issues.apache.org/jira/browse/AMBARI-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20880:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Storm Log4J Regex Replacement on Upgrade Fails
> --
>
> Key: AMBARI-20880
> URL: https://issues.apache.org/jira/browse/AMBARI-20880
> Project: Ambari
> Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.5.1
>
> Attachments: AMBARI-20880_trunk.patch
>
>
> Parameterising log4j - AMBARI-19660 - Branch 2.5, trunk
> was added to all config-upgrade.xml starting from HDP2.3 upto
> HDP2.5 to change from log4j values to parameters like storm_log_maxbackupindex
> In order to have a unique "find" key, above code uses
> {noformat}
> find :
> *fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"*
>
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
>
> ${pattern}
>
>
>
> replace :
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
>
> ${pattern}
>
>
>
> {noformat}
> This logic works well for any upgrade from HDP2.5->HDP2.x
> Because HDP2.5 inherits from Storm 1.0.1
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/1.0.1/configuration/storm-worker-log4j.xml#L116
> The above logic fails for all upgrades from HDP2.x to HDP2.5 because the
> configs are inherited from Storm 0.10.0
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-worker-log4j.xml#L115
> https://issues.apache.org/jira/browse/AMBARI-19860 - log4j directory - trunk
> The line change from
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/1.0.1/configuration/storm-worker-log4j.xml#L116
> to
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-worker-log4j.xml#L115
>
> was made in upgrade packs 2.3,2.4,2.5
> This change is not required in upgrade pack 2.5 since it already inherits
> from Storm 1.0.1
> Also, it was added under the storm_worker_log4j definition which is common
> for upgrade paths 2.3->2.4 as well which is not required. We want the log4j
> directory to change only for any upgrades happening to 2.5
> Fixes:
> 1. log4j parameterization
> HDP Upgrade packs (config-upgrade) HDP2.3,HDP2.4 should refer to Storm 0.10.0
> instead of Storm 1.0.1, for storm-worker-log4j, storm-cluster-log4j.
> a. Change the find key to exclude the dependent line for storm-worker-log4j.
> {noformat}
> find : }.%i.gz">
>
> ${pattern}
>
>
>
> replace : }.%i.gz">
>
> ${pattern}
>
>
>
> {noformat}
> b. Modify find key to refer storm-cluster-log4j content from
> common-services/STORM/0.10.0
> c. Better log message in
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigUpgradeChangeDefinition.java#L250
> 2. Resolve issues in https://hortonworks.jira.com/browse/BUG-67697
> a. Change from regex-replace to replace
> b. Remove the entry from HDP/2.5/config-upgrade.
> c. Create it as a separate entry in the config-upgrade files.
> d. Call this entry only for nonrolling-upgrade-2.5.xml and upgrade-2.5.xml
> files.
> e. Commit to 2.5.1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20883) Visual explain issues
[ https://issues.apache.org/jira/browse/AMBARI-20883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20883. Resolution: Fixed > Visual explain issues > - > > Key: AMBARI-20883 > URL: https://issues.apache.org/jira/browse/AMBARI-20883 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.1 > > Attachments: AMBARI-20883-trunk.01.patch, AMBARI-20883-trunk.patch > > > Use directed arrows rather than simple lines in visual explain and Issue in > connection lines for simple queries in visual-explain in Firefox -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20885) Convert all Ambari Views to use yarn package manager
[ https://issues.apache.org/jira/browse/AMBARI-20885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20885: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Convert all Ambari Views to use yarn package manager > > > Key: AMBARI-20885 > URL: https://issues.apache.org/jira/browse/AMBARI-20885 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.1 > > Attachments: AMBARI-20885-trunk.01.patch, > AMBARI-20885-trunk.02.patch, AMBARI-20885-trunk.03.patch, > AMBARI-20885-trunk.patch > > > Convert all Ambari Views to use yarn npm package manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20901) Improvement needed for creating ACID tables
[ https://issues.apache.org/jira/browse/AMBARI-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reopened AMBARI-20901: > Improvement needed for creating ACID tables > --- > > Key: AMBARI-20901 > URL: https://issues.apache.org/jira/browse/AMBARI-20901 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.1 > > Attachments: AMBARI-20901.branch-2.5.patch > > > Right now you need to mark a column as clustered before you try to mark the > table as transactional. > If you don't it doesn't prompt for number of buckets (which is mandatory). > Then the create will fail for reasons that are not in the exception / error. > Ideal would be if the user could choose the clustering columns when they mark > the table as transactional. Clustering is required for transactional but > transactional is not required for clustering. Right now the decoupling is > confusing. We should consider this one-way linkage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20901) Improvement needed for creating ACID tables
[ https://issues.apache.org/jira/browse/AMBARI-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-20901. Resolution: Fixed > Improvement needed for creating ACID tables > --- > > Key: AMBARI-20901 > URL: https://issues.apache.org/jira/browse/AMBARI-20901 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.1 > > Attachments: AMBARI-20901.branch-2.5.patch > > > Right now you need to mark a column as clustered before you try to mark the > table as transactional. > If you don't it doesn't prompt for number of buckets (which is mandatory). > Then the create will fail for reasons that are not in the exception / error. > Ideal would be if the user could choose the clustering columns when they mark > the table as transactional. Clustering is required for transactional but > transactional is not required for clustering. Right now the decoupling is > confusing. We should consider this one-way linkage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20902) Ambari build failure after npm to yarn package manager migration.
[ https://issues.apache.org/jira/browse/AMBARI-20902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20902: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari build failure after npm to yarn package manager migration. > - > > Key: AMBARI-20902 > URL: https://issues.apache.org/jira/browse/AMBARI-20902 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.1 > > Attachments: AMBARI-20902-trunk.patch > > > mvn clean install faills because of RAT check failure in yarn.lock files -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20545) Remove the use of legacy SSL and TLS protocol versions
[ https://issues.apache.org/jira/browse/AMBARI-20545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20545: --- Fix Version/s: (was: 2.5.1) trunk > Remove the use of legacy SSL and TLS protocol versions > -- > > Key: AMBARI-20545 > URL: https://issues.apache.org/jira/browse/AMBARI-20545 > Project: Ambari > Issue Type: Bug > Components: ambari-server, security >Affects Versions: 2.4.2 >Reporter: Andy LoPresto >Assignee: Robert Levas > Labels: security, ssl, tls > Fix For: trunk > > > I notice that the explicit enabling of various protocols still includes > SSLv2Hello and SSLv3, which are severely broken protocols with numerous known > vulnerabilities and not necessary for legacy compatibility. Even TLSv1 and > TLSv1.1 have been [discouraged since February > 2014|https://community.qualys.com/thread/12421], when all modern browsers > supported TLSv1.2. Is there any reason Ambari still needs to enable support > for these legacy protocols, and are there any other mitigating controls put > in place to prevent downgrade, brute force, padding oracle, and weak > parameter attacks against these protocols? Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20919) Change Storage of Data on Request/Stage/Task To Reduce Redundency
[ https://issues.apache.org/jira/browse/AMBARI-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20919: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Change Storage of Data on Request/Stage/Task To Reduce Redundency > - > > Key: AMBARI-20919 > URL: https://issues.apache.org/jira/browse/AMBARI-20919 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20919-2.5.patch > > > Move stage.cluster_host_info to request.cluster_host_info -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20970) Integrate StackService resource and it's subresources with swagger
[ https://issues.apache.org/jira/browse/AMBARI-20970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-20970: --- Status: Patch Available (was: Open) > Integrate StackService resource and it's subresources with swagger > -- > > Key: AMBARI-20970 > URL: https://issues.apache.org/jira/browse/AMBARI-20970 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 3.0.0 > > Attachments: AMBARI-20970-Stacks-API_v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20970) Integrate StackService resource and it's subresources with swagger
[ https://issues.apache.org/jira/browse/AMBARI-20970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-20970: --- Attachment: AMBARI-20970-Stacks-API_v2.patch > Integrate StackService resource and it's subresources with swagger > -- > > Key: AMBARI-20970 > URL: https://issues.apache.org/jira/browse/AMBARI-20970 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 3.0.0 > > Attachments: AMBARI-20970-Stacks-API_v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20969) Integrate ambari server REST APIs with Swagger
[ https://issues.apache.org/jira/browse/AMBARI-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-20969. Resolution: Duplicate > Integrate ambari server REST APIs with Swagger > -- > > Key: AMBARI-20969 > URL: https://issues.apache.org/jira/browse/AMBARI-20969 > Project: Ambari > Issue Type: Epic > Components: ambari-sever >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári > Fix For: 3.0.0 > > > Ambari server rest API's should be annotated with Swagger annotation and the > build process should generate the Rest API docs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003237#comment-16003237 ] Alejandro Fernandez commented on AMBARI-20368: -- +1 for [^AMBARI-20368-1.patch] > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.4.2, 2.5.1 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. > Maybe > there is no necessary to deal with hdfs-site about hadoop_conf_dir in > hbase.py. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20435) Integrate Ambari REST APIs with Swagger
[ https://issues.apache.org/jira/browse/AMBARI-20435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-20435: --- Description: Ambari Server REST APIs should be annotated with Swagger annotations and the build process should generate the Rest API docs. > Integrate Ambari REST APIs with Swagger > --- > > Key: AMBARI-20435 > URL: https://issues.apache.org/jira/browse/AMBARI-20435 > Project: Ambari > Issue Type: Epic > Components: ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > > Ambari Server REST APIs should be annotated with Swagger annotations and the > build process should generate the Rest API docs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20961) RBAC: Service Operator/Administrator Role don't have HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons on Web UI
[ https://issues.apache.org/jira/browse/AMBARI-20961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20961: -- Assignee: Yao Lei > RBAC: Service Operator/Administrator Role don't have > HOST.ADD_DELETE_COMPONENTS permission so we 'd better hide relevant buttons > on Web UI > -- > > Key: AMBARI-20961 > URL: https://issues.apache.org/jira/browse/AMBARI-20961 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20961.patch > > > Steps to reproduce: > 1.Create a user named test and assign Service Operator(Administrator) Role to > this user. > 2.Login with this user and open Services -> Hive -> Service Actions, the > menu include highlight items : Add Hive Metastore and Add HiveServer2. > Zookeeper,Hbase and other service also have the above issue. > Because Service Operator(Administrator) Role don't have > HOST.ADD_DELETE_COMPONENTS permission at all , we 'd better hide these buttons -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20946) Zip file with a service's "package" subdirectory is not recreated if the old zip file is removed but the archived hash file exists
[ https://issues.apache.org/jira/browse/AMBARI-20946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20946: --- Fix Version/s: (was: 2.5.0) 2.5.1 > Zip file with a service's "package" subdirectory is not recreated if the old > zip file is removed but the archived hash file exists > -- > > Key: AMBARI-20946 > URL: https://issues.apache.org/jira/browse/AMBARI-20946 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Diego Santesteban >Assignee: Diego Santesteban >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20946.patch > > Original Estimate: 4h > Time Spent: 4h > Remaining Estimate: 0h > > When Ambari recreates the archive.zip file for a service's "package" > directory (to distribute to Ambari Agents), it creates a .hash file that > checks if the archive should be recreated in the future. > If the .hash file is removed but the archive.zip is not, the archive will > always be recreated. > However, if the .hash file exists and matches the current directory's hash > (i.e. no changes have been made in the directory), Ambari won't recreate the > archive file, even if it was removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[
https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003161#comment-16003161
]
Hadoop QA commented on AMBARI-19369:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12867008/AMBARI-19369.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 12 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-metrics/ambari-metrics-common ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11575//console
This message is automatically generated.
> Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm
> sinks
> -
>
> Key: AMBARI-19369
> URL: https://issues.apache.org/jira/browse/AMBARI-19369
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics, ambari-server
>Affects Versions: 2.2.0
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19369.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector,
> currently do not support Kerberos HTTP SPNEGO authentication.
> e.g.,
> /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log:
> 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink
> (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST
> metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics,
> statusCode = 401
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20970) Integrate StackService resource and it's subresources with swagger
Balázs Bence Sári created AMBARI-20970: -- Summary: Integrate StackService resource and it's subresources with swagger Key: AMBARI-20970 URL: https://issues.apache.org/jira/browse/AMBARI-20970 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20969) Integrate ambari server REST APIs with Swagger
[ https://issues.apache.org/jira/browse/AMBARI-20969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-20969: --- Description: Ambari server rest API's should be annotated with Swagger annotation and the build process should generate the Rest API docs Summary: Integrate ambari server REST APIs with Swagger (was: Ambari server rest API's should be annotated with Swagger annotation and the build process should generate the Rest API docs) > Integrate ambari server REST APIs with Swagger > -- > > Key: AMBARI-20969 > URL: https://issues.apache.org/jira/browse/AMBARI-20969 > Project: Ambari > Issue Type: Epic > Components: ambari-sever >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári > Fix For: 3.0.0 > > > Ambari server rest API's should be annotated with Swagger annotation and the > build process should generate the Rest API docs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20969) Ambari server rest API's should be annotated with Swagger annotation and the build process should generate the Rest API docs
Balázs Bence Sári created AMBARI-20969: -- Summary: Ambari server rest API's should be annotated with Swagger annotation and the build process should generate the Rest API docs Key: AMBARI-20969 URL: https://issues.apache.org/jira/browse/AMBARI-20969 Project: Ambari Issue Type: Epic Components: ambari-sever Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20968) Pig and CapSched views are not loading in 2.4.3
[
https://issues.apache.org/jira/browse/AMBARI-20968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB updated AMBARI-20968:
--
Status: Patch Available (was: Open)
> Pig and CapSched views are not loading in 2.4.3
> ---
>
> Key: AMBARI-20968
> URL: https://issues.apache.org/jira/browse/AMBARI-20968
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.3
>Reporter: Akhil PB
>Assignee: Akhil PB
>Priority: Blocker
> Labels: system_test
> Fix For: 2.4.3
>
> Attachments: AMBARI-20968-branch-2.4.patch
>
>
> Pig and Cap sched views are not loading :
> Cap Sched :
> https://172.22.106.180:8443/#/main/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE
> Pig : https://172.22.106.180:8443/#/main/views/PIG/1.0.0/Pig
> Pig View error:
> {code:java}
> ember.js:15373 Error while processing route: splash Assertion Failed: Could
> not find "splash" template or view. Error: Assertion Failed: Could not find
> "splash" template or view.
> at EmberError
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:30819:23)
> at Object.Ember.assert
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:20433:15)
> at Class.render
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41957:17)
> at Class.renderTemplate
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/app.js:3438:10)
> at apply
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:36242:27)
> at Class.superWrapper [as renderTemplate]
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:35813:15)
> at Class.setup
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41223:16)
> at applyHook
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63552:30)
> at callHook
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63546:14)
> at handlerEnteredOrUpdated
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:62306:7)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20968) Pig and CapSched views are not loading in 2.4.3
[
https://issues.apache.org/jira/browse/AMBARI-20968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB updated AMBARI-20968:
--
Attachment: AMBARI-20968-branch-2.4.patch
> Pig and CapSched views are not loading in 2.4.3
> ---
>
> Key: AMBARI-20968
> URL: https://issues.apache.org/jira/browse/AMBARI-20968
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.3
>Reporter: Akhil PB
>Assignee: Akhil PB
>Priority: Blocker
> Labels: system_test
> Fix For: 2.4.3
>
> Attachments: AMBARI-20968-branch-2.4.patch
>
>
> Pig and Cap sched views are not loading :
> Cap Sched :
> https://172.22.106.180:8443/#/main/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE
> Pig : https://172.22.106.180:8443/#/main/views/PIG/1.0.0/Pig
> Pig View error:
> {code:java}
> ember.js:15373 Error while processing route: splash Assertion Failed: Could
> not find "splash" template or view. Error: Assertion Failed: Could not find
> "splash" template or view.
> at EmberError
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:30819:23)
> at Object.Ember.assert
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:20433:15)
> at Class.render
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41957:17)
> at Class.renderTemplate
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/app.js:3438:10)
> at apply
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:36242:27)
> at Class.superWrapper [as renderTemplate]
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:35813:15)
> at Class.setup
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41223:16)
> at applyHook
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63552:30)
> at callHook
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63546:14)
> at handlerEnteredOrUpdated
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:62306:7)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20968) Pig and CapSched views are not loading in 2.4.3
[
https://issues.apache.org/jira/browse/AMBARI-20968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil PB updated AMBARI-20968:
--
Labels: system_test (was: )
> Pig and CapSched views are not loading in 2.4.3
> ---
>
> Key: AMBARI-20968
> URL: https://issues.apache.org/jira/browse/AMBARI-20968
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.3
>Reporter: Akhil PB
>Assignee: Akhil PB
>Priority: Blocker
> Labels: system_test
> Fix For: 2.4.3
>
>
> Pig and Cap sched views are not loading :
> Cap Sched :
> https://172.22.106.180:8443/#/main/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE
> Pig : https://172.22.106.180:8443/#/main/views/PIG/1.0.0/Pig
> Pig View error:
> {code:java}
> ember.js:15373 Error while processing route: splash Assertion Failed: Could
> not find "splash" template or view. Error: Assertion Failed: Could not find
> "splash" template or view.
> at EmberError
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:30819:23)
> at Object.Ember.assert
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:20433:15)
> at Class.render
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41957:17)
> at Class.renderTemplate
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/app.js:3438:10)
> at apply
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:36242:27)
> at Class.superWrapper [as renderTemplate]
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:35813:15)
> at Class.setup
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41223:16)
> at applyHook
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63552:30)
> at callHook
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63546:14)
> at handlerEnteredOrUpdated
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:62306:7)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20968) Pig and CapSched views are not loading in 2.4.3
Akhil PB created AMBARI-20968:
-
Summary: Pig and CapSched views are not loading in 2.4.3
Key: AMBARI-20968
URL: https://issues.apache.org/jira/browse/AMBARI-20968
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.4.3
Reporter: Akhil PB
Assignee: Akhil PB
Priority: Blocker
Fix For: 2.4.3
Pig and Cap sched views are not loading :
Cap Sched :
https://172.22.106.180:8443/#/main/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE
Pig : https://172.22.106.180:8443/#/main/views/PIG/1.0.0/Pig
Pig View error:
{code:java}
ember.js:15373 Error while processing route: splash Assertion Failed: Could not
find "splash" template or view. Error: Assertion Failed: Could not find
"splash" template or view.
at EmberError
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:30819:23)
at Object.Ember.assert
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:20433:15)
at Class.render
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41957:17)
at Class.renderTemplate
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/app.js:3438:10)
at apply
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:36242:27)
at Class.superWrapper [as renderTemplate]
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:35813:15)
at Class.setup
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41223:16)
at applyHook
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63552:30)
at callHook
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63546:14)
at handlerEnteredOrUpdated
(https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:62306:7)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20891) Allow extensions to auto-link with supported stack versions
[ https://issues.apache.org/jira/browse/AMBARI-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002987#comment-16002987 ] Hudson commented on AMBARI-20891: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7446 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7446/]) AMBARI-20891 - Allow extensions to auto-link with supported stack (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aa78a1724feca81e75b5a0f82cf7b048dd2b938e]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ExtensionLinkEntity.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/repos/repoinfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HBASE/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/MAPREDUCE/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/ExtensionMetainfoXml.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HIVE/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ExtensionLinkDAO.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/ZOOKEEPER/metainfo.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ExtensionInfo.java * (edit) ambari-server/src/test/resources/extensions/EXT/0.1/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerCommonServicesTest.java * (edit) ambari-server/src/test/resources/extensions/EXT/0.2/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/global.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerMock.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hadoop-env.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hdfs-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerTest.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hdfs-log4j.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/package/dummy-script.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerMiscTest.java * (add) ambari-server/src/test/resources/extensions/EXT/0.3/services/OOZIE2/metainfo.xml * (add) ambari-server/src/test/resources/extensions/EXT/0.3/services/OOZIE2/themes/broken_theme.json * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionModule.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hbase-site.xml * (add) ambari-server/src/test/resources/extensions/EXT/0.3/metainfo.xml > Allow extensions to auto-link with supported stack versions > --- > > Key: AMBARI-20891 > URL: https://issues.apache.org/jira/browse/AMBARI-20891 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20891.patch > > > It would possible to link extensions to supported stack versions while > parsing the stacks, extensions and common-services directories. > This would allow extensions to avoid making rest API calls to set up the link. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20957) Remove cluster_version use
[
https://issues.apache.org/jira/browse/AMBARI-20957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-20957:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove cluster_version use
> --
>
> Key: AMBARI-20957
> URL: https://issues.apache.org/jira/browse/AMBARI-20957
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20957.patch
>
>
> With changes in the system for Patch and Service Upgrades, the
> {{cluster_version}} table is no longer in use and needs to be removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20938) LDAPS connections to an Active Directory when enabling Kerberos should validate the server's SSL certificate
[
https://issues.apache.org/jira/browse/AMBARI-20938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20938:
--
Status: Patch Available (was: In Progress)
> LDAPS connections to an Active Directory when enabling Kerberos should
> validate the server's SSL certificate
>
>
> Key: AMBARI-20938
> URL: https://issues.apache.org/jira/browse/AMBARI-20938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: active-directory, active_directory, kerberos, ssl
> Fix For: 2.5.2
>
> Attachments: AMBARI-20938_branch-2.5_01.patch,
> AMBARI-20938_trunk_01.patch
>
>
> LDAPS connections to an Active Directory when enabling Kerberos should
> validate the server's SSL certificate. The current implementation skips
> validation checks to help avoid SSL issues; however this is not secure. Also
> the _trusting_ SSL connection may not support the more secure SSL protocols -
> TLSv1.2.
> A flag in the {{ambari.properties}} file
> ({{kerberos.operation.verify.kdc.trust}}) should be available to allow for
> the user to select either a _trusting_ SSL connection or a validating
> (non-trusting) SSL connection to be used. The default should be to use the
> standard (non-trusting) SSL connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
