search for: db_omat

Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- src/db-omatic/db_omatic.rb | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index da11bfa..79f29d2 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -195,6 +195,9 @@ class DbOmatic < Qmf::ConsoleHandler...

--- src/db-omatic/db_omatic.rb | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index 155ff5e..b5b7b81 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -270,10 +270,10 @@ class DbOmatic < Qpid::Qmf::Conso...

The error is caused by the save! method updating an object that another thread (most likely in taskomatic) already updated. In the case of this race condition, we retry saving. However, a proper fix would involve fixing the locking. --- src/db-omatic/db_omatic.rb | 23 ++++++++++++++++++++--- 1 files changed, 20 insertions(+), 3 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index d2540e1..60ea9f7 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -160,7 +160,9 @@ class DbOmatic < Qpid::...

...of ovirt-server.conf in httpd conf (see https://bugzilla.redhat.com/show_bug.cgi?id=514536) I then looked at the logs and I found errors so I launched db-omatic and taskomatic in debug mode to see what the problem is: Lauching db-omatic.rb: [root at management ~]# /usr/share/ovirt-server/db-omatic/db_omatic.rb -n INFO Fri Jul 31 10:04:31 +0200 2009 (7242) dbomatic started. INFO Fri Jul 31 10:04:31 +0200 2009 (7242) Connecting to amqp://management.open.net:5672 /usr/share/ovirt-server/db-omatic/db_omatic.rb:252:in `object_props': undefined method `[]' for #<Qpid::Qmf::ClassKey:0x7f2a48ae8e...

This fixes a bug where if db-omatic restarted, any running vm lost the association with the host it is running on in the db. --- src/db-omatic/db_omatic.rb | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index b5b7b81..d2540e1 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -202,7 +202,18 @@ class DbOmatic < Qpid::Qmf::Consol...

The underlying issue has to do with optimistic locking for active record, and contention between db-omatic and task-omatic. That still needs to be fixed, especially since contention issues might get worse when the two daemons are made multithreaded. --- src/db-omatic/db_omatic.rb | 22 +++++++++++++++++++--- 1 files changed, 19 insertions(+), 3 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index d2540e1..819f67c 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -160,7 +160,9 @@ class DbOmatic < Qpid::Q...

...fixes state changes in dbomatic so that there is no intermediate 'stopped' state after being unreachable or on startup of dbomatic etc. Also fixes a number of smaller bugs around host associations, state changes, etc. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 85 +++++++++++++++++++++++++++++++------------- 1 files changed, 60 insertions(+), 25 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index b3d5e73..1091333 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -113,6 +113,15 @@ cla...

This fix db-omatic that cannot recover the node on wich the vm run for example. We have not investigate far away but that can be due to a change on the ruby-qmf API. Signed-off-by: Michel Loiseleur <mloiseleur at linagora.com> --- src/db-omatic/db_omatic.rb | 10 ++++++---- src/libvirt-list.rb | 6 +++--- src/matahari-list.rb | 4 ++-- 3 files changed, 11 insertions(+), 9 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index 686ad71..da11bfa 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/...

...| 9 - src/app/models/vm.rb | 36 ---- src/app/models/vm_host_history.rb | 22 --- src/app/views/vm/_form.rhtml | 3 - src/app/views/vm/show.rhtml | 4 - src/db-omatic/db_omatic.rb | 31 ---- src/db-omatic/vnc.rb | 173 -------------------- .../040_remove_vm_history_and_forward_vnc.rb | 65 ++++++++ src/test/fixtures/vms.yml | 2 - src/test/unit/vm_test.rb...

...gned-off-by: Jason Guiditta <jguiditt at redhat.com> --- src/app/models/vm.rb | 7 ++ src/app/models/vm_task.rb | 4 +- src/app/services/service_module_helper.rb | 34 +++++++ src/app/services/vm_service.rb | 33 ++++++- src/db-omatic/db_omatic.rb | 90 +++++++++++++----- src/test/fixtures/permissions.yml | 6 +- src/test/fixtures/vms.yml | 13 +++ src/test/unit/vm_service_test.rb | 149 +++++++++++++++++++++++++++++ src/test/unit/vm_task_test.rb | 38 ++++++++ src/te...

After running for a while the node becomes "unavailable" in the server UI. All VMs running on that node also become unavailable. The node is still running fine as are all the VMs, they're just no longer manageable. I looked on the node and everything appeared to be running fine. Looked on the server and ovirt-taskomatic was stopped (this seems to happen quite a bit).

...c, taskomatic and host-register to use the new C++ wrapped ruby QMF bindings. It also fixes a couple of bugs along the way including the 0 cpu bug for host-register. This is a compilation of work done by myself and Arjun Roy. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 111 ++++++------- src/host-browser/host-register.rb | 337 ++++++++++++++++++++----------------- src/libvirt-list.rb | 31 +++-- src/matahari-list.rb | 33 +++-- src/task-omatic/task_storage.rb | 10 +- src/task-omatic/taskomatic.rb | 81 +++...

...status) status $DAEMON RETVAL=$? diff --git a/conf/ovirt-db-omatic b/conf/ovirt-db-omatic index f8337e0..cba275d 100755 --- a/conf/ovirt-db-omatic +++ b/conf/ovirt-db-omatic @@ -13,6 +13,7 @@ export RAILS_ENV="${RAILS_ENV:-production}" DAEMON=/usr/share/ovirt-server/db-omatic/db_omatic.rb +DBOMATIC_LOCKFILE="${DBOMATIC_LOCKFILE:-/var/lock/subsys/ovirt-db-omatic }" . /etc/init.d/functions @@ -21,6 +22,9 @@ start() { daemon $DAEMON RETVAL=$? echo + if [ $RETVAL -eq 0 ]; then + touch $DBOMATIC_LOCKFILE + fi } stop() { @@ -28,6 +32,9...