Bugzilla – Bug 619648
Unable to add smb/cifs repository via YaST Software Repositories
Last modified: 2011-09-19 11:17:30 UTC
Created attachment 373602 [details] YaST Server and Directory Screen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.4) Gecko/20100611 SUSE/3.6.4-3.2 Firefox/3.6.4 Cannot add local network smb/cifs mount of the RC2 iso image via YaST software management. Reproducible: Always Steps to Reproduce: 1. Open YaST Software Repositories and select add. 2. Select SMB/CIFS and fill in details for server, directory and select iso image (See image YaST_Server_Directory1.png) 3. Select OK 4. Error occurs and need to press skip to continue. Actual Results: - Error encountered, unable to verify media mounted (see image YaST2-Error.png), skip and return to Server and Directory Screen.5. - Now part of the path is added into the share name?? (See image YaST_Server_Directory2.png) Expected Results: Local network smb/cifs mount point added to repository list as an iso image; iso:///?iso=openSUSE-DVD-Build0694-i586.iso&url=smb://muppet-nas200/repositories/iso/ Also expected to see four buttons (see first image), this is on a netbook ASUS 1000HE, had to work blind to find OK button (four tabs, then enter)
Created attachment 373603 [details] YaST Error
Created attachment 373604 [details] YaST Server and Directory Screen #2
I have just hit the same problem. My router hosts an update repository for 11.3 which is made available as an smb share. I can access the share from Dolphin with no problems using smb://192.168.1.1/www/opensuse/updates/11.3 However, entering the exact same url in Yast2 when adding a repository fails with this error message: Failed to mount //192.168.1.1/www on /var/adm/mount/AP_0x00000001: Unable to verify that the media was mounted According to the y2logs it mounts it successfully but then fails to find it in the mount table. Not quite sure but it looks as if the entry is there but the zypp++ process fails to match it properly I have attached the appropriate section of the y2log
Created attachment 382372 [details] y2log with the smb problem
I don't know which update fixed this but I just checked this again and it appears to work now.
OK, thank you for retesting. Closing as FIXED.
Ladislav, Sorry but I have just worked out why it started working on some of my machines. It seems to be a missing dependency because as soon as I install the base development pattern it works. On machines without this installed, it still doesn't work even with the latest updates. Thus reopening.
Really? Installing "base development" pattern? That's strange, the pattern doesn't contain anything relevant to SMB/CIFS I would say. Anyway, mounting is completely handled by libzypp. Excerpt from the log: 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] ExternalProgram.cc(start_program):221 Executing '/bin/mount' '-t' 'cifs' '-o' 'guest,ro' '//192.168.1.1/www' '/var/adm/mount/AP_0x00000001' 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] ExternalProgram.cc(start_program):373 pid 7641 launched 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] ExternalProgram.cc(checkStatus):431 Pid 7641 successfully completed 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] Mount.cc(Status):260 exit code: 0 2010-08-11 21:34:32 <1> suse113(7591) [zypp] Mount.cc(mount):156 mounted //192.168.1.1/www /var/adm/mount/AP_0x00000001 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] MediaHandler.cc(checkAttached):520 Forced check of the mount table 2010-08-11 21:34:32 <1> suse113(7591) [zypp] MediaHandler.cc(checkAttached):588 Looking for media(cifs<//192.168.1.1/www>)attached(*/var/adm/mount/AP_0x00000001) 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] MediaHandler.cc(checkAttached):595 MountEntries: { 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] MediaHandler.cc(checkAttached):595 /dev/sda10 on / type ext4 (rw,acl,user_xattr) [...] 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] MediaHandler.cc(checkAttached):595 //192.168.1.1/www/ on /var/adm/mount/AP_0x00000001 type cifs (ro,mand) 2010-08-11 21:34:32 <1> suse113(7591) [zypp++] MediaHandler.cc(checkAttached):595 } 2010-08-11 21:34:32 <2> suse113(7591) [zypp] MediaHandler.cc(checkAttached):606 Attached media not in mount table ... So the mount succeeded, but libzypp failed to verify that.
Ladislav, I agree it's strange but last night I tried to add my smb repo to one of my laptops and it wouldn't work. The only difference between it and the one on which it worked was the fact that I had installed the base development pattern on the one that worked. I installed the base pattern on the one that didn't work and "bingo", I could add the repository. Strange but true. At least it should now be easier to reproduce the error as I can image that you guys always have the base dev pattern installed by default and wouldn't have encountered this as a result...
Steve, could you figure out which particular package is needed? I suggest selecting the dev pattern, checking the installation overview and saving the list to a file. Then we could check the list of added packages and find the package which fixes the problem. (If it's not clear from the list you will be probably asked to install packages one by one to find it.) Thank you!
Ladislav, Unfortunately, I have already installed the basic dev pattern on all my machines so I won't be able to test this anymore. Well, as far as I am concerned, I have a workaround and it doesn't seem to affect too many people in the first place. Feel free to close this bug report. If I ever figure out which package(s) were the crucial ones, I'll update this report.
@Steve: Among other lines, 'grep checkAttached y2log' shows: Looking for media(cifs<//192.168.1.1/www>)attached(*/var/adm/mount/AP_0x00000001) MountEntries: { ... //192.168.1.1/www/ on /var/adm/mount/AP_0x00000001 type cifs (ro,mand) It would be interesting to know if now, as it works for you, the mount entry lines look different? If so, it's probably easy to fix the verification code even if we don't know the package that causes the change.
Created attachment 389840 [details] y2log with smb working This extract shows the smb mount working. I hope it includes all the debug info you were looking for. What I did was to remove the smb repo and then add it again. Please let me know if you need any further info. Cheers
It's the 'trailing '/' problem; media(cifs<//192.168.1.1/www <- no / vs. MountEntries: { ... //192.168.1.1/www/ <- one / *** This bug has been marked as a duplicate of bug 710269 ***