Project

General

Profile

Bug #14930

Incorrect warden.conf in newest freenas update

Added by Gerhard Röthlin over 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
No priority
Assignee:
Jordan Hubbard
Category:
Middleware
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

After applying the newest freenas update, warden.con is incorrect. It contains paths pointing at /usr instead of into my jail dataset. This might be related with my dataset being unavailable during boot because it is encrypted.

During the import of the pool, the web UI popped up an error dialog with following contents:

Environment: Software Version: FreeNAS-9.10-STABLE-201604181743 (74ef270) Request Method: POST Request URL: https://192.168.1.126/storage/volume/1/unlock/?X-Progress-ID=f3ad384f-9cf6-4fb7-8211-cf26c8de941f Traceback: File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File "/usr/local/www/freenasUI/../freenasUI/freeadmin/middleware.py" in process_view 156. return login_required(view_func)(request, *view_args, **view_kwargs) File "/usr/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view 22. return view_func(request, *args, **kwargs) File "/usr/local/www/freenasUI/../freenasUI/storage/views.py" in volume_unlock 1128. form.done(volume=volume) File "/usr/local/www/freenasUI/../freenasUI/storage/forms.py" in done 2546. notifier().sync_encrypted(volume=volume) File "/usr/local/www/freenasUI/../freenasUI/middleware/notifier.py" in sync_encrypted 4755. if not ed.encrypted_disk or ( File "/usr/local/lib/python2.7/site-packages/django/db/models/fields/related.py" in get 320. rel_obj = qs.get() File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py" in get 310. self.model._meta.object_name) Exception Type: DoesNotExist at /storage/volume/1/unlock/ Exception Value: Disk matching query does not exist.

Rolling back to freenas from 0327 and reapplying the update did not solve the issue, but changed this error message.

Restoring warden.conf from backup did. But this might only be temporary if freenas overwrites the fixed warden.conf with its own corrupted version.

History

#1 Updated by Jordan Hubbard over 4 years ago

  • Status changed from Unscreened to 15

There were other problems with encrypted storage + jails that may be interfering here. Can you try to update to http://download.freenas.org/9.10/STABLE/201604261518/ and see if this still reproduces?

#2 Updated by Gerhard Röthlin over 4 years ago

Jordan Hubbard wrote:

There were other problems with encrypted storage + jails that may be interfering here. Can you try to update to http://download.freenas.org/9.10/STABLE/201604261518/ and see if this still reproduces?

This update seems to solve the problem with warden not listing the jails, and it also seems to solve the problem with jails not auto-starting when the pool they reside on is unlocked that I reported here: https://bugs.freenas.org/issues/8288

Thanks!

#3 Updated by Jordan Hubbard over 4 years ago

  • Status changed from 15 to Resolved

#4 Updated by Dru Lavigne almost 3 years ago

  • Target version set to Master - FreeNAS Nightlies

Also available in: Atom PDF