[
https://issues.apache.org/jira/browse/AMBARI-20407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922797#comment-15922797
]
Hudson commented on AMBARI-20407:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7023 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7023/])
AMBARI-20407. When agent retries commands it needs to handle credential
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=991c35b6e9c65b1f9953472bfb78a54cd556983a])
* (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
> When agent retries commands it needs to handle credential store processing
> correctly
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-20407
> URL: https://issues.apache.org/jira/browse/AMBARI-20407
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.5.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20407.patch
>
>
> Credential store handling has a one-way logic to move passwords to jceks
> files and then removing the passwords from the configs. When agent does an
> auto-retry of command execution then the initial assumption of relying on the
> existence of the "password" properties no longer holds true. This incorrectly
> disables credential store but as passwords are no longer available it results
> in broken configurations.
> The solution here is to avoid processing the password properties when command
> is an implicit retry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
