Project

General

Profile

Bug #1156

Upgrade from 1.2.3 to 2.0 with VMware tools installed will panic

Added by Jim Pingle almost 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Package System
Target version:
Start date:
01/03/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:
All

Description

If you upgrade a VMware instance from 1.2.3 to 2.0 with the VMware tools installed, once booted into 2.0 (FreeBSD 8) the VM will attempt to load the old tools (From FreeBSD 7) and a panic will occur.

We may need something in the upgrade process to disable certain packages (or all packages?) until they can be upgraded.

Associated revisions

Revision cf42de70 (diff)
Added by Scott Ullrich almost 9 years ago

Swoop through and stop any packages prior to upgrade. Ticket #1156

Revision fe868e1d (diff)
Added by Scott Ullrich almost 9 years ago

Revert "Swoop through and stop any packages prior to upgrade. Ticket #1156"

This reverts commit cf42de70c84632bcee5d6d545b1242f14a73c618.

Revision 9b193619 (diff)
Added by Scott Ullrich almost 9 years ago

Reinstall packages on bootup during console. Ticket #1156

History

#1 Updated by Scott Ullrich over 8 years ago

  • Status changed from New to Feedback

Marking as feedback, the recent package changes should have resolved this.

#2 Updated by Craig Reynolds over 8 years ago

After upgrade, still panics and reboots.

#3 Updated by Jim Pingle over 8 years ago

Probably the same issue now as #1251 - /tmp/post_upgrade_command.php is not executing when going from 1.2.3 to 2.0, so the packages aren't getting reinstalled at bootup on the 2.0 upgrade.

#4 Updated by Jon Gerdes over 8 years ago

This is still an issue:

Install new VM from 1.2.3-Release LiveCD
Install Open VM Tools
Use automatic updater to 2.0 RC1 - snapshot dated 28 Feb 2011

It's hard to see exactly where it panics but I definitely see "Configuring Firewall" and a line or two more before a great long stream of white text that looks like an unhappy system followed by a reboot.

#5 Updated by Jim Pingle over 8 years ago

Boot to single user mode, touch /conf/needs_package_sync, and then reboot.

#6 Updated by rancor rancor over 8 years ago

It works for me with 2.0 RC3 - snapshot dated 23 june 2011

I just tested with a fresh install with pfSense-1.2.3-RELEASE-LiveCD-Installer.iso on VMware ESXi 4.1, installed on harddisk and installed Open VMware tools and rebooted the system.

Switched updater to 2.0 and upgraded. On the console I could see that Open VMware tools was reinstalled after upgrade and it booted up just fine. I checked with ps ax | grep vmware and kldstat and the modules was running.

vCenter also reported that VMware tools was installed as "Unmanaged"

// rancor

#7 Updated by Scott Ullrich over 8 years ago

  • Status changed from Feedback to Closed

Thanks for the update!

Also available in: Atom PDF