Bug 158567 - yast2: can't access CD1 on finishing SLP installation
Summary: yast2: can't access CD1 on finishing SLP installation
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 8
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Andreas Jaeger
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-16 09:41 UTC by Heiko Rommel
Modified: 2006-03-29 06:52 UTC (History)
0 users

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast2 logs (1.43 MB, application/x-bzip2)
2006-03-16 09:42 UTC, Heiko Rommel 		Details
ldap.conf (316 bytes, text/plain)
2006-03-16 09:42 UTC, Heiko Rommel 		Details
nsswitch.conf (1.21 KB, text/plain)
2006-03-16 09:42 UTC, Heiko Rommel 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Rommel 2006-03-16 09:41:55 UTC 
I performed an SLP based installation of SL 10.1 beta8 on x86_64 with selection "minimal X".

When configuring the authentication type, I chose LDAP.
Some packages get installed, but then I get an error that CD1 can not be accessed.
I can't continue the installation unless I choose abort.

After that the host seems to be bind to the configured ldap server.
Comment 1 Heiko Rommel 2006-03-16 09:42:25 UTC 
Created attachment 73273 [details]
yast2 logs
Comment 2 Heiko Rommel 2006-03-16 09:42:41 UTC 
Created attachment 73274 [details]
ldap.conf
Comment 3 Heiko Rommel 2006-03-16 09:42:58 UTC 
Created attachment 73275 [details]
nsswitch.conf
Comment 4 Heiko Rommel 2006-03-16 09:43:43 UTC 
ldap seems to work:

boxer:/var/log/YaST2 # ldapsearch -x -h ldap2.suse.de -b dc=suse,dc=de uid=rommel cn
# extended LDIF
#
# LDAPv3
# base <dc=suse,dc=de> with scope subtree
# filter: uid=rommel
# requesting: cn
#

# 283, people, suse.de
dn: suseid=283,ou=people,dc=suse,dc=de
cn: Heiko Rommel

# 3283, accounts, suse.de
dn: suseid=3283,ou=accounts,dc=suse,dc=de
cn: Heiko Rommel

# search result
search: 2
result: 0 Success

# numResponses: 3
# numEntries: 2
Comment 5 Heiko Rommel 2006-03-16 09:44:34 UTC 
However, the binding does not:

boxer:~ # getent passwd rommel
boxer:~ #
Comment 6 Michael Gross 2006-03-16 13:53:24 UTC 
Which packages failed? Could still be an issue with the SLP installation sources (bug #156483). Did the system boot into the correct runlevel 5?
Comment 7 Heiko Rommel 2006-03-17 11:40:22 UTC 
I don't know exactly.
Most likely the packages that are needed for LDAP bindings.
Like pam_ldap and nss_ldap.

I just successfully installed SLES10 beta 8 for x86_64 with SLP into the same partition (which worked including the ldap configuration).
So I think it is either a problem of the SLP source or of the box product.
I currently have no time to reproduce.

It did boot into runlevel 5. However the preselection of the installer was runlevel 3 (see Bug 158571).
Comment 8 Michael Gross 2006-03-20 12:33:52 UTC 
The SLP installation source contains these packages. Redirecting to Andreas for clarification.
Comment 9 Andreas Jaeger 2006-03-20 12:48:38 UTC 
These packages might not be part of the minimal selection but should get installed from the yast2-ldap module during setup.
Comment 10 Stanislav Visnovsky 2006-03-28 11:49:15 UTC 
Jiri, just verify if the YaST module tries to install all needed packages.

If yes, there is nothing we could do more.
Comment 11 Jiří Suchomel 2006-03-28 17:01:21 UTC 
Yes it does.
Comment 12 Andreas Jaeger 2006-03-29 06:52:31 UTC 
Then let's close as WORKFSFOR Jiri.  Heiko, if you can reproduce, tell us more details...