FreeNAS 11.0-RC2 Now Available

[microbug]

Since there's nothing in the official Announcements subforum yet, I thought I'd point this out. It's available to update to from 11.0-RC1 in the GUI. Apparently it's mostly bugfixes, including getting VMs to reboot properly.

Edit: Changelog:

Code:

#23992	Bug	Important	The "reset to Factory Defaults" in the Console isn't working correctly
#23961	Bug	Critical	Encode issue in kerberos ticket
#23938	Bug	Critical	Plugin jail creation may end up with duplicated mac
#23932	Bug	Important	Jails with communication problem will hang plugin page for a good while
#23920	Feature	Nice to have	Update ZeroTier to 1.2.4
#23919	Bug	Expected	Is CVEÂ2016Â10012 patched in the current 9.10.2-U3?
#23909	Bug	Nice to have	Typo in getting unused disks when there is iscsi disk device
#23907	Bug	No priority	Improve clarity of lagg member inactive alert
#23889	Bug	Important	middlewared.log has too much noise
#23887	Bug	Important	Traceback getting unused disks when there is a Disk iscsi extent
#23861	Bug	Important	Cannot Upload Saved Config
#23858	Bug	Blocks Until Resolved	Critical Alerts emailed every minute
#23846	Bug	Important	Wrong graphs shown for disks latency
#23844	Bug	Expected	Subject Alternative Name support in SSL certificates
#23836	Bug	Important	Increase default timeout for middleware client
#23835	Bug	Nice to have	Possible exception on update.get_pending
#23821	Bug	Blocks Until Resolved	upgraded from 9.3 to 11 stable
#23815	Bug	Nice to have	Typo in train downgrade alert
#23803	Bug	Critical	Losing default route after boot if no interface is configured (DHCP)
#23802	Bug	Important	Include middleware log on timeout exceptions from GUI
#23800	Bug	Nice to have	Update iocage to cd6334eb0236642d7294149552a197312037bb68
#23783	Bug	Important	Web interface not available after upgrade to 11.0 RC
#23774	Bug	Important	Add middlewared event to tell when system has been booted
#23764	Bug	Expected	Certificate in api doc shows mostly empty, not sure if it's done or not
#23761	Bug	Important	Update iocage to latest version.
#23760	Bug	Nice to have	jsonify the response coming from the API call.
#23749	Bug	Important	Failure at jail creation will not be reported correctly
#23705	Bug	Nice to have	Make sure homedir exists in replication pairing
#23704	Bug	Important	Traceback when there is no jail matching plugin
#23689	Bug	Important	s3 Secret Key - Incorrect Length
#23593	Bug	Expected	mountd quoted parsing is not right
#23591	Bug	No priority	Unable to reboot VM.  FreeNAS 11 GUI and bhyvectl show different status.
#23390	Feature	Nice to have	Make Zerotier available to Freenas OS
#21639	Feature	Important	Add warning if lagg members aren't all active when they should be.
#20970	Feature	Important	Bump log retention
#20212	Bug	Important	traceback on factory restore on 201701120619 (40e8230)

Edit 2: My CentOS 7 VM reboots as expected under 11.0-RC2.

 

[Terry Pounds]

When I did upgrade from FreeNAS11 RC1 to RC2 it fails to boot complaining that it can't find python files. I had to revert back to RC1. Anyone else having this same issue?

 

[Ericloewe]

No. It may be a dodgy boot device.

 

[gpsguy]

It looks like there are plans for 11.0-RC3.

I don't see it on the roadmap, but in the 11.0 docs, they bumped the version to RC3 today.

 

[microbug]

I guess they really don't want a repeat of Corral.

 

[Ericloewe]

It looks like there are plans for 11.0-RC3.

I don't see it on the roadmap, but in the 11.0 docs, they bumped the version to RC3 today.

That's odd, there are a few bugs left with not too much time to spare, but I didn't see any that sounded like they'd block a release.

 

[gpsguy]

I just checked the roadmap again. 11.0 RC3 is now listed with 16 closed items. 0 are open.

 

[m0nkey_]

