9.3Stable April 29th Update Removing itself

[Dave Genton]

got the 4/29 update last night/early this morning and since fighting so many bugs past 3 days allowed it to take it and reboot with high hopes. Waited for boot to finish and checked version was 4/29 build, then freenas took a nap for a few hours being powered off while other maintenance was done in that room its housed in. Back at it fighting LDAP only to see same version running, not the 4/29 update just pushed. Checked the Boot tab and 4/29 shows "on reboot", while prior revision is again marked as active ?? Marked 4/29 update active on reboot, rebooted, but again same thing, reverts back to prior release never actually coming up so I see 4/29 version in effect and running except for that initial boot when update was installed.

Any other erratic behavior being seen ?? First time I have ever seen this with freenas so hoping i dont have something flaking out as this is my recently purchased and built new lab system only a few months old...

Version still running is 201504152200 to clarify, so deleting the 20150429xxxx since will no longer go active. If prompted to download again, I may but wont active until I find out if I'm the rare flower or the build has issues..

Thanks in advance,
Dave

 

[dlavigne]

A bug was found in that update so it was pulled from the download website. It appears that the installed version is doing what you've reported.

 

[Dave Genton]

A bug was found in that update so it was pulled from the download website. It appears that the installed version is doing what you've reported.

Thanks, checked back after just checking and seeing it wasn't downloading again. Quick question, some issues I am being roadblocked with on LDAP is because and this is just one of many, but a big one being NTP needs to be updated to at least 4.2.6. 4.2.8p2 is the newest but wondering if/when 4.2.6 or better was going to be pushed into Freenas updates ?? that allows the ntpd_signd for time sync with client machines, ddns, etc. The Samba41 cannot be fully functional until our ntpd is updated and apparently the ntpd within freenas differs greatly than normal "ports" or distro's and I feel safer not attempting to manually update it for fear of obstructing freenas in production, or at every least losing the update during next freenas upgrade. Due to certificates imported from open directory not showing up to allow freenas to bind into ldap with os x server I'm forced temporarily into using active directory, however the project originated from requirement of OS X Server Profile Manager and MDM tools which require Open Directory forcing me to have both in a single site... all issues would go away quickly if ldap on freenas would bind to ldap but stuck at certificates not in drop down for ldap, but show in drop down on all other services oddly..

thx again :)
d-

 

[dlavigne]

It is worth creating a feature request at bugs.freenas.org that describes the features you need in that version. If you do, post the issue number here.