Project

General

Profile

Actions

Bug #1699

closed

Update fail from 1.2.3 to 2.0-RC3 if umlaute are used in descriptions

Added by Jens Kuehnel over 12 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
07/20/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

If umlaut like äöü are used in the description somewhere like FW-rules the update from 1.2.3-release to 2.0-RC3 hangs during 1st reboot to 2.0 with the errormessage "Network interface mismatch -- Running interface assignment option".

If you remove the special characters and than do a upgrade and change it back again, everything works.

If this is not fixed, please at least put it into the readme file.

Actions #1

Updated by Jens Kuehnel over 12 years ago

Tested it with update from 1.2.3-RELEASE to both:

pfSense-Full-Update-2.0-RC3-i386-20110719-2331.tgz
pfSense-Full-Update-2.0-RC3-i386-20110621-1542.tgz

Same result.

Actions #2

Updated by Jim Pingle over 12 years ago

  • Status changed from New to Rejected

They were not supported in 1.2.3, count yourself lucky it didn't blow up on you earlier. This is a known issue, not much of a workaround either because the XML parser is tossing the input out - you have invalid XML, that was allowed only by a lack of input validation on the old box and a less strict XML parser.

Actions #3

Updated by Jens Kuehnel over 12 years ago

Could you at least added this to the "known problems" or the README file for the update.
It worked in 1.2.3 and will bite you in the a** during the update. Took me 2 days to find it.

Actions #4

Updated by Jim Pingle over 12 years ago

It's been mentioned in dozens of forum threads and on the mailing list, and elsewhere. I'm not sure if it's on the doc wiki. I can check and add notes to the upgrade guide.

Actions #5

Updated by Jim Pingle over 12 years ago

Note added: (broken link)

Actions #7

Updated by Jim Pingle over 12 years ago

Just added a "Pre-2.0 Upgrade Check" package for 1.2.x that will flag such things, though it can't be done automatically as part of the upgrade process, it's there for people to use to help avoid such problems.

Actions #8

Updated by Chris Buechler over 8 years ago

  • Target version deleted (2.0)
Actions

Also available in: Atom PDF