Project

General

Profile

Bug #6516

Plugin install faill addr var

Added by Laramy Black almost 6 years ago. Updated almost 3 years ago.

Status:
Closed: Not To Be Fixed
Priority:
No priority
Assignee:
John Hixson
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Expected result: Plugins install

Actual Result: plugin fails with
manage.py: [middleware.exceptions:38] [MiddlewareError: Failed to install plugin: local variable 'addrs' referenced before assignment]"

configuration that causes this

Jails > configuration
ipv4
DHCP checked
ipv6
autoconf unchecked
other fields left empty

Jails will install with above setup, plugins will not.

To make plugins work either
1
Set ipv4 dhcp off and set a static range
2
check both ipv4 dhcp and ipv6 autoconf

History

#1 Updated by Laramy Black almost 6 years ago

i updated from 9.2.1.x (forgot exact version but the one with the jail issue that caused the host to reboot on a jail restart)

#2 Updated by Wedge Jarrad almost 6 years ago

Submitted pull request 83 ( https://github.com/freenas/freenas/pull/83 )to partially address this. The variable 'addrs' was only being initialized if IPv4 was NOT set to DHCP. This meant that if IPv6 was NOT set to autoconfig and IPv4 WAS set to DHCP then it would try to reference addrs without it having been initialized. After the fix you can now set IPv4 to DHCP and specify a fixed address for IPv6.

This will still produce an error, however, if IPv6 is NOT set to autoconfig and the IPv6 Network/Start Address/End Address have not been configured on the Jails tab. I'm not sure what the desired behavior in this circumstance should be. Should it default to autoconfig (this is what the regular jails appear to do) or should it just not configure IPv6 at all?

#3 Updated by Jordan Hubbard almost 6 years ago

  • Status changed from Unscreened to Resolved

The behavior should be to not configure IPv6 at all; IPv6 doesn't actually work fully in FreeNAS yet. There are still many fields that are IPv4-only and we have some ground to cover before IPv6 will be a feature users can even turn on.

#4 Updated by Dru Lavigne almost 3 years ago

  • Category set to 38
  • Status changed from Resolved to Closed: Not To Be Fixed
  • Assignee set to John Hixson
  • Target version set to N/A

Also available in: Atom PDF