Bugzilla – Bug 537300
CIFS repository not working
Last modified: 2009-12-07 10:01:00 UTC
Created attachment 317128 [details] Content of /var/log after several attempts of authentication User-Agent: Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.6 I am installing openSUSE 11.2 Milestone 6 from a CIFS share. The installer is loaded from the CIFS share without a problem. But the installation fails during the "System analysis" screen, "Package manager initialization" phase. The installation cannot continue. The window says: "User authentication", "URL: smb://radek@192.168.1.1/suse/" and two prompts (username and password). When the username and password, which was used for downloading the installation system, is entered, the authentication fails. If it helps: My password contains numbers, upper-case and lower-case symbols. I have found a similar bug (Bug 509324), but I think this problem is slightly different, because the installer itself is loaded from the CIFS and hence there should be no problem with the share itself. Reproducible: Always
Sorry, there is a typo, which might be confusing. The window asking for username+password says: "URL: smb://radek@192.168.1.32/suse/" Like this it is consistent with the logs.
I just tested and the password gets correctly passed in /etc/install.inf via ZyppRepoURL=smb://username:passwd@servername/share/path So, looks like a bug in yast to me.
Created attachment 318213 [details] YaST logs with FTP installation I've just tried Milestone 7 via FTP. The error is the same as with CIFS: Installer loads fine, but the repository is not accessible.
c#3, yes, but in the CIFS case the cause was different: most probably bug #547354. In the FTP case, the bug was in the metadata, so it makes no sense to investigate that now. Radomir, i'll close this bug as duplicate of bug 547354 now. If it happens again with libzypp>=6.21.3 and the hint in bug 547354, comment #10 does not help, please file a new report with fresh logs. Thanx! *** This bug has been marked as a duplicate of bug 547354 ***