Instead of *not* being prompted, and being permanently locked out of sudo, the user is shown a prompt asking what to do about hte differences in sudo configuration, and suggesting they use sudo.d.
In the limited case of EC2/UEC images, we can recognize that they're using an unmodified sudo file and appropriately write a sudo.d entry for them.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: sudo 1.7.4p4-5ubuntu7
ProcVersionSignature: User Name 2.6.38-8.42-virtual 2.6.38.2
Uname: Linux 2.6.38-8-virtual i686
Architecture: i386
Date: Thu Apr 21 21:51:09 2011
Ec2AMI: ami-a6f504cf
Ec2AMIManifest: ubuntu-images-us/ubuntu-maverick-10.10-i386-server-20101225.manifest.xml
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: m1.small
Ec2Kernel: aki-407d9529
Ec2Ramdisk: unavailable
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: sudo
UpgradeStatus: Upgraded to natty on 2011-04-21 (0 days ago)
VisudoCheck: /etc/sudoers: parsed OK
Binary package hint: sudo
This is a much less sever bug than bug 761689.
Instead of *not* being prompted, and being permanently locked out of sudo, the user is shown a prompt asking what to do about hte differences in sudo configuration, and suggesting they use sudo.d.
In the limited case of EC2/UEC images, we can recognize that they're using an unmodified sudo file and appropriately write a sudo.d entry for them.
ProblemType: Bug ature: User Name 2.6.38-8.42-virtual 2.6.38.2 images- us/ubuntu- maverick- 10.10-i386- server- 20101225. manifest. xml Zone: us-east-1c
DistroRelease: Ubuntu 11.04
Package: sudo 1.7.4p4-5ubuntu7
ProcVersionSign
Uname: Linux 2.6.38-8-virtual i686
Architecture: i386
Date: Thu Apr 21 21:51:09 2011
Ec2AMI: ami-a6f504cf
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-407d9529
Ec2Ramdisk: unavailable
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: sudo
UpgradeStatus: Upgraded to natty on 2011-04-21 (0 days ago)
VisudoCheck: /etc/sudoers: parsed OK