[
https://issues.apache.org/jira/browse/BIGTOP-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855240#comment-13855240
]
Evans Ye commented on BIGTOP-1167:
----------------------------------
Ok, Jay, I am sorry that I did not make myself clear. The bug itself has no
connection with the version of vagrant.
Let me explain this more clearly. The problem here is that we'll get following
error message when provisioning with provision.sh:
{code}
...
mkdir: Permission denied: user=root, access=WRITE,
inode="/user":hdfs:supergroup:drwxr-xr-x
...
Job Finished in 23.258 seconds
Estimated value of Pi is 4.00000000000000000000
{code}
Which is caused by executing hdfs write operations by root.
So what I'm trying to do in those patches is to clarify the shell executor and
makes user specific commands being executed successfully.
The vagrant version is only related to the solutions because we can run the
shell provisioner either by root or by vagrant.
I've tested vagrant 1.3.3, and I still got "Permission denied" when creating
the folder. So I think the question you're asking is because of the unclear
description on the bug.
Please let me know if there is something still not explained well.
Thanks for your rapid response:)
> got "Permission denied" when creating vagrant home folder in provision.sh
> -------------------------------------------------------------------------
>
> Key: BIGTOP-1167
> URL: https://issues.apache.org/jira/browse/BIGTOP-1167
> Project: Bigtop
> Issue Type: Bug
> Components: Deployment, VM
> Reporter: Evans Ye
> Priority: Minor
> Attachments: BIGTOP-1167.1.patch, BIGTOP-1167.2.patch
>
>
> By default, vagrant shell provisioner run shell scripts with superuser
> privileges. Since provision.sh do hdfs write operations by root, it get
> permission denied.
> There're two ways we can fix it.
> 1). Create vagrant's home folder by hdfs.
> 2). Let vagrant shell provisioner run the shell script without superuser
> privileges. (set privileged to false in Vagrantfile)
> It seems solution 2 is much more elegant.
> Unfortunately, the privileged setting is only available with vagrant 1.3.0+,
> and there's another issue coming up with 1.3.5+ which [failed the network
> setting in fedora|https://github.com/mitchellh/vagrant/issues/2430]. So, I
> might suggest to take solution 1 fist.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
