[Users] engine-setup fails when trying to setup ovirt-engine-reports

Hello! After upgrade to 3.4.0, removed ovirt-engine-reports-3.3.4 and any subsequent packaged, then install ovirt-engine-reports-3.4.0-2.fc19.noarch and dependenciees, run engine-setup and got "engine-setup Failed to execute stage 'Misc configuration': Command './js-ant' failed to execute" a second run on engine-setup raised: "[ ERROR ] Failed to execute stage 'Environment setup': initial_value must be unicode or None, not str" Relevant (I think) lines from first try ( grep -i error): 2014-04-03 09:13:07 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'False' 2014-04-03 09:13:13 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'False' ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36084 OperationalError: FATAL: password authentication failed for user "ovirt_engine_history" 2014-04-03 09:17:56 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'False' └─1209 ovirt-engine -server -XX:+TieredCompilation -Xms1g -Xmx1g -XX:PermSize=256m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Djsse.enableSNIExtension=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/ovirt-engine/dump -Djava.util.logging.manager=org.jboss.logmanager -Dlogging.configuration=file:///var/tmp/ovirt-engine/config/ovirt-engine-logging.properties -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.modules.write-indexes=false -Djboss.server.default.config=ovirt-engine -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=/usr/share/ovirt-engine -Djboss.server.data.dir=/var/lib/ovirt-engine -Djboss.server.log.dir=/var/log/ovirt-engine -Djboss.server.config.dir=/var/tmp/ovirt-engine/config -Djboss.server.temp.dir=/var/tmp/ovirt-engine/tmp -Djboss.controller.temp.dir=/var/tmp/ovirt-engine/tmp -jar /usr/share/jboss-as/jboss-modules.jar -mp /var/tmp/ovirt-engine/modules/00-ovirt-engine-modules:/var/tmp/ovirt-engine/modules/01-ovirt-engine-reports-modules:/var/tmp/ovirt-engine/modules/02-jboss-as-modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -c ovirt-engine.xml LoadState=error LoadState=error LoadState=error -- -- This should be written to an error var or include object_id that is missing SELECT setval('vdc_db_log_seq', max(error_id)) FROM vdc_db_log; select fn_db_add_config_value('AbortMigrationOnError','false','3.0'); select fn_db_add_config_value('AbortMigrationOnError','false','3.1'); select fn_db_add_config_value('AbortMigrationOnError','false','3.2'); select fn_db_add_config_value('AbortMigrationOnError','false','3.3'); select fn_db_delete_config_value('RedirectServletReportsPageError','general'); select fn_db_delete_config_value('RenewGuestIpOnVdsSubnetChangeOnParseError','general'); select fn_db_delete_config_value('VdsErrorsFileName','general'); base_disks.propagate_errors, images_storage_domain_view.disk_interface as disk_interface, images_storage_domain_view.boot as boot, images_storage_domain_view.wipe_after_delete as wipe_after_delete, images_storage_domain_view.propagate_errors as propagate_errors, images_storage_domain_view.sgio as sgio, bd.propagate_errors, vds_groups.transparent_hugepages, vds_groups.migrate_on_error, vds_groups.architecture, vm_images_view.boot, vm_images_view.wipe_after_delete, vm_images_view.propagate_errors, vm_images_view.entity_type, vm_images_view.number_of_vms, vm_images_view.vm_names, vm_images_view.quota_id, v_propagate_errors VARCHAR(32), propagate_errors, v_propagate_errors, v_propagate_errors VARCHAR(32), propagate_errors = v_propagate_errors, v_migrate_on_error INTEGER, transparent_hugepages, migrate_on_error, virt_service, gluster_service, tunnel_migration, emulated_machine, detect_emulated_machine, trusted_service, ha_reservation, cluster_policy_id, v_transparent_hugepages, v_migrate_on_error, v_virt_service, v_gluster_service, v_tunnel_migration, v_emulated_machine, v_detect_emulated_machine, v_trusted_service, v_ha_reservation, v_cluster_policy_id, v_cluster_policy_custom_properties, v_enable_balloon, v_migrate_on_error INTEGER, migrate_on_error = v_migrate_on_error, ALTER DATABASE "ovirt_engine_history_20140403091836" SET client_min_messages=ERROR; RuntimeError: Command './js-ant' failed to execute 2014-04-03 09:21:44 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Misc configuration': Command './js-ant' failed to execute psql:/var/lib/ovirt-engine/backups/engine-20140403091925._LX2Dn.sql:22: ERROR: must be owner of extension plpgsql 2014-04-03 09:23:59 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'True' 2014-04-03 09:23:59 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Command './js-ant' failed to execute",), <traceback object at 0x3500170>)]' 2014-04-03 09:23:59 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'True' 2014-04-03 09:23:59 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Command './js-ant' failed to execute",), <traceback object at 0x3500170>)]' 2014-04-03 09:23:59 ERROR otopi.plugins.ovirt_engine_common.base.core.misc misc._terminate:150 Execution of setup failed "

----- Original Message -----
From: "Gabi C" <gabicr@gmail.com> To: users@ovirt.org Sent: Thursday, April 3, 2014 9:53:36 AM Subject: [Users] engine-setup fails when trying to setup ovirt-engine-reports
Hello!
After upgrade to 3.4.0, removed ovirt-engine-reports-3.3.4 and any subsequent packaged, then install ovirt-engine-reports-3.4.0-2.fc19.noarch and dependenciees, run engine-setup and got
"engine-setup Failed to execute stage 'Misc configuration': Command './js-ant' failed to execute"
a second run on engine-setup raised:
"[ ERROR ] Failed to execute stage 'Environment setup': initial_value must be unicode or None, not str"
Probably fixed by [1]. You can try applying it directly and see if it solves, or use the snapshot repo, or wait till 3.4.1 :-) If it does not solve, please send the whole log. grepping for just error does not show what specific run of js-ant failed (there might be a few) and why. [1] http://gerrit.ovirt.org/26005 Thanks for the report! -- Didi
participants (2)
-
Gabi C
-
Yedidyah Bar David