Bug 4356

Summary: Cannot register service: RPC: Authentication error while booting qemu using <core-image-sato-arch.rootfs.tar.bz2>
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Saurav Kumar Gupta <sauravkg>
Component: virtual machinesAssignee: Saul Wold <sgw>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Medium+ CC: sgw
Version: 1.4   
Target Milestone: 1.4.1   
Hardware: x86   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Saurav Kumar Gupta 2013-04-19 14:25:11 UTC
While booting qemu (for arm, x86 and x86-64) using following command 

1. runqemu-extract-sdk <core-image-sato-arch.rootfs.tar.bz2> rootfs
2. runqemu nfs <kernel> rootfs

Following error is appearing
-----------------------------
"Cannot register service: RPC: Authentication error; why = Client credential too weak"

Detailed Log:
-----------

>runqemu nfs  /opt/va/releases/20130418-1/zImage-qemuarm.bin ./rootfs                                        

Assuming ./rootfs is an nfs rootfs                                                          
Set MACHINE to [qemuarm] based on kernel [/opt/va/releases/20130418-1/zImage-qemuarm.bin]
                                                                                            
Continuing with the following parameters:                                                   
KERNEL: [/opt/va/releases/20130418-1/zImage-qemuarm.bin]                                 
ROOTFS: [./rootfs]                                                                          
FSTYPE: [nfs]                                                                               
Acquiring lockfile for tap0...                                                              
Using preconfigured tap device 'tap0'                                                       
runqemu-export-rootfs restart ./rootfs                                                      
No PID file, not stopping rpc.mountd                                                        
No PID file, not stopping rpc.nfsd                                                         
Creating exports file...                                                                    
Starting User Mode rpc.mountd                                                               
  /opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr/bin/pseudo -P /opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr /opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr/sbin/rpc.mountd --allow-non-root --mount-pid /home/yocto/.runqemu-sdk/mount0.pid -f /home/yocto/.runqemu-sdk/exports0 --rmtab /home/yocto/.runqemu-sdk/rmtab0 --prog 21111 -r -P 3048
Cannot register service: RPC: Authentication error; why = Client credential too weak        
Cannot register service: RPC: Authentication error; why = Client credential too weak        
Cannot register service: RPC: Authentication error; why = Client credential too weak        
Cannot register service: RPC: Authentication error; why = Client credential too weak        
Starting User Mode nfsd                                                                     
  /opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr/bin/pseudo -P /opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr /opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr/sbin/rpc.nfsd --allow-non-root --nfs-pid /home/yocto/.runqemu-sdk/nfs0.pid -f /home/yocto/.runqemu-sdk/exports0 --prog 11111 -P 3049 -r                                              
Cannot register service: RPC: Authentication error; why = Client credential too weak        
Cannot register service: RPC: Authentication error; why = Client credential too weak        
                                                                                            
On your target please remember to add the following options for NFS                         
nfsroot=IP_ADDRESS:/opt/poky/1.4-M6-RC2-arm/rootfs,nfsvers=2,mountprog=21111,nfsprog=11111,udp                                                                                          
Running qemu-system-arm...                                                                  
/opt/poky/1.4-M6-RC2-arm/sysroots/i686-pokysdk-linux/usr/bin/qemu-system-arm -kernel /opt/va/releases/20130418-1/zImage-qemuarm.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,scrip
t=no,downscript=no -M versatilepb --no-reboot -show-cursor -usb -usbdevice wacom-tablet -no-reboot -m 128 --append "root=/dev/nfs nfsroot=192.168.7.1:./rootfs,nfsvers=2,mountprog=21111,nfsprog=11111,udp,port=3049,mountport=3048 rw ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M "
Comment 1 Saul Wold 2013-04-22 21:42:08 UTC
I think I need a little more information about your environment, I was able to run this without any issues on an Ubuntu 12.10 and Fedora 18 systems.  Can you give me more details thanks.
Comment 2 Saurav Kumar Gupta 2013-04-23 04:49:17 UTC
(In reply to comment #1)
> I think I need a little more information about your environment, I was able
> to run this without any issues on an Ubuntu 12.10 and Fedora 18 systems. 
> Can you give me more details thanks.


I executed this in open suse 12.1.
Comment 3 Saul Wold 2013-04-26 16:29:23 UTC
I still can not reproduce this, I have tested it on an OpenSuSE 12.2 machine, I wonder if there is an issue with 12.1 and rpc?  Do you have other security testting on your system than the default?  Have you enabled or changed selinux?

I don't have a 12.1 machine available.
Comment 4 Saurav Kumar Gupta 2013-04-29 13:03:48 UTC
(In reply to comment #3)
> I still can not reproduce this, I have tested it on an OpenSuSE 12.2
> machine, I wonder if there is an issue with 12.1 and rpc?  Do you have other
> security testting on your system than the default?  Have you enabled or
> changed selinux?
> 
> I don't have a 12.1 machine available.

No changes are done in default security settings. 
As you mention, even I doubt it might be a issue with open suse 12.1 and rpc because today when I tested this build in open suse 12.3, this problem is not coming.
To reproduce the problem, I suggest to use open suse12.1
Comment 5 Saul Wold 2013-06-27 17:55:49 UTC
Since this issue is isolated to Suse 12.1 and we know it's been fixed in 12.2, 
I am going to close this and recommed moving to the new OS if possible.
Another possible solution if you have root access would be to run rpcbind in 
"Insecure" mode (rpcbind -i).  You can also set it in /etc/default/rpcbind with 
OPTIONS="-w -i"