Bug #25287
Autocreate iocage bridges
Description
Hi guys,
jails managed with iocage are not started when the FreeNAS box boots. Of course I did
iocage set boot=on <jail>
After the system booted I logged in via ssh and tried
service iocage start
only to be told I had to enable it ;) OK, so far, so expectable. I manually created a tunable of type rc.conf setting
iocage_enable=YES
and it did start. Only networking in my jail was completely dysfunctional. No device vnet0 at all. When I later tried
iocage stop <jail> iocage start <jail>
that fixed the problem for the moment, but I depend on jails coming up correctly at boot time ... (including the necessary bridge0/vnet config, of course).
Kind regards,
Patrick
History
#1
Updated by Dru Lavigne over 3 years ago
- Assignee changed from Release Council to Brandon Schneider
- Target version set to 11.1
Brandon: I wasn't sure if this was the same or just a similar issue to 25036.
#2
Updated by Patrick M. Hausen over 3 years ago
Clarification: after setting the tunable and reboot the jail did start but only without networking. Then, without another reboot, manual stop and start fixed the networking issue.
Patrick
#3
Updated by Brandon Schneider over 3 years ago
- Status changed from Unscreened to Investigation
Hey Patrick!
Do you have this issue with `iocage stop --rc` and `iocage start --rc` on the command line as well?
#4
Updated by Patrick M. Hausen over 3 years ago
root@freenas-pmh:~ # iocage list +-----+----------+-------+----------------------------+--------------+---------------+ | JID | UUID | STATE | TAG | RELEASE | IP4 | +=====+==========+=======+============================+==============+===============+ | 3 | b921488a | up | 2017-07-24@19:58:33:237869 | 11.0-RELEASE | 217.29.46.102 | +-----+----------+-------+----------------------------+--------------+---------------+ root@freenas-pmh:~ # iocage stop --rc b921488a b921488a-9c08-4699-a0dd-2e0147ca0a7f (2017-07-24@19:58:33:237869) is already running! root@freenas-pmh:~ # iocage stop --rc b921488a-9c08-4699-a0dd-2e0147ca0a7f (2017-07-24@19:58:33:237869) is already running! root@freenas-pmh:~ # iocage stop b921488a * Stopping b921488a-9c08-4699-a0dd-2e0147ca0a7f (2017-07-24@19:58:33:237869) + Running prestop OK + Stopping services OK + Removing jail process OK + Running poststop OK root@freenas-pmh:~ # iocage start --rc root@freenas-pmh:~ # iocage list +-----+----------+-------+----------------------------+--------------+---------------+ | JID | UUID | STATE | TAG | RELEASE | IP4 | +=====+==========+=======+============================+==============+===============+ | 4 | b921488a | up | 2017-07-24@19:58:33:237869 | 11.0-RELEASE | 217.29.46.102 | +-----+----------+-------+----------------------------+--------------+---------------+ root@freenas-pmh:~ # iocage console b921488a Last login: Mon Jul 24 23:10:50 on pts/0 FreeBSD 11.0-STABLE (FreeNAS.amd64) #0 r313908+d7d07647f69(freenas/11.0-stable): Thu Jul 20 19:01:05 UTC 2017 Welcome to FreeBSD! [...] root@dhcp:~ # ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> groups: lo vnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8<VLAN_MTU> ether 02:ff:60:00:00:01 inet 217.29.46.102 netmask 0xffffffe0 broadcast 217.29.46.127 nd6 options=1<PERFORMNUD> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active groups: epair root@dhcp:~ # logout
So, no issue if the FreeNAS box is already up and running. I suspect the bridge0 interface is not created when iocage is started at boot time. I have a bhyve VM on that box as well, so when everything's finished booting and I start the jails manually, bridge0 is already there and everything works.
HTH,
Patrick
#5
Updated by Brandon Schneider over 3 years ago
Thanks Patrick.
I suspect it might be a couple things, we'll circle back once I get a new iocage in nightlies.
#6
Updated by Dru Lavigne over 3 years ago
- Status changed from Investigation to 46
#7
Updated by Brandon Schneider over 3 years ago
- Status changed from 46 to Ready For Release
iocage now creates bridges for you, this issue can be considered solved
#8
Updated by Dru Lavigne over 3 years ago
- Subject changed from Iocage managed jails are not started at boot to Autocreate iocage bridges
#9
Updated by Dru Lavigne over 3 years ago
- Target version changed from 11.1 to 11.1-BETA1
#10
Updated by Dru Lavigne over 3 years ago
- Status changed from Ready For Release to Resolved
#11
Updated by Joe Maloney over 3 years ago
- Needs QA changed from Yes to No
- QA Status Test Passes FreeNAS added
- QA Status deleted (
Not Tested)