[jira] [Created] (AMBARI-25485) Change authentication method from get to post
Dmytro Vitiuk created AMBARI-25485:
--
Summary: Change authentication method from get to post
Key: AMBARI-25485
URL: https://issues.apache.org/jira/browse/AMBARI-25485
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.5
Reporter: Dmytro Vitiuk
Fix For: 2.7.6
Currently we are using GET method while login:
GET
api/v1/users/$
{username}
We need to change it to post.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25485) Change authentication method from get to post
[
https://issues.apache.org/jira/browse/AMBARI-25485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25485:
Labels: pull-request-available (was: )
> Change authentication method from get to post
> -
>
> Key: AMBARI-25485
> URL: https://issues.apache.org/jira/browse/AMBARI-25485
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: Dmytro Vitiuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.6
>
>
> Currently we are using GET method while login:
> GET
> api/v1/users/$
> {username}
> We need to change it to post.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (AMBARI-23816) Change Installation on Agent for Mpack package names
[
https://issues.apache.org/jira/browse/AMBARI-23816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko resolved AMBARI-23816.
--
Resolution: Abandoned
> Change Installation on Agent for Mpack package names
>
>
> Key: AMBARI-23816
> URL: https://issues.apache.org/jira/browse/AMBARI-23816
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 3.0.0
>
>
> Installation on python boils down to just {{yum install $\{package}}} since
> mpacks are supposed to provide the EXACT package name and version to install.
> We no longer need to do {{hdp-select}} magic to get the right package name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (AMBARI-24726) Remove outdated functions.list_ambari_managed_repos module
[ https://issues.apache.org/jira/browse/AMBARI-24726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-24726. -- Resolution: Abandoned > Remove outdated functions.list_ambari_managed_repos module > -- > > Key: AMBARI-24726 > URL: https://issues.apache.org/jira/browse/AMBARI-24726 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 40m > Remaining Estimate: 0h > > code cleanup -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-21192) Move Gson singleton instance from StageUtils to JsonUtils
[ https://issues.apache.org/jira/browse/AMBARI-21192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-21192. -- Resolution: Abandoned > Move Gson singleton instance from StageUtils to JsonUtils > - > > Key: AMBARI-21192 > URL: https://issues.apache.org/jira/browse/AMBARI-21192 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: trunk > > > Gson semantically belongs to JsonUtils and have no real relation to set of > functions which working on StageLevel, thus clases not involved with Stage > work shouldn't import StageUtils functionality to be able to de-serialize json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-24741) Update simplejson to newest with speedup bindings to python2.7 and PyUnicodeUCS4/PyUnicodeUCS2 variations
[ https://issues.apache.org/jira/browse/AMBARI-24741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-24741: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update simplejson to newest with speedup bindings to python2.7 and > PyUnicodeUCS4/PyUnicodeUCS2 variations > - > > Key: AMBARI-24741 > URL: https://issues.apache.org/jira/browse/AMBARI-24741 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Current version of simlejson budled with Ambari doesn't provide performance > boost, as speedup lib is linked with libpython2.6, which caused slowness on > cluster deployments and increasing the overall CPU resource usage. > Simplejson need to be updated to support python 2.7, specially speedup > binding. As we supporting various distribs, we need to provide > PyUnicodeUCS4/PyUnicodeUCS2 lib variations as well. In the future we need > separate lib for ibm ppc > In addition, logging functionality should be added to agent, which will > notify if the boost is used. > The way how logging should be done: > on Agent start with message like: "Available boosts for: simplejson, > subproccess32" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25072) Remove stack packages and installed by them dependencies ( yum; centos/rhel 7)
[ https://issues.apache.org/jira/browse/AMBARI-25072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25072. -- Resolution: Abandoned > Remove stack packages and installed by them dependencies ( yum; centos/rhel 7) > -- > > Key: AMBARI-25072 > URL: https://issues.apache.org/jira/browse/AMBARI-25072 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: trunk > > > Goals: > - Determine a best way to remove installed with stack packages and their > dependencies > - Enable stack removal for yum enabled distros > - Enable stack removal feature API -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25073) Enable stack removal through web client (UI)
[ https://issues.apache.org/jira/browse/AMBARI-25073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25073. -- Resolution: Abandoned > Enable stack removal through web client (UI) > > > Key: AMBARI-25073 > URL: https://issues.apache.org/jira/browse/AMBARI-25073 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: trunk > > > Change the way how Admin View determine that stack could be removed. > For that, > ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js#isDeletable > should be changed to consume changes made in AMBARI-25071 (i.e. use new > provided flag with the repository) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25071) The way to determine if repository is removable
[ https://issues.apache.org/jira/browse/AMBARI-25071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25071. -- Resolution: Abandoned > The way to determine if repository is removable > --- > > Key: AMBARI-25071 > URL: https://issues.apache.org/jira/browse/AMBARI-25071 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: trunk > > > With possibility to removing no needed or not yet already used repositories, > we need to provide to the world the information about it "removability". > Previously we had 1 factor, which tells that repo could be removed - it were > not installed and not present on any host. Now it would be more complex: > - We will allow to uninstall any non-current repo except revertable things > like hotfixes, patches incl. base branch to which they were applied > Due to more complex nature of remove possibility, we need to provide this > info alongside with the repositories information through API, so UI would be > able to not hard-code this logic on own side. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25074) Enable repository removal for apt and zypper base systems
[ https://issues.apache.org/jira/browse/AMBARI-25074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25074. -- Resolution: Abandoned > Enable repository removal for apt and zypper base systems > - > > Key: AMBARI-25074 > URL: https://issues.apache.org/jira/browse/AMBARI-25074 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-sever >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: trunk > > > Enable stack package removal with their dependencies for APT and ZYPPER based > systems -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25070) Remove old stack versions
[ https://issues.apache.org/jira/browse/AMBARI-25070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25070. -- Resolution: Abandoned > Remove old stack versions > - > > Key: AMBARI-25070 > URL: https://issues.apache.org/jira/browse/AMBARI-25070 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Fix For: trunk > > > Add possibility to Ambari to clean/remove rolling upgrade leftovers after the > cluster upgrade has been tested. In addition to 'yum erase', need to consider > any hdp-select operation that needs to be performed as well as the version > needs to be de-registered from Ambari. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-24547) A foreign key constraint fails when deleting a cluster from ambari
[
https://issues.apache.org/jira/browse/AMBARI-24547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-24547:
-
Resolution: Won't Do
Status: Resolved (was: Patch Available)
Closed due to inactivity
> A foreign key constraint fails when deleting a cluster from ambari
> --
>
> Key: AMBARI-24547
> URL: https://issues.apache.org/jira/browse/AMBARI-24547
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: yangqk
>Assignee: Dmytro Grinenko
>Priority: Critical
> Labels: ambari-server, pull-request-available
> Attachments: 0001-AMBARI-24547.patch
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> when deleting a cluster which has been called some schedule requests, ambari
> server will reponse 500 , ambari-server.log has a exception like this:
> {code:java}
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Cannot delete or update a parent row: a foreign ke
> y constraint fails (`aquila`.`request`, CONSTRAINT `FK_request_schedule_id`
> FOREIGN KEY (`request_schedule_id`) REFERENCES `requestschedule`
> (`schedule_id`))
> Error Code: 1451
> Call: DELETE FROM requestschedule WHERE (schedule_id = ?)
> bind => [1 parameter bound]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (AMBARI-25468) Kerberos keytab injection to the agent commands is slow
[ https://issues.apache.org/jira/browse/AMBARI-25468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25468. -- Resolution: Duplicate dup of AMBARI-25479 > Kerberos keytab injection to the agent commands is slow > --- > > Key: AMBARI-25468 > URL: https://issues.apache.org/jira/browse/AMBARI-25468 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.4 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.7.6 > > > During test on a big cluster were found that refreshing keytabs operation > takes a long amount of time. The result shows the slowness in injectKeytab > operation caused at the AgentPublishCommands class. > The estimation before looks like 54 mins in total: > ~36 mins -> getKerberosDescriptor > ~18 mins -> getClusterHostInfo -- This message was sent by Atlassian Jira (v8.3.4#803005)
