Operational Defect Database
BugZero found this defect 3545 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000g3k6SAA
Dimension upgrade to v1.3 fails with error “-y was used without –force-yes”
Last update date:
9/4/2014
Affected products:
WatchGuard Dimension
Affected releases:
All
WatchGuard Dimension
2.x and 1.x
Fixed releases:
All
Description:
Issue
When your Dimension installation is behind a Firebox or XTM device configured with an HTTP proxy that blocks responses with their content type set to "none" in the file header, your upgrade to Dimension v1.3 can fail. When this issue occurs, you can see this error in your log messages:Operation failed. Reason: Error installing packages from file /var/opt/watchguard/dimension/upload.62ded34d-ff8d-4c64-83dc-c8901d61d43f.deb; E: There are problems and -y was used without --force-yesIn Fireware XTM v11.9.1 and earlier releases, the HTTP proxy denied headers with a content type set to "none" by default.
Workaround/Solution
The Content-Type header in an HTTP response is a general description of the media content provided by the server to help clients process the response, and is not guaranteed to be accurate. By default, the HTTP proxy in Fireware XTM v11.9.1 or earlier will not allow HTTP server responses that do not specify a content type.To upgrade to v1.3, you can either configure the HTTP proxy on your Firebox or XTM device to allow HTTP server responses with a content type of "none" as described below, or create a separate HTTP proxy or packet filter policy to allow the Dimension server access to the Ubuntu repository. From Policy Manager, right-click the HTTP proxy policy and select Edit Policy.Click View/Edit Proxy.From the Categories tree, select Content Types.Click Change View. In the Rules (advanced view) list, select the check box adjacent to the Allow (none) rule.
