[Bug 395402] New: yast cannot install packages from cdrom in second stage of installation
https://bugzilla.novell.com/show_bug.cgi?id=395402 Summary: yast cannot install packages from cdrom in second stage of installation Product: openSUSE 11.0 Version: Beta 3plus Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers@suse.de ReportedBy: chrubis@novell.com QAContact: jsrain@novell.com Found By: --- Created an attachment (id=218876) --> (https://bugzilla.novell.com/attachment.cgi?id=218876) y2logs When installing from cd in the second stage of installation suddenly I can't install any package from cd. Installer keeps telling me that there is no cd in the drive however mounting it by hand worked fine. So I skipped kerberos configuration, that needs to install kerberos packages, finish installation, disabled cd repository and finally configured kerberos. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User ma@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c1
--- Comment #1 from Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=395402
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=395402
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c2
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c5
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=395402
Stanislav Visnovsky
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c9
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c10
--- Comment #10 from Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c11
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c12
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c13
--- Comment #13 from Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=395402
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c14
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c15
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c16
--- Comment #16 from Timo Hoenig
But c#11 suggests that there is a chance that this is reproducible - it seems that installing a package that triggers restart of dbus makes the problem to appear on installation of another package.
What package is that? We shall not restart D-Bus. At least as there isn't a strict reason for doing so. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c17
--- Comment #17 from Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c18
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=395402
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c19
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c20
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User lmuelle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c21
Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c22
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User rhafer@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c23
--- Comment #23 from Ralf Haferkamp
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c24
Ján Kupec
Having this said: I'm not responsible for applications failing at the restart of the D-Bus system bus. However, I'm happy to help if fix up applications in order to survive it. I just don't have the time to analyze this scenario, but if someone is willing to work on this, I'm happy to help.
I would like to fix this particular libzypp scenario. If you could help, it would be great if we find some time to work on that. Let's arrange that by mail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c25
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c26
--- Comment #26 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User kukuk@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c30
--- Comment #30 from Thorsten Kukuk
After the experiences of the last years please suggest a reboot after a domain join (YaST Windows Domain Membership). This is a straight and simple approach and not only required by dbus as Timo explained in comment #19. This is also required by the authentication stack (pam, nscd).
nscd: rcnscd try-restart will solve this problem. pam: that's wrong. pam always reads the config at pam_start() and throws them away with pam_end(), means for every single authentication. If not, it's an application bug. So this are no valid reasons for a reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c32
Jiří Suchomel
(In reply to comment #21 from Lars Mueller)
After the experiences of the last years please suggest a reboot after a domain join (YaST Windows Domain Membership). This is a straight and simple approach and not only required by dbus as Timo explained in comment #19. This is also required by the authentication stack (pam, nscd).
nscd: rcnscd try-restart will solve this problem.
So do we really need to restart dbus? yast2-ldap-client and yast2-samba-client currently invalidate nscd cache with "nscd -i". Maybe adding rcnscd try-restart would solve the problems? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User kukuk@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c33
--- Comment #33 from Thorsten Kukuk
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c34
--- Comment #34 from Jiří Suchomel
I forgot to mention: in all cases, the restart of dbus on _configured system_ would be removed. I guess that will leave the system in a broken state when running -ldap-client or -samba-client on an already installed system. I don't quite understand what
https://bugzilla.novell.com/show_bug.cgi?id=395402
User rhafer@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c35
--- Comment #35 from Ralf Haferkamp
From https://bugzilla.novell.com/show_bug.cgi?id=174589#c88 : "If you modify /etc/nsswitch.conf, the best is to reboot. Else you have to restart __ALL__ applications which are running at the time of modification."
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c36
--- Comment #36 from Jiří Suchomel
(In reply to comment #26 from Jiří Suchomel)
I forgot to mention: in all cases, the restart of dbus on _configured system_ would be removed. I guess that will leave the system in a broken state when running -ldap-client or -samba-client on an already installed system.
On running system, I'm showing (already now) a popup advising to reboot: "This change only affects newly created processes and not already running services. Restart your services manually or reboot the machine to enable it for all services." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User lmuelle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c37
--- Comment #37 from Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c38
Jiří Suchomel
From the YaST point, restart of the service is probably easier, since we do not have to tell user about it. Reboot is also easy itself, but I'm not sure how to show a popup about upcoming reboot when the YaST is actually already finished. Popup could be shown by a very last piece of YCP code run in the 2nd stage of installation: Lukas, do we have such code or aren't we able to guarantee it (because of add-ons changing the workflow)?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c39
Lukas Ocilka
https://bugzilla.novell.com/show_bug.cgi?id=395402
User lmuelle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c40
--- Comment #40 from Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=395402
User kukuk@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c41
--- Comment #41 from Thorsten Kukuk
https://bugzilla.novell.com/show_bug.cgi?id=395402
User lmuelle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c42
--- Comment #42 from Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=395402
User kukuk@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c43
--- Comment #43 from Thorsten Kukuk
As it's possible to change the authentication method from inside of an installed system as well, we'll see more services running in this case than those listed in comment #41.
Correct, and in that case we tell the user to reboot. But we cannot force a reboot, since we don't know what else is running and if it is possible at that time.
Also a modification of the authentication system happens very rarely. Usually this is configured _one_ time. Therefore suggesting or causing a reboot isn't an issue to the user.
It is, if it is for various reasons not possible at that time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c44
--- Comment #44 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User locilka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c45
--- Comment #45 from Lukas Ocilka
So no, a reboot at this point is inacceptable. If we cannot restart dbus/hal because of YaST2, we have to do it at the end.
That would need some additional support added to installation / installation scripts. Installation itself (Some Installation module) could write the list of services which should be restarted to the /etc/install.inf and the installation scripts (that actually call YaST and handle its return) would restart the services listed there (these scripts actually check that file for another information already). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c46
--- Comment #46 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c47
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c48
--- Comment #48 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c49
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User mvidner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c50
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c51
Jiří Suchomel
We should not restrict that to the Samba/LDAP case btw, I think LUM requires the same. (We had that discussion in the past already)
I forgot about this one: yast2-linux-user-mgmt should be updated the same way... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c52
--- Comment #52 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User chrubis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c53
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c54
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=395402
User chrubis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c55
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c56
Jiří Suchomel
participants (1)
-
bugzilla_noreply@novell.com