11.3-BETA - defaultrouter for jails not set

[Patrick M. Hausen]

Hi all,

after updating my jails start OK, but don't have an IPv4 default route.

Code:

root@freenas-pmh[~]# iocage get defaultrouter gateway
217.29.46.97
root@freenas-pmh[~]# iocage console gateway
root@gateway:~ # netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
127.0.0.1          link#1             UH          lo0
192.168.255.0/24   192.168.255.2      UGS        tun0
192.168.255.1      link#3             UHS         lo0
192.168.255.2      link#3             UH         tun0
217.29.46.64/26    link#2             U       epair0b
217.29.46.102      link#2             UHS         lo0

root@gateway:~ # route add default 217.29.46.97

The last statement fixes things temporarily.

Anyone else seeing this? If I am not overlooking anything obvious, I will open a bug ticket later today ...

 

[mjt5282]

Patrick, yes, I am seeing the same on 75% of my jails. My 1 jail I upgraded to 11.3-Release failed. I can't even login to it right now. So I will copy the mount points etc off and try again with a brand new 11.3 beta jail.

 

[Patrick M. Hausen]

BTW: a quick rollback to 11.2-U6 did not start any jails. Iocage crashes if I try to use it ... :(

Backt to 11.3-BETA currently with the manual defaultrouter workaround.

Kind regards,
Patrick

 

[waqarahmed]

Patrick can you please create a ticket and attach a debug ? It shouldn't happen what you are seeing but depends on how you have the jail set up. Rolling back to U6 wouldn't help as iocage performs a migration on the config and U6 iocage version is not able to handle the new configuration.

 

[waqarahmed]

For clarification, i have not been able to reproduce this but i would like to see how you have it configured - maybe there's a case where that happens.

 

[Kelly Hays]

Rolling back to U6 wouldn't help as iocage performs a migration on the config and U6 iocage version is not able to handle the new configuration.

This needs to be added to the release notes to let people know that the upgrade makes permanent changes to jails that are NOT covered by the boot environments!

 

[Patrick M. Hausen]

Rolling back to U6 wouldn't help as iocage performs a migration on the config and U6 iocage version is not able to handle the new configuration.

This needs to be added to the release notes to let people know that the upgrade makes permanent changes to jails that are NOT covered by the boot environments!

Yes, please document the changes - I am pretty sure editing the jails' config.json would be a way to roll back the update.

Kind regards,
Patrick

 

[Patrick M. Hausen]

Patrick can you please create a ticket and attach a debug ? It shouldn't happen what you are seeing but depends on how you have the jail set up.

https://jira.ixsystems.com/browse/NAS-103825

Could you please fix the summary - I forgot to mention that it's a jail's default gateway that is not set.
And for some reason your Jira does not grok the '{code}' formatting like ours does.