You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Myroslav Papirkovskyy (JIRA)" <ji...@apache.org> on 2013/07/24 15:43:49 UTC
[jira] [Commented] (AMBARI-2719) Passwordless sudo bootstrap
scenario is broken
[ https://issues.apache.org/jira/browse/AMBARI-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718366#comment-13718366 ]
Myroslav Papirkovskyy commented on AMBARI-2719:
-----------------------------------------------
+1
> Passwordless sudo bootstrap scenario is broken
> ----------------------------------------------
>
> Key: AMBARI-2719
> URL: https://issues.apache.org/jira/browse/AMBARI-2719
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.5
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Priority: Blocker
> Fix For: 1.2.5
>
> Attachments: AMBARI-2719_1.2.5.patch
>
>
> Tested on current 1.2.5 brunch. The scenario is broken because there is no sudo effect when doing scp. That's why we can't directly replace remote file when doing scp as a passwordless sudo user. But we still can copy file to some temporary directory and then make "sudo mv" it to the target dir.
> {code}
> STDOUT
> STDERR
> STDOUT
> Cluster primary OS type is redhat6 and local OS type is centos6
> STDERR
> Connection to va21.name closed.
> STDOUT
> sudo-1.8.6p3-7.el6.x86_64
> STDERR
> Connection to va21.name closed.
> STDOUT
> STDERR
> scp: /etc/yum.repos.d/ambari.repo: Permission denied
> {code}
> I'm going to revert patch https://issues.apache.org/jira/browse/AMBARI-2679 and fix the source issue in another way. The patch will be done only for 1.2.5 brunch, because for trunk we have a fully refactored bootstrap.py patch at AMBARI-2713 that has not this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira