201502110455 Having issues with Config upload?

[Knowltey]

So I performed a fresh install with 9.3 version 201502110455 here today, when I went to upload my config from version 201502050159 the database update would fail and refer me to a file at /data/update.failed

When I go to look at that file it says

! Since you have a database that does not support running
! schema-altering statements in transactions, we have had
! to leave it in an interim state between migrations.

Also a bunch of other info, I"ll upload the file to the post.

I ended up just installing via 201502050159 directly and then upgrading to 201502110455 via the GUI. I then figured I would test to see if it was just 201502110455 having an issue with configs from older versions so I saved a config out of 201502110455 and went to upload it, same behaviour occurred again.

Seems that there may be potentially some sort of issue in the system with it configuring the database from uploaded configs. Can anyone else see if they can reproduce this? Should just need to save a config from your GUI if you are running versions 201502110455 and then see if it failed during the process and if afterwards a file exists at /data/update.failed. It will also issue a Critical Alert when this fails.


((My hardware is as follows:
Current Build: Supermicro MBD-X10SLM-F-O, Intel Pentium G3220, 16GB Samsung DDR3 ECC, 2x1TB Mirror pool.

(the boot media is an 8GB Sony USB Drive.))

 

[Ericloewe]

My auto-update from 201502070132 (to the latest Stable, I guess) failed in pretty much the same way.

Seems to be something with the snapshots, but I can't really interpret the log.

I find it odd that this isn't more widespread, since the update's been out for a few days.

 

[Knowltey]

My auto-update from 201502070132 (to the latest Stable, I guess) failed in pretty much the same way.

Seems to be something with the snapshots, but I can't really interpret the log.

I find it odd that this isn't more widespread, since the update's been out for a few days.

I found this bug shortly after submitting this post, seems that cyberjock has encountered the issue as well.
https://bugs.freenas.org/issues/7884

 

[cyberjock]

Yep. Upgraded and put the ticket in the following morning. ;)

 

[Ericloewe]

In case anyone is wondering, we're talking about Bug #7884

 

[Knowltey]

In case anyone is wondering, we're talking about Bug #7884

Whoops, could've sworn I had linked it but apparently failed to.

 

[Ericloewe]

Working now with 201502142001. Upgrade went painlessly.