paulhoule
sudo busted when AMI launched in Ookaboo VPC
The product works great in "AWS Classic" but when it is launched in a VPC the "sudo" command does not work because it can't resolve an IP address. This breaks all the scripts that use sudo.
Ok, this problem does not look critical.
I do this sequence
ubuntu@ip-10-0-0-130:~$ sudo touch /top-of-filesystem
sudo: unable to resolve host ip-10-0-0-130
ubuntu@ip-10-0-0-130:~$ ls -l /
total 76
drwxr-xr-x 2 root root 4096 Apr 18 17:07 bin
drwxr-xr-x 3 root root 4096 Apr 28 19:08 boot
...
drwxrwxrwt 2 root root 4096 May 21 21:12 tmp
-rw-r--r-- 1 root root 0 May 21 21:12 top-of-filesystem
drwxr-xr-x 10 root root 4096 Feb 26 03:33 usr
...
It looks like the touch command worked despite the error message from sudo.
I'll see if I can reproduce the problem with the Base AMI which is ami-d7dbc7be
It is a bug for the vendor since the problem can be reproduced with the Ubuntu AMI mentioned above. Is the problem in the current 14.04 LTS product?
ami-1d8c9574
Yes this problem is in the 14.04 LTS product with the above id. Let's hassle the vendor.
Vendor hassled: https://forums.aws.amazon.com/thread.jspa?threadID=152681