From nobody@FreeBSD.ORG Fri Jul 23 08:08:57 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 190EB14E04; Fri, 23 Jul 1999 08:08:57 -0700 (PDT)
Message-Id: <19990723150857.190EB14E04@hub.freebsd.org>
Date: Fri, 23 Jul 1999 08:08:57 -0700 (PDT)
From: wayne@staff.msen.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: 3.1 RELEASE -> 3.2 upgrade is incomplete, leaves system unusable
X-Send-Pr-Version: www-1.0

>Number:         12777
>Category:       i386
>Synopsis:       3.1 RELEASE -> 3.2 upgrade is incomplete, leaves system unusable
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    jkh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 23 08:10:00 PDT 1999
>Closed-Date:    Mon Dec 13 08:35:22 PST 1999
>Last-Modified:  Mon Dec 13 08:41:05 PST 1999
>Originator:     Michael R. Wayne
>Release:        3.1/3.2 RELEASE
>Organization:
Msen, Inc.
>Environment:
reeBSD dns2.msen.net 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Tue May 18 04:05:08 GMT 1999     jkh@cathair:/usr/src/sys/compile/GENERIC  i386
>Description:
System was running 3.1 RELEASE, GENERIC kernel, no significant local
modifications.  Used /stand/sysinstall to upgrade.  3 issues:
1) No /kernel was installed.  Old kernel was moved to /kernel.prev,
   new kernel was in /kernel.GENERIC.  No /kernel at all.
2) sysinstall claimed to plan to reboot the machine on exit.  It did
   not.  In light of the above this is a better failure.
3) Password routines were foobarred.  logins were accepted just fine but
   it was impossible to change one's password, su to root or run sudo.
   Only solution was to reboot with console access in single user mode,
   boot kernel.GENERIC, link /kernel.GENERIC to /kernel and reboot again
>How-To-Repeat:
Install 3.1 release 
run /stand/sysinstall
choose upgrade
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Fri Jul 23 14:33:52 PDT 1999 
State-Changed-Why:  
Just to clarify, you're saying you used /stand/sysinstall as installed 
by 3.1-RELEASE to upgrade to 3.2-RELEASE? I ask because it's always been 
my understanding that you need the sysinstall supplied with any given 
release or snapshot to install that release or snapshot. The Upgrade 
option in 3.1-RELEASE sysinstall is three for those who want to upgrade 
_to_ 3.1-RELEASE, not _from_ it. :-) 


Responsible-Changed-From-To: freebsd-bugs->sheldonh 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Fri Jul 23 14:33:52 PDT 1999 
Responsible-Changed-Why:  
I'll take this one, it looks like pilot error. 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: "Michael R. Wayne" <wayne@msen.com>
Cc:  
Subject: Re: i386/12777: Using legacy sysinstall to upgrade live system 
Date: Wed, 11 Aug 1999 14:06:29 +0200

 On Tue, 10 Aug 1999 23:50:02 -0400, "Michael R. Wayne" wrote:
 
 > Well, it makes it VERY hard to upgrade servers that are many miles away.
 
 Not really. Build and install the correct sysinstall from source on the
 remote machine.
 
 > Personally, I can't imagine that it's all that hard to fix the upgrade
 > process (right now it fails to install a kernel, making the machine
 > essentially useless).
 
 You'll probably find that it's harder than you expect, because each new
 release comes out with new features that sysinstall needs to be made
 aware of.
 
 > I just wanted to build the upgrade package, not a Gig of stuff!
 > I don't care WHAT is used to upgrade, so long as it can be done
 > remotely.
 
 There _is_ no "upgrade package". Perhaps you should look at the
 FreeBSD Handbook section called "The Cutting Edge: FreeBSD-current and
 FreeBSD-stable". I think you'll be pleasantly surprised.
 
 > To the best of my knowledge, there is NO SAFE WAY to upgrade a
 > machine to a new release w/o physical access.  
 
 That's correct, but not in the way that you mean it. The problem is that
 a dud kernel will make it difficult for you to bring the machine back
 up. However, assuming the kernel is sound, upgrading from source is
 "safe".
 
 Ciao,
 Syheldon.
 
State-Changed-From-To: feedback->open 
State-Changed-By: sheldonh 
State-Changed-When: Fri Oct 1 04:54:28 PDT 1999 
State-Changed-Why:  
Feedback was provided. 


Responsible-Changed-From-To: sheldonh->jkh 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Fri Oct 1 04:54:28 PDT 1999 
Responsible-Changed-Why:  
Jordan, this is the one we discussed, where sysinstall's Upgrade 
option can be misinterpreted as a feature that allows the use of 
an exinsting installed sysinstall to upgrade the system to a  
later release of FreeBSD, for which the installed sysinstall was not 
designed. 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Mon Dec 13 08:35:22 PST 1999 
State-Changed-Why:  
A fat warning has been added to UPGRADE.TXT, which is displayed 
as soon as you select the Upgrade menu option.  That's about the 
best we can do, given that some people actually don't care too 
much about this problem, because they're prepared to do 
the fixups later 

This'll make it into 3.4-RELEASE, as rev 1.1.4.3. 
>Unformatted:
