[jira] [Updated] (AMBARI-25454) API exception on trying to assign permission to user group with custom Ambari Views
[ https://issues.apache.org/jira/browse/AMBARI-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25454: --- Fix Version/s: 2.8.0 > API exception on trying to assign permission to user group with custom Ambari > Views > --- > > Key: AMBARI-25454 > URL: https://issues.apache.org/jira/browse/AMBARI-25454 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-views >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0, 2.7.6 > > Time Spent: 40m > Remaining Estimate: 0h > > Issue appears when logic trying to fetch allowed statuses for the request > scope. The problem is that views are pushed to the request scope and have no > allowance to have Ambari admin permissions. > Here are several ways to solve the problem: > - do not include views for such kind of the request to the scope > - instead of failing, give a warning to the log, and if there are no objects > left in the scope, show to the user last warning in return > The less intrusive way is to done it in a second way as first way may change > the logic of how it currently work -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25454) API exception on trying to assign permission to user group with custom Ambari Views
[ https://issues.apache.org/jira/browse/AMBARI-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25454: - Resolution: Fixed Status: Resolved (was: Patch Available) > API exception on trying to assign permission to user group with custom Ambari > Views > --- > > Key: AMBARI-25454 > URL: https://issues.apache.org/jira/browse/AMBARI-25454 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-views >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 20m > Remaining Estimate: 0h > > Issue appears when logic trying to fetch allowed statuses for the request > scope. The problem is that views are pushed to the request scope and have no > allowance to have Ambari admin permissions. > Here are several ways to solve the problem: > - do not include views for such kind of the request to the scope > - instead of failing, give a warning to the log, and if there are no objects > left in the scope, show to the user last warning in return > The less intrusive way is to done it in a second way as first way may change > the logic of how it currently work -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25454) API exception on trying to assign permission to user group with custom Ambari Views
[ https://issues.apache.org/jira/browse/AMBARI-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25454: - Status: Patch Available (was: In Progress) > API exception on trying to assign permission to user group with custom Ambari > Views > --- > > Key: AMBARI-25454 > URL: https://issues.apache.org/jira/browse/AMBARI-25454 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-views >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 10m > Remaining Estimate: 0h > > Issue appears when logic trying to fetch allowed statuses for the request > scope. The problem is that views are pushed to the request scope and have no > allowance to have Ambari admin permissions. > Here are several ways to solve the problem: > - do not include views for such kind of the request to the scope > - instead of failing, give a warning to the log, and if there are no objects > left in the scope, show to the user last warning in return > The less intrusive way is to done it in a second way as first way may change > the logic of how it currently work -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25454) API exception on trying to assign permission to user group with custom Ambari Views
[ https://issues.apache.org/jira/browse/AMBARI-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25454: Labels: pull-request-available (was: ) > API exception on trying to assign permission to user group with custom Ambari > Views > --- > > Key: AMBARI-25454 > URL: https://issues.apache.org/jira/browse/AMBARI-25454 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-views >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > > Issue appears when logic trying to fetch allowed statuses for the request > scope. The problem is that views are pushed to the request scope and have no > allowance to have Ambari admin permissions. > Here are several ways to solve the problem: > - do not include views for such kind of the request to the scope > - instead of failing, give a warning to the log, and if there are no objects > left in the scope, show to the user last warning in return > The less intrusive way is to done it in a second way as first way may change > the logic of how it currently work -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25454) API exception on trying to assign permission to user group with custom Ambari Views
[ https://issues.apache.org/jira/browse/AMBARI-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25454: - Fix Version/s: (was: trunk) 2.7.6 > API exception on trying to assign permission to user group with custom Ambari > Views > --- > > Key: AMBARI-25454 > URL: https://issues.apache.org/jira/browse/AMBARI-25454 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-views >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: 2.7.6 > > > Issue appears when logic trying to fetch allowed statuses for the request > scope. The problem is that views are pushed to the request scope and have no > allowance to have Ambari admin permissions. > Here are several ways to solve the problem: > - do not include views for such kind of the request to the scope > - instead of failing, give a warning to the log, and if there are no objects > left in the scope, show to the user last warning in return > The less intrusive way is to done it in a second way as first way may change > the logic of how it currently work -- This message was sent by Atlassian Jira (v8.3.4#803005)
