[jira] [Commented] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379916#comment-16379916 ] Hudson commented on AMBARI-22759: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #629 (See [https://builds.apache.org/job/Ambari-branch-2.6/629/]) AMBARI-22759 [Hive Views 2.0] Deleting a Saved query is Buggy (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d9b324e79d4e0b9af0a0dd7ed4fb39da01236990]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/savedqueries.js > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Assignee: venkat >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379914#comment-16379914 ] Hudson commented on AMBARI-22759: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1851 (See [https://builds.apache.org/job/Ambari-branch-2.5/1851/]) AMBARI-22759 [Hive Views 2.0] Deleting a Saved query is Buggy (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8204a151b77aa5b4bad20e11842209dfd0c34907]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/savedqueries.js > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Assignee: venkat >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23002) Cancel Button in Upload table doesnt works in Hive views 2.0
[ https://issues.apache.org/jira/browse/AMBARI-23002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379913#comment-16379913 ] Hudson commented on AMBARI-23002: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1851 (See [https://builds.apache.org/job/Ambari-branch-2.5/1851/]) AMBARI-23002 Cancel Button in Upload table doesnt works in Hive views (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=19733e9a8bce85b33a642624db99d9461256a49e]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/upload-table.js > Cancel Button in Upload table doesnt works in Hive views 2.0 > > > Key: AMBARI-23002 > URL: https://issues.apache.org/jira/browse/AMBARI-23002 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: Ambari, ambari-views, hive-view, pull-request-available > Attachments: hive views cancel issue.png > > Time Spent: 2.5h > Remaining Estimate: 0h > > *Steps to reproduce :* > 1) Open Hive Views 2.0 > 2) navigate to *Tables* Tab > 3) click on *+* button > 4) click on *Upload Table* button > 5) Click on *cancel* button that appears along with create button , its > throws a *script error* and no action is performed > Attached screen shot of the error > [screenshot of > issue|https://issues.apache.org/jira/secure/attachment/12910750/hive%20views%20cancel%20issue.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23103:
-
Status: Patch Available (was: In Progress)
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23103:
Labels: pull-request-available (was: )
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23103:
-
Attachment: AMBARI-23103.patch
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
Mugdha Varadkar created AMBARI-23103:
Summary: Adding Stack feature constant for Ranger and Ranger KMS
services
Key: AMBARI-23103
URL: https://issues.apache.org/jira/browse/AMBARI-23103
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: trunk
Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23102) start-build-env.sh failed in MacOS due to mount volume permissions
[
https://issues.apache.org/jira/browse/AMBARI-23102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23102:
Labels: pull-request-available (was: )
> start-build-env.sh failed in MacOS due to mount volume permissions
> --
>
> Key: AMBARI-23102
> URL: https://issues.apache.org/jira/browse/AMBARI-23102
> Project: Ambari
> Issue Type: Bug
>Reporter: Thai Bui
>Priority: Minor
> Labels: pull-request-available
>
> Currently, start-build-env.sh doesn't work if the host OS is MacOS and the
> docker container is run as any user other than root. This is because the
> ~/.m2 is mounted as `root` user under the home directory of a docker user
> (such as jane.doe).
> For example:
> {noformat}
> centos6:~/src $ ls -lah ~/.m2/
> total 20K
> drwxr-xr-x 1 1000 ftp 238 Jan 22 16:32 .
> drwx-- 5 thai.bui games 4.0K Feb 27 19:53 ..
> drwxr-xr-x 1 1000 ftp 4.6K Feb 27 19:52 repository
> -rw-r--r-- 1 1000 ftp 3.0K Aug 8 2017 settings.old{noformat}
> This causes maven to fail because it can't write to the ~/.m2/repository. I'm
> adding an option to ./start-build-env.sh to run as root to fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23102) start-build-env.sh failed in MacOS due to mount volume permissions
[
https://issues.apache.org/jira/browse/AMBARI-23102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thai Bui updated AMBARI-23102:
--
Summary: start-build-env.sh failed in MacOS due to mount volume permissions
(was: start-build-env.sh failed in macos due to mount volume permissions)
> start-build-env.sh failed in MacOS due to mount volume permissions
> --
>
> Key: AMBARI-23102
> URL: https://issues.apache.org/jira/browse/AMBARI-23102
> Project: Ambari
> Issue Type: Bug
>Reporter: Thai Bui
>Priority: Minor
>
> Currently, start-build-env.sh doesn't work if the host OS is MacOS and the
> docker container is run as any user other than root. This is because the
> ~/.m2 is mounted as `root` user under the home directory of a docker user
> (such as jane.doe).
> For example:
> {noformat}
> centos6:~/src $ ls -lah ~/.m2/
> total 20K
> drwxr-xr-x 1 1000 ftp 238 Jan 22 16:32 .
> drwx-- 5 thai.bui games 4.0K Feb 27 19:53 ..
> drwxr-xr-x 1 1000 ftp 4.6K Feb 27 19:52 repository
> -rw-r--r-- 1 1000 ftp 3.0K Aug 8 2017 settings.old{noformat}
> This causes maven to fail because it can't write to the ~/.m2/repository. I'm
> adding an option to ./start-build-env.sh to run as root to fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23102) start-build-env.sh failed in macos due to mount volume permissions
Thai Bui created AMBARI-23102:
-
Summary: start-build-env.sh failed in macos due to mount volume
permissions
Key: AMBARI-23102
URL: https://issues.apache.org/jira/browse/AMBARI-23102
Project: Ambari
Issue Type: Bug
Reporter: Thai Bui
Currently, start-build-env.sh doesn't work if the host OS is MacOS and the
docker container is run as any user other than root. This is because the ~/.m2
is mounted as `root` user under the home directory of a docker user (such as
jane.doe).
For example:
{noformat}
centos6:~/src $ ls -lah ~/.m2/
total 20K
drwxr-xr-x 1 1000 ftp 238 Jan 22 16:32 .
drwx-- 5 thai.bui games 4.0K Feb 27 19:53 ..
drwxr-xr-x 1 1000 ftp 4.6K Feb 27 19:52 repository
-rw-r--r-- 1 1000 ftp 3.0K Aug 8 2017 settings.old{noformat}
This causes maven to fail because it can't write to the ~/.m2/repository. I'm
adding an option to ./start-build-env.sh to run as root to fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23101) Rhel6: Deploy with NewMySQL for Hive fails
[ https://issues.apache.org/jira/browse/AMBARI-23101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23101: Labels: pull-request-available (was: ) > Rhel6: Deploy with NewMySQL for Hive fails > -- > > Key: AMBARI-23101 > URL: https://issues.apache.org/jira/browse/AMBARI-23101 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.5.0 > > Attachments: AMBARI-23101.patch, AMBARI-23101.patch, > AMBARI-23101.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23101) Rhel6: Deploy with NewMySQL for Hive fails
[ https://issues.apache.org/jira/browse/AMBARI-23101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23101: - Attachment: AMBARI-23101.patch > Rhel6: Deploy with NewMySQL for Hive fails > -- > > Key: AMBARI-23101 > URL: https://issues.apache.org/jira/browse/AMBARI-23101 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.5.0 > > Attachments: AMBARI-23101.patch, AMBARI-23101.patch, > AMBARI-23101.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23100) Merge branch-3.0-ams onto trunk.
[ https://issues.apache.org/jira/browse/AMBARI-23100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23100: Labels: pull-request-available (was: ) > Merge branch-3.0-ams onto trunk. > - > > Key: AMBARI-23100 > URL: https://issues.apache.org/jira/browse/AMBARI-23100 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23101) Rhel6: Deploy with NewMySQL for Hive fails
[ https://issues.apache.org/jira/browse/AMBARI-23101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23101: - Attachment: AMBARI-23101.patch > Rhel6: Deploy with NewMySQL for Hive fails > -- > > Key: AMBARI-23101 > URL: https://issues.apache.org/jira/browse/AMBARI-23101 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.5.0 > > Attachments: AMBARI-23101.patch, AMBARI-23101.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23101) Rhel6: Deploy with NewMySQL for Hive fails
Andrew Onischuk created AMBARI-23101: Summary: Rhel6: Deploy with NewMySQL for Hive fails Key: AMBARI-23101 URL: https://issues.apache.org/jira/browse/AMBARI-23101 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.5.0 Attachments: AMBARI-23101.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23101) Rhel6: Deploy with NewMySQL for Hive fails
[ https://issues.apache.org/jira/browse/AMBARI-23101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23101: - Attachment: AMBARI-23101.patch > Rhel6: Deploy with NewMySQL for Hive fails > -- > > Key: AMBARI-23101 > URL: https://issues.apache.org/jira/browse/AMBARI-23101 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.5.0 > > Attachments: AMBARI-23101.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23101) Rhel6: Deploy with NewMySQL for Hive fails
[ https://issues.apache.org/jira/browse/AMBARI-23101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23101: - Status: Patch Available (was: Open) > Rhel6: Deploy with NewMySQL for Hive fails > -- > > Key: AMBARI-23101 > URL: https://issues.apache.org/jira/browse/AMBARI-23101 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.5.0 > > Attachments: AMBARI-23101.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23100) Merge branch-3.0-ams onto trunk.
[ https://issues.apache.org/jira/browse/AMBARI-23100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-23100: -- Assignee: Aravindan Vijayan > Merge branch-3.0-ams onto trunk. > - > > Key: AMBARI-23100 > URL: https://issues.apache.org/jira/browse/AMBARI-23100 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23100) Merge branch-3.0-ams onto trunk.
Aravindan Vijayan created AMBARI-23100: -- Summary: Merge branch-3.0-ams onto trunk. Key: AMBARI-23100 URL: https://issues.apache.org/jira/browse/AMBARI-23100 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23099) Let custom service users to access Log Search collections
Olivér Szabó created AMBARI-23099: - Summary: Let custom service users to access Log Search collections Key: AMBARI-23099 URL: https://issues.apache.org/jira/browse/AMBARI-23099 Project: Ambari Issue Type: Bug Components: ambari-infra, ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23098) Add User Name field to Background Ops Modal
[ https://issues.apache.org/jira/browse/AMBARI-23098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23098: - Summary: Add User Name field to Background Ops Modal (was: Add User Name to Background Ops Modal) > Add User Name field to Background Ops Modal > --- > > Key: AMBARI-23098 > URL: https://issues.apache.org/jira/browse/AMBARI-23098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23098) Add User Name to Background Ops Modal
Ishan Bhatt created AMBARI-23098: Summary: Add User Name to Background Ops Modal Key: AMBARI-23098 URL: https://issues.apache.org/jira/browse/AMBARI-23098 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22781) Fix OneFS blueprint installation
[ https://issues.apache.org/jira/browse/AMBARI-22781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22781: Labels: pull-request-available (was: ) > Fix OneFS blueprint installation > > > Key: AMBARI-22781 > URL: https://issues.apache.org/jira/browse/AMBARI-22781 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23097) Log Search: knox proxy support
Olivér Szabó created AMBARI-23097: - Summary: Log Search: knox proxy support Key: AMBARI-23097 URL: https://issues.apache.org/jira/browse/AMBARI-23097 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 Add knox proxy support and update knox docker env with that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23096) Ambari needs to call refreshNodes after deleting a host that was running a datanode
Sanjeev created AMBARI-23096: Summary: Ambari needs to call refreshNodes after deleting a host that was running a datanode Key: AMBARI-23096 URL: https://issues.apache.org/jira/browse/AMBARI-23096 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Environment: Ambari 2.6.1 Reporter: Sanjeev Currently when a host(that was running a datanode) is completely deleted from the cluster, refreshnode on HDFS is not called and thus the the deleted datanode continues to show up in the HDFS NN UI. The UI is refreshed when we explicitly run refreshNodes. Ambari already has the information which slave components a given host is running, if a host being deleted is one among the hosts that was running a datanode, then deleting it should trigger refreshNodes as part of the delete workflow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23094) Ambari does not manage repositories
[ https://issues.apache.org/jira/browse/AMBARI-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379053#comment-16379053 ] Hudson commented on AMBARI-23094: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8782 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8782/]) AMBARI-23094. Ambari does not manage repositories (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=69c9fc16e665826240e49d46ad2210d2d9619513]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepoOsEntity.java > Ambari does not manage repositories > --- > > Key: AMBARI-23094 > URL: https://issues.apache.org/jira/browse/AMBARI-23094 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23094.patch, AMBARI-23094.patch, > AMBARI-23094.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > While running CI tests > > > > Traceback (most recent call last): > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", > line 283, in _call_with_retries > code, out = func(cmd, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 72, in inner > result = function(command, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do > > > > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not > managed by Ambari > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is > not managed by Ambari > 2018-02-26 12:16:14,480 - Repository for > HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari > > I checked in DB and indeed manage_repos was false, however I didn't found any > signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23084) Background Ops Modal Updates - Get user name
[ https://issues.apache.org/jira/browse/AMBARI-23084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378970#comment-16378970 ] Hudson commented on AMBARI-23084: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8781 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8781/]) AMBARI-23084 Background Ops Modal Updates - Get user name (#476) (swagle: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=723210ca5e1af42eeea7c69f914db6b391c16f0f]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestStageContainerTest.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RequestEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Request.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestStageContainer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog270Test.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql > Background Ops Modal Updates - Get user name > > > Key: AMBARI-23084 > URL: https://issues.apache.org/jira/browse/AMBARI-23084 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Endre Major >Assignee: Endre Major >Priority: Blocker > Labels: pull-request-available > Fix For: trunk > > Time Spent: 2h 40m > Remaining Estimate: 0h > > clusters/clusterName/requests/... API call to provide user name associated > with the request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23095) knoxsso.redirect.whitelist.regex should not require a port number
[
https://issues.apache.org/jira/browse/AMBARI-23095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23095:
--
Description:
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
meaning it won't work for redirects to normal HTTP and HTTPS on :80 and :443:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
{code}
Proposal is to make the port optional and validate that anything after the host
or port starts with /.
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1)(:[0-9]+)?(\/|\/.*)?$
{code}
Pull request with the change: https://github.com/apache/ambari/pull/484
was:
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
meaning it won't work for redirects to normal HTTP and HTTPS on :80 and :443:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
{code}
Proposal is to make the port optional and validate that anything after the host
or port starts with /.
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1)(:[0-9]+)?(\/|\/.*)?$
{code}
> knoxsso.redirect.whitelist.regex should not require a port number
> -
>
> Key: AMBARI-23095
> URL: https://issues.apache.org/jira/browse/AMBARI-23095
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0, trunk, 2.6.2
>Reporter: Sean Roberts
>Priority: Major
> Labels: knox, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The default 'knoxsso.redirect.whitelist.regex' is set to require a port
> number meaning it won't work for redirects to normal HTTP and HTTPS on :80
> and :443:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
> {code}
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
> {code}
> Proposal is to make the port optional and validate that anything after the
> host or port starts with /.
> {code}
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1)(:[0-9]+)?(\/|\/.*)?$
> {code}
> Pull request with the change: https://github.com/apache/ambari/pull/484
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23095) knoxsso.redirect.whitelist.regex should not require a port number
[
https://issues.apache.org/jira/browse/AMBARI-23095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23095:
Labels: knox pull-request-available (was: knox)
> knoxsso.redirect.whitelist.regex should not require a port number
> -
>
> Key: AMBARI-23095
> URL: https://issues.apache.org/jira/browse/AMBARI-23095
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0, trunk, 2.6.2
>Reporter: Sean Roberts
>Priority: Major
> Labels: knox, pull-request-available
>
> The default 'knoxsso.redirect.whitelist.regex' is set to require a port
> number meaning it won't work for redirects to normal HTTP and HTTPS on :80
> and :443:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
> {code}
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
> {code}
> Proposal is to make the port optional and validate that anything after the
> host or port starts with /.
> {code}
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1)(:[0-9]+)?(\/|\/.*)?$
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23095) knoxsso.redirect.whitelist.regex should not require a port number
[
https://issues.apache.org/jira/browse/AMBARI-23095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23095:
--
Description:
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
meaning it won't work for redirects to normal HTTP and HTTPS on :80 and :443:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
{code}
Proposal is to make the port optional and validate that anything after the host
or port starts with /.
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1)(:[0-9]+)?(\/|\/.*)?$
{code}
was:
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
meaning it won't work for redirects to normal HTTP and HTTPS on :80 and :443:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
{code}
Proposal is to make the port optional and validate that anything after the host
or port starts with /.
> knoxsso.redirect.whitelist.regex should not require a port number
> -
>
> Key: AMBARI-23095
> URL: https://issues.apache.org/jira/browse/AMBARI-23095
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0, trunk, 2.6.2
>Reporter: Sean Roberts
>Priority: Major
> Labels: knox
>
> The default 'knoxsso.redirect.whitelist.regex' is set to require a port
> number meaning it won't work for redirects to normal HTTP and HTTPS on :80
> and :443:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
> {code}
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
> {code}
> Proposal is to make the port optional and validate that anything after the
> host or port starts with /.
> {code}
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1)(:[0-9]+)?(\/|\/.*)?$
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23095) knoxsso.redirect.whitelist.regex should not require a port number
Sean Roberts created AMBARI-23095:
-
Summary: knoxsso.redirect.whitelist.regex should not require a
port number
Key: AMBARI-23095
URL: https://issues.apache.org/jira/browse/AMBARI-23095
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.0, trunk, 2.6.2
Reporter: Sean Roberts
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
meaning it won't work for redirects to normal HTTP and HTTPS on :80 and :443:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.5/services/KNOX/configuration/knoxsso-topology.xml#L109-L110
{code}
^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$
{code}
Proposal is to make the port optional and validate that anything after the host
or port starts with /.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22781) Fix OneFS blueprint installation
[ https://issues.apache.org/jira/browse/AMBARI-22781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22781: --- Fix Version/s: (was: 3.0.0) 2.7.0 > Fix OneFS blueprint installation > > > Key: AMBARI-22781 > URL: https://issues.apache.org/jira/browse/AMBARI-22781 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23094) Ambari does not manage repositories
[ https://issues.apache.org/jira/browse/AMBARI-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23094: Labels: pull-request-available (was: ) > Ambari does not manage repositories > --- > > Key: AMBARI-23094 > URL: https://issues.apache.org/jira/browse/AMBARI-23094 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23094.patch, AMBARI-23094.patch, > AMBARI-23094.patch > > > While running CI tests > > > > Traceback (most recent call last): > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", > line 283, in _call_with_retries > code, out = func(cmd, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 72, in inner > result = function(command, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do > > > > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not > managed by Ambari > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is > not managed by Ambari > 2018-02-26 12:16:14,480 - Repository for > HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari > > I checked in DB and indeed manage_repos was false, however I didn't found any > signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23094) Ambari does not manage repositories
[ https://issues.apache.org/jira/browse/AMBARI-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23094: - Attachment: AMBARI-23094.patch > Ambari does not manage repositories > --- > > Key: AMBARI-23094 > URL: https://issues.apache.org/jira/browse/AMBARI-23094 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23094.patch, AMBARI-23094.patch, > AMBARI-23094.patch > > > While running CI tests > > > > Traceback (most recent call last): > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", > line 283, in _call_with_retries > code, out = func(cmd, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 72, in inner > result = function(command, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do > > > > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not > managed by Ambari > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is > not managed by Ambari > 2018-02-26 12:16:14,480 - Repository for > HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari > > I checked in DB and indeed manage_repos was false, however I didn't found any > signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23094) Ambari does not manage repositories
[ https://issues.apache.org/jira/browse/AMBARI-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23094: - Attachment: AMBARI-23094.patch > Ambari does not manage repositories > --- > > Key: AMBARI-23094 > URL: https://issues.apache.org/jira/browse/AMBARI-23094 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23094.patch, AMBARI-23094.patch, > AMBARI-23094.patch > > > While running CI tests > > > > Traceback (most recent call last): > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", > line 283, in _call_with_retries > code, out = func(cmd, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 72, in inner > result = function(command, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do > > > > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not > managed by Ambari > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is > not managed by Ambari > 2018-02-26 12:16:14,480 - Repository for > HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari > > I checked in DB and indeed manage_repos was false, however I didn't found any > signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23094) Ambari does not manage repositories
Andrew Onischuk created AMBARI-23094: Summary: Ambari does not manage repositories Key: AMBARI-23094 URL: https://issues.apache.org/jira/browse/AMBARI-23094 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-23094.patch While running CI tests Traceback (most recent call last): File "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", line 283, in _call_with_retries code, out = func(cmd, **kwargs) File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72, in inner result = function(command, **kwargs) File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not managed by Ambari 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is not managed by Ambari 2018-02-26 12:16:14,480 - Repository for HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari I checked in DB and indeed manage_repos was false, however I didn't found any signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23094) Ambari does not manage repositories
[ https://issues.apache.org/jira/browse/AMBARI-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23094: - Status: Patch Available (was: Open) > Ambari does not manage repositories > --- > > Key: AMBARI-23094 > URL: https://issues.apache.org/jira/browse/AMBARI-23094 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23094.patch > > > While running CI tests > > > > Traceback (most recent call last): > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", > line 283, in _call_with_retries > code, out = func(cmd, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 72, in inner > result = function(command, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do > > > > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not > managed by Ambari > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is > not managed by Ambari > 2018-02-26 12:16:14,480 - Repository for > HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari > > I checked in DB and indeed manage_repos was false, however I didn't found any > signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23094) Ambari does not manage repositories
[ https://issues.apache.org/jira/browse/AMBARI-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23094: - Attachment: AMBARI-23094.patch > Ambari does not manage repositories > --- > > Key: AMBARI-23094 > URL: https://issues.apache.org/jira/browse/AMBARI-23094 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23094.patch > > > While running CI tests > > > > Traceback (most recent call last): > File > "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", > line 283, in _call_with_retries > code, out = func(cmd, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 72, in inner > result = function(command, **kwargs) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", > line 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install > hadooplzo_3_0_0_2_87' returned 1. Error: Nothing to do > > > > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0 is not > managed by Ambari > 2018-02-26 12:16:14,479 - Repository for HDP/3.0.0.2-87/HDP-3.0-GPL is > not managed by Ambari > 2018-02-26 12:16:14,480 - Repository for > HDP/3.0.0.2-87/HDP-UTILS-1.1.0.22 is not managed by Ambari > > I checked in DB and indeed manage_repos was false, however I didn't found any > signs in logs etc. that it was set to false during cluster setup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23093) Remove dependency on org.apache.zookeeper:zookeeper before version 3.4.6.2.0.0.0-579 for Ambari Server
Sandor Molnar created AMBARI-23093:
--
Summary: Remove dependency on org.apache.zookeeper:zookeeper
before version 3.4.6.2.0.0.0-579 for Ambari Server
Key: AMBARI-23093
URL: https://issues.apache.org/jira/browse/AMBARI-23093
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.6.2, 2.7.0
Remove dependency on org.apache.zookeeper:zookeeper before version
3.4.6.2.0.0.0-579 due to security concerns. See
* CVE-2017-5637 - [https://nvd.nist.gov/vuln/detail/CVE-2017-5637]
* CVE-2016-5017 - [https://nvd.nist.gov/vuln/detail/CVE-2016-5017]
{noformat}
--- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
org.apache.ambari:ambari-server:jar:2.6.1.0.0
+- org.apache.ambari:ambari-metrics-common:jar:2.6.1.0.0:compile
| \- org.apache.curator:curator-framework:jar:2.7.1:compile
| \- (org.apache.zookeeper:zookeeper:jar:3.4.6:compile - omitted for
duplicate)
+- org.apache.hadoop:hadoop-auth:jar:2.7.2:compile
| \- org.apache.zookeeper:zookeeper:jar:3.4.6:compile
\- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
+- org.apache.curator:curator-client:jar:2.7.1:compile
| \- (org.apache.zookeeper:zookeeper:jar:3.4.6:compile - omitted for
duplicate)
+- org.apache.curator:curator-recipes:jar:2.7.1:compile
| \- (org.apache.zookeeper:zookeeper:jar:3.4.6:compile - omitted for
duplicate)
\- (org.apache.zookeeper:zookeeper:jar:3.4.6:compile - omitte{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22421) Ambari upgrade is not idempotent if it fails with service not found error
[
https://issues.apache.org/jira/browse/AMBARI-22421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar resolved AMBARI-22421.
Resolution: Fixed
Fix Version/s: 2.6.2
Fixed by [~dmitriusan]; see AMBARI-22723
> Ambari upgrade is not idempotent if it fails with service not found error
> -
>
> Key: AMBARI-22421
> URL: https://issues.apache.org/jira/browse/AMBARI-22421
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Sandor Molnar
>Priority: Major
> Fix For: 2.6.2
>
>
> If Upgrade is failed with below exception and try to upgrade from that point
> after correcting the service not found issue.
> {noformat}
> 06 Nov 2017 04:31:26,823 ERROR [main] SchemaUpgradeHelper:233 - Upgrade
> failed.
> org.apache.ambari.server.ServiceNotFoundException: Service not found,
> clusterName=, serviceName=NIFI
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> 06 Nov 2017 04:31:26,826 ERROR [main] SchemaUpgradeHelper:437 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=usldwdevhdp, serviceName=NIFI
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=usldwdevhdp, serviceName=NIFI
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
> {noformat}
> Upgrade fails with below exception
> {noformat}
> INFO: Updating Ambari Server properties in ambari.properties ...
> WARNING: Can not find ambari.properties.rpmsave file from previous version,
> skipping import of settings
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> INFO: Can not find ambari-env.sh.rpmsave file from previous version, skipping
> restore of environment settings. ambari-env.sh may not include any user
> customization.
> INFO: Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)?
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> cluster_version table does not contain repo_version_id column
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: java.lang.IllegalArgumentException: cluster_version table does not
> contain repo_version_id column
> at
> org.apache.ambari.server.orm.DBAccessorImpl.getIntColumnValues(DBAccessorImpl.java:1536)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:507)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR:
[jira] [Commented] (AMBARI-23091) Zeppelin Notebook SSL credentials in Ambari UI are in plain text rather than being hidden
[ https://issues.apache.org/jira/browse/AMBARI-23091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378502#comment-16378502 ] Hudson commented on AMBARI-23091: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #628 (See [https://builds.apache.org/job/Ambari-branch-2.6/628/]) [AMBARI-23091] Zeppelin Notebook SSL credentials in Ambari UI are in (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=dc5cc669f1a536d87fa96cd0a7c02d2a00ee55f9]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/configuration/zeppelin-config.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/configuration/zeppelin-config.xml > Zeppelin Notebook SSL credentials in Ambari UI are in plain text rather than > being hidden > - > > Key: AMBARI-23091 > URL: https://issues.apache.org/jira/browse/AMBARI-23091 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Zeppelin Notebook keystore & truststore passwords appear in plain text rather > than being hidden in Ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22421) Ambari upgrade is not idempotent if it fails with service not found error
[
https://issues.apache.org/jira/browse/AMBARI-22421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar reassigned AMBARI-22421:
--
Assignee: Sandor Molnar
> Ambari upgrade is not idempotent if it fails with service not found error
> -
>
> Key: AMBARI-22421
> URL: https://issues.apache.org/jira/browse/AMBARI-22421
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Sandor Molnar
>Priority: Major
>
> If Upgrade is failed with below exception and try to upgrade from that point
> after correcting the service not found issue.
> {noformat}
> 06 Nov 2017 04:31:26,823 ERROR [main] SchemaUpgradeHelper:233 - Upgrade
> failed.
> org.apache.ambari.server.ServiceNotFoundException: Service not found,
> clusterName=, serviceName=NIFI
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> 06 Nov 2017 04:31:26,826 ERROR [main] SchemaUpgradeHelper:437 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=usldwdevhdp, serviceName=NIFI
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=usldwdevhdp, serviceName=NIFI
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
> {noformat}
> Upgrade fails with below exception
> {noformat}
> INFO: Updating Ambari Server properties in ambari.properties ...
> WARNING: Can not find ambari.properties.rpmsave file from previous version,
> skipping import of settings
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> INFO: Can not find ambari-env.sh.rpmsave file from previous version, skipping
> restore of environment settings. ambari-env.sh may not include any user
> customization.
> INFO: Fixing database objects owner
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)?
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException:
> cluster_version table does not contain repo_version_id column
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
> Caused by: java.lang.IllegalArgumentException: cluster_version table does not
> contain repo_version_id column
> at
> org.apache.ambari.server.orm.DBAccessorImpl.getIntColumnValues(DBAccessorImpl.java:1536)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:507)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {noformat}
--
This message
[jira] [Updated] (AMBARI-23091) Zeppelin Notebook SSL credentials in Ambari UI are in plain text rather than being hidden
[ https://issues.apache.org/jira/browse/AMBARI-23091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23091: Labels: pull-request-available (was: ) > Zeppelin Notebook SSL credentials in Ambari UI are in plain text rather than > being hidden > - > > Key: AMBARI-23091 > URL: https://issues.apache.org/jira/browse/AMBARI-23091 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > > Zeppelin Notebook keystore & truststore passwords appear in plain text rather > than being hidden in Ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23092) Deleting a Group from the Group detail page navigates to the Cluster Information page
[ https://issues.apache.org/jira/browse/AMBARI-23092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23092: Labels: pull-request-available (was: ) > Deleting a Group from the Group detail page navigates to the Cluster > Information page > - > > Key: AMBARI-23092 > URL: https://issues.apache.org/jira/browse/AMBARI-23092 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23092) Deleting a Group from the Group detail page navigates to the Cluster Information page
Antonenko Alexander created AMBARI-23092: Summary: Deleting a Group from the Group detail page navigates to the Cluster Information page Key: AMBARI-23092 URL: https://issues.apache.org/jira/browse/AMBARI-23092 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23092) Deleting a Group from the Group detail page navigates to the Cluster Information page
[ https://issues.apache.org/jira/browse/AMBARI-23092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23092: Assignee: Antonenko Alexander > Deleting a Group from the Group detail page navigates to the Cluster > Information page > - > > Key: AMBARI-23092 > URL: https://issues.apache.org/jira/browse/AMBARI-23092 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23091) Zeppelin Notebook SSL credentials in Ambari UI are in plain text rather than being hidden
Vitaly Brodetskyi created AMBARI-23091: -- Summary: Zeppelin Notebook SSL credentials in Ambari UI are in plain text rather than being hidden Key: AMBARI-23091 URL: https://issues.apache.org/jira/browse/AMBARI-23091 Project: Ambari Issue Type: Bug Components: ambari-sever Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Fix For: 2.6.2 Zeppelin Notebook keystore & truststore passwords appear in plain text rather than being hidden in Ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23090) Delete User button from individual user page navigates to clusterInformation page instead of Users page
[ https://issues.apache.org/jira/browse/AMBARI-23090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23090: - Status: Patch Available (was: Open) > Delete User button from individual user page navigates to clusterInformation > page instead of Users page > --- > > Key: AMBARI-23090 > URL: https://issues.apache.org/jira/browse/AMBARI-23090 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23090) Delete User button from individual user page navigates to clusterInformation page instead of Users page
[ https://issues.apache.org/jira/browse/AMBARI-23090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23090: Labels: pull-request-available (was: ) > Delete User button from individual user page navigates to clusterInformation > page instead of Users page > --- > > Key: AMBARI-23090 > URL: https://issues.apache.org/jira/browse/AMBARI-23090 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23090) Delete User button from individual user page navigates to clusterInformation page instead of Users page
Antonenko Alexander created AMBARI-23090: Summary: Delete User button from individual user page navigates to clusterInformation page instead of Users page Key: AMBARI-23090 URL: https://issues.apache.org/jira/browse/AMBARI-23090 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23090) Delete User button from individual user page navigates to clusterInformation page instead of Users page
[ https://issues.apache.org/jira/browse/AMBARI-23090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23090: Assignee: Antonenko Alexander > Delete User button from individual user page navigates to clusterInformation > page instead of Users page > --- > > Key: AMBARI-23090 > URL: https://issues.apache.org/jira/browse/AMBARI-23090 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23089) UI allows to hide current version
[ https://issues.apache.org/jira/browse/AMBARI-23089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23089: - Status: Patch Available (was: Open) > UI allows to hide current version > - > > Key: AMBARI-23089 > URL: https://issues.apache.org/jira/browse/AMBARI-23089 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23089) UI allows to hide current version
[ https://issues.apache.org/jira/browse/AMBARI-23089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23089: Labels: pull-request-available (was: ) > UI allows to hide current version > - > > Key: AMBARI-23089 > URL: https://issues.apache.org/jira/browse/AMBARI-23089 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23089) UI allows to hide current version
[ https://issues.apache.org/jira/browse/AMBARI-23089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23089: Assignee: Antonenko Alexander > UI allows to hide current version > - > > Key: AMBARI-23089 > URL: https://issues.apache.org/jira/browse/AMBARI-23089 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23089) UI allows to hide current version
Antonenko Alexander created AMBARI-23089: Summary: UI allows to hide current version Key: AMBARI-23089 URL: https://issues.apache.org/jira/browse/AMBARI-23089 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
