Bug #7276
closed
2.3.3 upgrade does not upgrade
Added by Kill Bill almost 8 years ago. Updated over 7 years ago.
0%
Description
Really starting to lose my patience with pkg. :-X
Installed packages to be REMOVED:
openvpn-2.4.0
New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]
Installed packages to be UPGRADED:
pfSense-default-config-serial: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense-base: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense: 2.3.3.a.20170203.1258 -> 2.3.3.r.20170214.0531 [pfSense]
bind-tools: 9.11.0P2 -> 9.11.0P3 [pfSense]
Installed packages to be REINSTALLED:
net-snmp-5.7.3_11 [pfSense] (options changed)
Number of packages to be removed: 1
Number of packages to be installed: 2
Number of packages to be upgraded: 4
Number of packages to be reinstalled: 1
Upgrade is complete. Rebooting in 10 seconds.
After reboot, of course nothing is upgraded.
$ cat /etc/version* 2.3.3-DEVELOPMENT Fri Feb 03 13:31:32 CST 2017 67bc9afc96a32954c84d1b504085ac97dc5a14ef 0
Updated by Kill Bill almost 8 years ago
Third round of pkg idiocy, now pkg getting more schizo, first wants to reinstall itself, then changes its mind, first it can see openvpn conflict, seconds later it cannot see any conflict at all, and then it does absolutely nothing again.
Enter an option: 13
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
>>> Unlocking package pfSense-kernel-pfSense... done.
The following 9 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
openvpn-2.4.0
New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]
Installed packages to be UPGRADED:
pfSense-default-config-serial: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense-base: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense: 2.3.3.a.20170203.1258 -> 2.3.3.r.20170214.0531 [pfSense]
bind-tools: 9.11.0P2 -> 9.11.0P3 [pfSense]
Installed packages to be REINSTALLED:
pkg-1.9.4_1 [pfSense]
net-snmp-5.7.3_11 [pfSense] (options changed)
Number of packages to be removed: 1
Number of packages to be installed: 2
Number of packages to be upgraded: 4
Number of packages to be reinstalled: 2
2 MiB to be downloaded.
**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) y
>>> Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (5 candidates): ..... done
Processing candidates (5 candidates): ..... done
Checking integrity... done (1 conflicting)
- openvpn23-2.3.14 [pfSense] conflicts with openvpn-2.4.0 [installed] on /usr/local/include/openvpn-plugin.h
Checking integrity... done (0 conflicting)
The following 8 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
openvpn-2.4.0
New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]
Installed packages to be UPGRADED:
pfSense-default-config-serial: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense-base: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense: 2.3.3.a.20170203.1258 -> 2.3.3.r.20170214.0531 [pfSense]
bind-tools: 9.11.0P2 -> 9.11.0P3 [pfSense]
Installed packages to be REINSTALLED:
net-snmp-5.7.3_11 [pfSense] (options changed)
Number of packages to be removed: 1
Number of packages to be installed: 2
Number of packages to be upgraded: 4
Number of packages to be reinstalled: 1
Upgrade is complete. Rebooting in 10 seconds.
Again, nothing upgraded. Junk!
Round 4 - Alas, even after providing all the manual assistance with the inability to downgrade a single package, this "next generation" package manager fails yet again and does absolutely NOTHING.
$ pkg delete -f openvpn\*
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 2 packages (of 0 packages in the universe):
Installed packages to be REMOVED:
openvpn-2.4.0
openvpn-client-export-2.4
Number of packages to be removed: 2
The operation will free 13 MiB.
Proceed with deinstalling packages? [y/N]: y
[1/2] Deinstalling openvpn-2.4.0...
[1/2] Deleting files for openvpn-2.4.0: 53%
openvpn-2.4.0: missing file /usr/local/man/man8/openvpn.8.gz
[1/2] Deleting files for openvpn-2.4.0: 100%
[2/2] Deinstalling openvpn-client-export-2.4...
[2/2] Deleting files for openvpn-client-export-2.4: 100%
Enter an option: 13
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
>>> Unlocking package pfSense-kernel-pfSense... done.
The following 7 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]
Installed packages to be UPGRADED:
pfSense-default-config-serial: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense-base: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense: 2.3.3.a.20170203.1258 -> 2.3.3.r.20170214.0531 [pfSense]
bind-tools: 9.11.0P2 -> 9.11.0P3 [pfSense]
Installed packages to be REINSTALLED:
net-snmp-5.7.3_11 [pfSense] (options changed)
Number of packages to be installed: 2
Number of packages to be upgraded: 4
Number of packages to be reinstalled: 1
The process will require 1 MiB more space.
**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) y
>>> Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (5 candidates): ..... done
Processing candidates (5 candidates): ..... done
Checking integrity... done (0 conflicting)
The following 7 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]
Installed packages to be UPGRADED:
pfSense-default-config-serial: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense-base: 2.3.3.a.20170203.1331 -> 2.3.3.r.20170215.0027 [pfSense-core]
pfSense: 2.3.3.a.20170203.1258 -> 2.3.3.r.20170214.0531 [pfSense]
bind-tools: 9.11.0P2 -> 9.11.0P3 [pfSense]
Installed packages to be REINSTALLED:
net-snmp-5.7.3_11 [pfSense] (options changed)
Number of packages to be installed: 2
Number of packages to be upgraded: 4
Number of packages to be reinstalled: 1
The process will require 1 MiB more space.
Upgrade is complete. Rebooting in 10 seconds.
Updated by Kill Bill almost 8 years ago
After Round 5 (same output as Round 4 and another reboot later), the next generation thing by some huge miracle actually (probably) did something:
Enter an option: 13 >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Your packages are up to date $ cat /etc/version* 2.3.3-RC Wed Feb 15 00:27:19 CST 2017 7b85c9aea79bb210daba645b31fffeae7aa91970 0
So, I might finally have 2.3.3-RC installed, or not. I have no idea how to verify with the next generation random failure generator.
Updated by Jim Thompson almost 8 years ago
- Assignee set to Renato Botelho
- Priority changed from Very High to High
Updated by Kill Bill almost 8 years ago
So now it doesn't even find the final release upgrade... and I'm not alone with that: https://forum.pfsense.org/index.php?topic=125873.msg695384#msg695384
Enter an option: 13 >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Your packages are up to date *** Welcome to pfSense 2.3.3-RC (amd64 full-install) on gw ***
Updated by Phillip Davis almost 8 years ago
My workaround for that was switching to development then back to stable.
Procedure at https://forum.pfsense.org/index.php?topic=125873.msg695386#msg695386
Yeh, it is a pain that this stuff does not "just work".
Updated by Renato Botelho almost 8 years ago
- Target version changed from 2.3.3 to 2.4.0
I've already did changes on pfSense-upgrade to force it to upgrade (or even downgrade) pfSense-repo package. Lets take care to avoid same problem on 2.4.0
Updated by Kill Bill almost 8 years ago
It's broken even with snapshots. The goddamn thing reliably bombs out during post-"upgrade" reboot on
pkg: https://beta.pfsense.org/packages/pfSense_v2_3_3_amd64-pfSense_v2_3_3/All/pkg-1.9.4_1.txz: No address record
Of course there's nothing wrong with address record and the same box fetches the pkg just fine when it's booted. So, whatever is in the output, it's not showing anything relevant, just bogus junk.
Another thing: to get the 2.3.3 snapshots box switch to the stable branch, this braindead drill seems to be absolutely required:
- switch branch back to development in GUI, otherwise you won't get anywhere
- 13/ from console, decline upgrade - without this, you won't move anywhere. This picks up some 2.3.3 snapshot for god knows what reason.
- switch branch to stable in GUI
- 13/ from console, decline upgrade - without this, you again won't move anywhere. This again picks up some 2.3.3 snapshot, god knows why.
- switch branch to development in GUI
- 13/ from console, decline upgrade - without this, still no luck. This picks up 2.3.4 snapshot, that at least finally makes sense.
- switch branch to stable in GUI
- 13/ from console - NOW it picks up 2.3.3 stable, incredible!!!
Christ... Argh.
Updated by Michael Kellogg over 7 years ago
just upgrade last nite from 2.3.4 snapshot no problem
Updated by Renato Botelho over 7 years ago
Now I understood what happened here. RC packages were held at beta.pfsense.org instead of pkg.pfSense.org and this caused all confusion.
I'll change code and next RCs will stay in pkg.pfsense.org as well
Updated by Renato Botelho over 7 years ago
- Status changed from New to Resolved
I've upgraded internal docs and next time a new version is RELEASED this won't happen anymore