[ovirt-users] uncaught exception with engine vm in 3.6.1 selecting hosted_storage

[Gianluca Cecchi]

On Tue, Dec 22, 2015 at 2:54 PM, Alexander Wels <awels at redhat.com> wrote:

>
>
> If you can provide us with the obfuscated stack trace, we can point to you
> what to look for in the mapping file.
>
>
Hello,
I'm going to try.
In the mean time, do you think it could be related somehow with what below?

After engine upgrade to 3.6.1 from 3.6.0 I updated via yum the package
ovirt-engine-extension-aaa-jdbc, without running its own update phase (in
practice another engine-setup as I only have internal profile)
And this caused problems with the internal profile.
See also
https://bugzilla.redhat.com/show_bug.cgi?id=1293338

So I reverted the package to its previous version.
I'm now testing upgrade internal profile passing from
---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.1-1.el7 will be
updated

to
---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.4-1.el7 will be
an update

and following
/usr/share/doc/ovirt-engine-extension-aaa-jdbc-1.0.4/README.admin

So I put env in global maintenance, stopped engine and then run engine-setup

But it seems it remains stuck at
         ...
          Please confirm installation settings (OK, Cancel) [OK]:
[ INFO  ] Cleaning async tasks and compensations
          The following system tasks have been found running in the system:
          The following commands have been found running in the system:
          The following compensations have been found running in the system:

org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand
org.ovirt.engine.core.common.businessentities.StorageDomainStatic

org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand
org.ovirt.engine.core.common.businessentities.StorageDomainDynamic

org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand
org.ovirt.engine.core.common.businessentities.StorageDomainDynamic
          Would you like to try to wait for that?
          (Answering "no" will stop the upgrade (Yes, No) Yes
          Waiting for the completion of 3 running tasks during the next 20
seconds.
          Press Ctrl+C to interrupt.
          Waiting for the completion of 3 running tasks during the next 20
seconds.
          Press Ctrl+C to interrupt.
          Waiting for the completion of 3 running tasks during the next 20
seconds.
          Press Ctrl+C to interrupt.
          Waiting for the completion of 3 running tasks during the next 20
seconds.
          Press Ctrl+C to interrupt.

With "Ctrl+C" I interrupt engine-setup:
^C[ ERROR ] Failed to execute stage 'Setup validation': SIG2
[ INFO  ] Stage: Clean up
          Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151222145043-phm0eh.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20151222145643-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

If I see the log and compare with the output and execute the query
indicated inside the log I can effectively see inside the database:
engine=# select command_type, entity_type
engine-#                 from business_entity_snapshot
engine-# ;
                             command_type                              |

entity_type
-----------------------------------------------------------------------+----------------------------
----------------------------------------
 org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand |
org.ovirt.engine.core.commo
n.businessentities.StorageDomainStatic
 org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand |
org.ovirt.engine.core.commo
n.businessentities.StorageDomainDynamic
 org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand |
org.ovirt.engine.core.commo
n.businessentities.StorageDomainDynamic
(3 rows)

Can this in some way influence the exception I'm getting? O that perhaps it
is better to first solve this problem?

Let me know. I can downgrade again the ovirt-engine-extension-aaa-jdbc
package and try your suggestions instead and let see after the problem with
the extension.

Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20151222/4ed27ded/attachment-0001.html>