Ticket #21 (closed defect: worksforme)

Opened 6 years ago

Last modified 5 years ago

text upgrade on remote machines

Reported by: pirast Owned by: wwoods
Priority: minor Milestone: 1.1
Component: preupgrade Version: prerelease
Keywords: Cc:
Blocked By: Blocking:

Description

hi,

i just had the thought that when doing a text upgrade on a machine without x and in case you do not want to go to the machine, you could run preupgrade in text mode.

but what happens after the reboot? IMO, anaconda should start in text mode and some sshd should start. when joining the machine via ssh (network settings are taken from the install), the user should have the possibility to go on with the upgrade remotely.

Change History

comment:1 Changed 6 years ago by pirast

  • Owner changed from wwoods to skvidal
  • Component changed from preupgrade-gtk to preupgrade

comment:2 Changed 6 years ago by wwoods

  • Milestone set to 1.1
  • Status changed from new to assigned
  • Owner changed from skvidal to wwoods

Anaconda doesn't currently support text-mode remote installs over ssh. It does support graphical remote installs using VNC. You just need to add vnc to the boot commandline (in grub.conf before you reboot).

You can also do vncpassword=XXX and vncconnect=HOSTNAME. See this page for details: http://fedoraproject.org/wiki/Anaconda/Options

We could certainly add these options to the commandline when running preupgrade-cli, if the user requests it. I think that would suffice for remote upgrades.

I'm not sure what would happen if you tried to do minstg2 + VNC, though.

comment:3 Changed 6 years ago by pirast

We could certainly add these options to the commandline when running preupgrade-cli, if the user requests it. I think that would suffice for remote upgrades.

Yeah, dito. Short question (although not really part of this bug report), which app do I have to run on the machine which ip I enter in vncconnect=...?

comment:4 Changed 6 years ago by wwoods

Normally I just do vnc vncpassword=XXX and use vinagre to connect to the machine (on port 5901, not 5900).

When using vncconnect=HOST we usually use vncviewer --listen 5901.

comment:5 Changed 6 years ago by pirast

Thanks :)

comment:6 Changed 5 years ago by wwoods

  • Status changed from assigned to closed
  • Resolution set to worksforme
Note: See TracTickets for help on using tickets.