Bug 862521 - Fedora18:Alpha:Login to anaconda shell prompt during installation is not possible
Fedora18:Alpha:Login to anaconda shell prompt during installation is not poss...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
18
ppc64 All
unspecified Severity urgent
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-03 02:40 EDT by IBM Bug Proxy
Modified: 2013-01-09 21:23 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-03 11:57:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
installation-log-for-anaconda-sshd.txt (281.75 KB, text/plain)
2012-10-03 02:41 EDT, IBM Bug Proxy
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
IBM Linux Technology Center 85593 None None None 2012-10-03 02:40:56 EDT

  None (edit)
Description IBM Bug Proxy 2012-10-03 02:40:55 EDT
Problem Description
-----------------------------
While doing installation of Fedora 18 PPC64 on P7 LPAR using VNC method  , noticed it is not allowing to login to the ssh session to collect anaconda log during any issue occurred.

--- Collected from installation Console ---
...
Starting installer, one moment...
anaconda 18.6.7 for Fedora 18-Alpha (pre-release) started.
09:36:13 Starting VNC...
09:36:14 The VNC server is now running.
09:36:14 
WARNING!!! VNC server running with NO PASSWORD!
You can use the vncpassword=<password> boot option
if you would like to secure the server.
09:36:14 Please manually connect your vnc client to miz04.austin.ibm.com:1 (9.3.110.196) to begin the install.
(anaconda:795): Gtk-WARNING **: Overriding tab label for notebook
(anaconda:795): Gtk-WARNING **: Unknown property: GtkGrid.n-columns
(anaconda:795): Gtk-WARNING **: Unknown property: GtkGrid.n-columns
Thu Sep 27 00:41:27 HADT 2012
Thu Sep 27 00:41:27 HADT 2012
Thu Sep 27 00:41:27 HADT 2012
(anaconda:795): Gtk-WARNING **: Overriding tab label for notebook
(anaconda:795): Gtk-WARNING **: Overriding tab label for notebook
[anaconda] 1:main* 2:shell  3:log  4:storage-log  5:program-log                 

We can see at last line , there are multiple options to get into different environment , but none of the option is working & it is not going to anaconda shell prompt at all.

Even if ssh to the server is not happening even if it pings successfully.
You can see the below findings:

$ ping 9.3.110.196
PING 9.3.110.196 (9.3.110.196) 56(84) bytes of data.
64 bytes from 9.3.110.196: icmp_seq=1 ttl=49 time=270 ms
64 bytes from 9.3.110.196: icmp_seq=2 ttl=49 time=274 ms

$ ssh root@9.3.110.196
ssh: connect to host 9.3.110.196 port 22: Connection refused


--- Steps to reproduce ---
1) Virtual DVD boot using command line parameters.
boot:linux ip=9.3.110.196::9.3.110.1:255.255.255.0:miz02.austin.ibm.com:eth0:none nameserver=9.0.9.1 vnc noipv6 sshd=1 debug rd.debug
2) Once it displays vnc session is ready , we can proceed for installation.
3) During installation process ,we can try to login to the anaconda shell prompt,  Either by pressing enter / pressing keys like 1:main* 2:shell  3:log  4:storage-log  5:program-log 
   Or, by trying ssh root@serverip.
We may notice all attempt will fail.

Attached full installation log file as named "installation-log-for-anaconda-sshd.txt" to the bugzilla.
Comment 1 IBM Bug Proxy 2012-10-03 02:41:11 EDT
Created attachment 620633 [details]
installation-log-for-anaconda-sshd.txt
Comment 2 IBM Bug Proxy 2012-10-03 10:51:43 EDT
------- Comment From clnperez@us.ibm.com 2012-10-03 14:45 EDT-------
Rejecting on our side as NOTABUG. There was a miscommunication. Sorry for the noise.
Comment 3 Jesse Keating 2012-10-03 11:45:18 EDT
You're seeing tmux on the console screen.  If you use ^b 2  (that's CONTROL+b then the number 2) do you then get to the shell?

ssh is disabled by default, you'll have to pass "inst.sshd" as a boot parameter in order to have the daemon started.  Note, I can't recall if it's fixed in alpha or just after, but there was a bug preventing the sshd parameter from working correctly.  Recently nightly composes do have this fixed.

Note You need to log in before you can comment on or make changes to this bug.