Project

General

Profile

Bug #46245

Correctly create aliases for shared IP jails that don't specify an interface

Added by Brandon Schneider about 2 years ago. Updated almost 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Brandon Schneider
Category:
Middleware
Target version:
11.2-RC1
Seen in:
Master - FreeNAS Nightlies
Severity:
High
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Seems jail(8) behavior may have changed, this now requires an explicit interface. iocage will try to use a default interface if one isn't supplied by the user. Otherwise no networking will function.

History

#1 Updated by Brandon Schneider about 2 years ago

  • Status changed from Unscreened to In Progress

PR: https://github.com/freenas/iocage/pull/28
DESC: Not supplying an interface no longer creates an ipv4 alias
RISK: Low
ACCEPTANCE: Create a jail without an interface but with an IP address and verify with ifconfig after starting the jail that the alias is applied.

#2 Updated by Brandon Schneider about 2 years ago

  • Status changed from In Progress to Ready for Testing

#3 Updated by Dru Lavigne about 2 years ago

  • Subject changed from Create aliases if no interface is given for shared IP's in iocage to Correctly create aliases for shared IP jails that don't specify an interface
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#4 Updated by Bonnie Follweiler almost 2 years ago

  • Status changed from Ready for Testing to Passed Testing

Test Passed in FreeNAS-11.2-MASTER-201809270704

#5 Updated by Dru Lavigne almost 2 years ago

  • Status changed from Passed Testing to Done
  • Needs QA changed from Yes to No

Also available in: Atom PDF