+++ This bug was initially created as a clone of Bug #1072549 +++
I've recently rebased to master and it looks like the
03_05_0050_event_notification_methods.sql script is failing on schema
upgrade. Is this a bug or am I doing something wrong? To upgrade I
did the normal proceedure with my development installation:
make install-dev ...
~/ovirt/bin/engine-setup
Got this result in the log file:
psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: ERROR: column "notification_method" contains null values
FATAL: Cannot execute sql command: --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql
2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod
method['method']()
File "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", line 280, in _misc
osetupcons.DBEnv.PGPASS_FILE
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in execute
command=args[0],
RuntimeError: Command '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' failed to execute
Version-Release number of selected component (if applicable):
faafbcf89fb1b236e228aa64c6143032d850a4fa
--- Additional comment from Eli Mesika on 2014-03-05 05:17:26 EST ---
moving that to 3.4 urgent since any installation that have non-empty event_subscriber table (users that had subscribed to any event) will cause the upgrade to fail
set to 3.4 and mark as blocker and urgent since any installation that have non-empty event_subscriber table (users that had subscribed to any event) will cause the upgrade to fail