You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Boone, Jon" <Jo...@comcast.com> on 2018/10/16 20:44:45 UTC
Re: [EXTERNAL] [jira] [Created] (HADOOP-15802) start-build-env.sh
creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry
Greetings.
I opened this Bug and have subsequently provided a patch, but the overall score was -1 due to no new tests being added. Can someone help me understand how to contribute a test for the start-build-env.sh script?
--jon
On 9/28/18, 8:44 PM, "Jon Boone (JIRA)" <ji...@apache.org> wrote:
Jon Boone created HADOOP-15802:
----------------------------------
Summary: start-build-env.sh creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry
Key: HADOOP-15802
URL: https://issues.apache.org/jira/browse/HADOOP-15802
Project: Hadoop Common
Issue Type: Bug
Components: common
Environment: Ubuntu 18.04 x86_64 running in a VM with 4 CPUs / 8 GBs RAM / 128 GB disk.
Reporter: Jon Boone
In my Ubuntu 18.04 dev VM, I cloned the hadoop repo and ran the start-build-env.sh script. Once the docker build was completed and the container running, I tried to sudo and it failed. Upon investigation, I discovered that it was creating an entry in /etc/sudoers.d/hadoop-build-${USER_ID} that contained the characters '\t' rather than a tab.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org