http://bugzilla.opensuse.org/show_bug.cgi?id=920175 Bug ID: 920175 Summary: yast.ssh missing dependency Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: forge.novell.com@matthias.subik.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.78.2 (KHTML, like Gecko) Version/6.1.6 Safari/537.78.2 Build Identifier: After installation of opensuse 13.2 via net.iso in a kvm environment (serial console) with autoyast, yast.ssh fails because of missing "ip" command. after installing iproute2 via normal yast (!) I can continue "first time configuration". I can't skip first configuration via yast. I can't login via (virtual) serial console, b/c the only console started is ssh. Reproducible: Always Steps to Reproduce: 1. start virtual machine booting from openSUSE-13.2-NET-x86_64.iso 2. use boot setting "console=ttyS0" or start via isolinux serial In my case I did an "minimal autoyast" install, to speed up debugging 3. serial console presents "connect via ssh and run yast.ssh" Actual Results: /usr/lib/YaST2/startup/common/network.sh: line 31: ip: command not found *** Fatal Error occured, process stopped *** - Commandline available at <Alt-F2> - Further information written to: /var/log/YaST2/y2start.log Expected Results: starting yast "first run", ignoring the missing dependency, as IPv4, IPv6, ssh and yast all function normally (and I'm already connected via network, as first run seem to have wicked normally). further annoyance is, that after installing iproute2 via yast (without .ssh), I can start the "must have" "first run" yast but get kicked out on completion. Please make the first run available on the serial console, as this would speed up the virtual deployment. Please remove the annoying and wrong reference to Alt-F2. If possible, please let systemd give a meaningful error message, if I try to start the serial-getty@ttyS0 manually before completing first-run-yast. I assume the custom IP setup code from yast can be removed, as wicked does handle ip correctly before the first run. Please do not kick out the running session, as in my case I did connect via ssh (through pam_nologin) as root, but couldn't reconnect, as ssh does not allow this. -- You are receiving this mail because: You are on the CC list for the bug.