Update from 10.1.74 to V11 staging (11.0.3-beta.26)

Hello

I get following error, when I am trying to update from V10 to V11 staging:


File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pymysql/connections.py”, line 516, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pymysql/connections.py”, line 727, in _read_query_result
result.read()
File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pymysql/connections.py”, line 1066, in read
first_packet = self.connection._read_packet()
File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pymysql/connections.py”, line 683, in _read_packet
packet.check_error()
File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pymysql/protocol.py”, line 220, in check_error
err.raise_mysql_exception(self._data)
File “/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pymysql/err.py”, line 109, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.ProgrammingError: (1146, u"Table ‘6d4b9452aef14153.tabPrepared Report’ doesn’t exist")

Often just rerun bench update a few times will resolve a “table doesn’t exist” snag.

For more clues search here on for eg “Prepared Report” or check here for issue reports or PR fix activity

bench restart as well as sudo service nginx restart
sudo supervisorctl restart all also helps.

And bench update --patch

its mean the DB does not contain the table
use
bench migrate
or
bench update --patch

sometimes you need to use
bench setup requirements

I followed all of this and it still does not work. Any suggestion?

How about this

ImportError: Module import failed for Prepared Report (frappe.core.doctype.prepared_report.prepared_report Error: No module named file_manager)

here Error create new site: No module file_manager

I’ve been struggling to get ERPNext to upgrade to version 11, using the Production Image. I’ve tried every trick on the forums. Even when I can move to the staging branch, the update fails at some point.

Perhaps it makes sense to release a new Virtual Image which is already setup with version 11?