Project

General

Profile

Bug #30672

Add vnet_interfaces to iocage creation config

Added by Dan Brown over 1 year ago. Updated about 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
Brandon Schneider
Category:
OS
Target version:
Seen in:
Severity:
New
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

I've seen a number of bugs, generally marked as dupes of #28627, for iocage networking problems when using virtual networking. But I'm having problems creating a jail WITHOUT using vnet. On a test VM (running under Proxmox, with an interface name of vtnet0), I run:
root@freenas:~ # iocage create --name "testjail" -r 11.1-RELEASE ip4_addr="vtnet0|192.168.1.26/24" defaultrouter="192.168.1.1" boot="on" host_hostname="testjail"

...and get this traceback as a result:
Traceback (most recent call last):
File "/usr/local/bin/iocage", line 10, in <module>
sys.exit(cli())
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
return process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/iocage/cli/create.py", line 145, in cli
basejail=basejail, empty=empty)
File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", line 644, in create
exit_on_error=self.exit_on_error).create_jail()
File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_create.py", line 86, in create_jail
return self._create_jail(jail_uuid, location)
File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_create.py", line 449, in _create_jail
silent=self.silent)
File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_start.py", line 64, in init
self.
_start_jail__()
File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_start.py", line 127, in start_jail
vnet_interfaces = self.conf["vnet_interfaces"]
KeyError: 'vnet_interfaces'

Other people reporting similar issues are using different NIC drivers (e.g., https://forums.freenas.org/index.php?threads/scripted-installation-of-nextcloud-13-in-iocage-jail.62485/page-3#post-447471 is using re0, and another is using em0), so it doesn't seem to relate to the adapter name.

This was working in 11.1-U2, some folks were reporting problems in 11.1-U3, and it's definitely broken for me in 11.1-U4.

History

#1 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to Brandon Schneider
  • Target version set to 11.2-RC2
  • Seen in changed from Unspecified to 11.1-U4

#2 Updated by Dan Brown over 1 year ago

  • File debug-freenas-20180325115836.txz added
  • Private changed from No to Yes

#3 Updated by Brandon Schneider over 1 year ago

  • Status changed from Unscreened to Not Started

Thanks for reporting! Embarrassing when ones forgets a spot ;)

Commit: https://github.com/iocage/iocage/commit/0271b76d46767def4d9085f88edf30e726e28733

#4 Updated by Brandon Schneider over 1 year ago

  • Status changed from Not Started to In Progress

#5 Updated by Brandon Schneider over 1 year ago

  • Status changed from In Progress to Done
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#6 Updated by Dru Lavigne over 1 year ago

  • File deleted (debug-freenas-20180325115836.txz)

#7 Updated by Dru Lavigne over 1 year ago

  • Subject changed from Creating iocage jail WITHOUT virtual networking fails to Add vnet_interfaces to iocage creation config
  • Target version changed from 11.2-RC2 to 11.2-BETA1
  • Private changed from Yes to No

#8 Updated by Dru Lavigne about 1 year ago

  • Status changed from Done to Ready for Testing

#9 Updated by Nick Wolff about 1 year ago

  • Status changed from Ready for Testing to Passed Testing
  • Severity set to New

Passed testing

root@fncertified:~ # iocage create --name "testjail" -r 11.1-RELEASE ip4_addr="igb3|192.168.1.26/24" defaultrouter="192.168.1.1" boot="on" host_hostname="testjail" 
testjail successfully created!
* Starting testjail
  + Started OK
  + Starting services OK

#10 Updated by Dru Lavigne about 1 year ago

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

#11 Updated by Disk Didler about 1 year ago

Guys is this now in nightly builds or no?

I've made a complete warcrime of several threads, reporting problems which may not exist.
Am I being impacted by this bug?

https://forums.freenas.org/index.php?threads/freenas-under-vmware-having-iocage-networking-problems.68379/

"Error: error sending query: General LDNS error {repo} could not be reached, please check your DNS" when making a jail using iocage.

#12 Updated by Dru Lavigne about 1 year ago

If the error persists in BETA1 (due out today), please create a new ticket.

#13 Updated by Disk Didler about 1 year ago

Hi Dru,

There may be other issues which I'm not aware of. I did end up fixing my issue. It was to do with the creation of a DHCP iocage jail and requiring a particular flag to be set.

To be fair, I test under VMWare and that did add complications (it never used to though,.....)
Cheers

Also available in: Atom PDF