Project

General

Profile

Bug #23518

Downgrading from 11 nightlies to 9.10 results in django error.

Added by Tim Chaubet over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Important
Assignee:
William Grzybowski
Category:
GUI (new)
Target version:
Seen in:
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

It seems the django config remains when downgrading to 9.10
I've tried to start django and it's still looking for the VM menu item.
I was on the Freenas 11 nightlies build of 2017-04-24.

[root@seth] ~# /conf/base/etc/local/rc.d/django start
Traceback (most recent call last):
File "/usr/local/www/freenasUI/manage.py", line 42, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 280, in execute
translation.activate('en-us')
File "/usr/local/lib/python2.7/site-packages/django/utils/translation/__init__.py", line 130, in activate
return _trans.activate(language)
File "/usr/local/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 188, in activate
_active.value = translation(language)
File "/usr/local/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 177, in translation
default_translation = _fetch(settings.LANGUAGE_CODE)
File "/usr/local/lib/python2.7/site-packages/django/utils/translation/trans_real.py", line 159, in _fetch
app = import_module(appname)
File "/usr/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
import(name)
ImportError: No module named vm

Associated revisions

Revision aa2936b7 (diff)
Added by William Grzybowski over 4 years ago

fix(gui): handle MAJOR_DOWNGRADE Ticket: #23518

Revision 9e6d9744 (diff)
Added by Warren Block about 4 years ago

Enhance note about downgrades not being allowed. Ticket: #23518

History

#1 Avatar?id=14398&size=24x24 Updated by Kris Moore over 4 years ago

  • Assignee set to William Grzybowski

We don't typically support "downgrades". How did you roll back? Did you use a BE?

#2 Updated by William Grzybowski over 4 years ago

  • Status changed from Unscreened to 15
  • Priority changed from No priority to Important
  • Target version set to 11.0

#3 Updated by William Grzybowski over 4 years ago

  • Status changed from 15 to Resolved

Downgrading from UI was not supposed to be allowed. Please boot to an older Boot Environment if thats the path you wanna take: e.g.

beadm list
beadm activate <name_of_old_environment>
reboot

#4 Updated by Tim Chaubet over 4 years ago

I'll accept your explanations, although a push-of-config-files on downgrade would be an option.
As in "If you downgrade, you lose all config"

To answer Kris' second question: I just chose the 9.10 stable stream from the gui and "updated"

using the beadm command wasn't an option, since the 9.10 was never used before on this system

PS: in the meantime, I reinstalled from usb. Swiftly done, though not remote.

#5 Updated by Vaibhav Chauhan about 4 years ago

  • Target version changed from 11.0 to 11.0-RC

Also available in: Atom PDF