I guess they really don't want a repeat of Corral.

I don't think anyone wants a repeat of Corral.

 

[Adrian]

I have upgraded my test and backup machines to 11.0-RC2.
Both are simple replication targets, no shares, few packages, no jails or VMs.
All seems well.

Creating a cache device works.
Looks like the L2ARC usage >> actual device size problem is fixed.

On the backup machine (a FreeNAS Mini) I have a few occurrences of a message I have never noticed before:

Code:

May 18 21:07:41 freenas collectd[8030]: aggregation plugin: Unable to read the current rate of "freenas.censored/cpu-3/cpu-user".
May 18 21:07:41 freenas collectd[8030]: utils_vl_lookup: The user object callback failed with status 2.
May 18 21:29:11 freenas collectd[8030]: aggregation plugin: Unable to read the current rate of "freenas.censored/cpu-3/cpu-user".
May 18 21:29:11 freenas collectd[8030]: utils_vl_lookup: The user object callback failed with status 2.
May 18 21:36:11 freenas collectd[8030]: aggregation plugin: Unable to read the current rate of "freenas.censored/cpu-4/cpu-system".
May 18 21:36:11 freenas collectd[8030]: utils_vl_lookup: The user object callback failed with status 2.

 

[Ericloewe]

That sounds vaguely related to that somewhat mysterious bug report. Let me see if I can find it...
https://bugs.freenas.org/issues/23668

 

[Stux]

I have upgraded my test and backup machines to 11.0-RC2.
Both are simple replication targets, no shares, few packages, no jails or VMs.
All seems well.

Creating a cache device works.
Looks like the L2ARC usage >> actual device size problem is fixed.

On the backup machine (a FreeNAS Mini) I have a few occurrences of a message I have never noticed before:

Code:

May 18 21:07:41 freenas collectd[8030]: aggregation plugin: Unable to read the current rate of "freenas.censored/cpu-3/cpu-user".
May 18 21:07:41 freenas collectd[8030]: utils_vl_lookup: The user object callback failed with status 2.
May 18 21:29:11 freenas collectd[8030]: aggregation plugin: Unable to read the current rate of "freenas.censored/cpu-3/cpu-user".
May 18 21:29:11 freenas collectd[8030]: utils_vl_lookup: The user object callback failed with status 2.
May 18 21:36:11 freenas collectd[8030]: aggregation plugin: Unable to read the current rate of "freenas.censored/cpu-4/cpu-system".
May 18 21:36:11 freenas collectd[8030]: utils_vl_lookup: The user object callback failed with status 2.

I've been getting that with RC1 too.

 

[Adrian]

It does indeed. I had been loading up my L2ARC with tar -c -f /dev/null <a big directory> at the time. I will see if it is reproducible and update the bug.

 

[HermesGroup]

Maybe I found a problem with Tunables, which are not applied in 11.0-rc2

No result in /boot/loader.conf after reboot:

Do you have any hints? Thanks

Johnny R.
- - -
Hermes Group

 

[amiskell]

Maybe I found a problem with Tunables, which are not applied in 11.0-rc2

No result in /boot/loader.conf after reboot:

Do you have any hints? Thanks

Johnny R.
- - -
Hermes Group

Did you check loader.conf.local to see if values are there?

 

[HermesGroup]

You're right Amiskell, thanks for the suggestion. This is the content of loader.conf.local and it looks ok:

I was worried because ctladm devlist showed empty result. In fact ctladm port -l works. I will check the docs.

Johnny R.
- - -
Hermes Group

 

[HermesGroup]

Solved, I didn't noticed iSCSI service was not running, because of bug #23941

Johnny R.

 

[gpsguy]

Today, I noticed the docs were updated to 11.0-RC4. Looks like yet another RC is coming soon - https://bugs.freenas.org/projects/freenas/roadmap#11.0-RC4

 

[Ericloewe]

So it seems.

 

[Z300M]

That sounds vaguely related to that somewhat mysterious bug report. Let me see if I can find it...
https://bugs.freenas.org/issues/23668

I have those messages with 11.0-RELEASE. I've added my report to the same Bug report.