Bug 1062318

There are patches, but are there any nightly builds that I can test?

The patches are incomplete and abandoned, so there isn't anything that can be tested.

Are you interested in working in this?

Nah, I'm just an user, who inadvertently upgraded his engine box to Fedora 20. I have no java skills to solve this issue by myself.

If you want to use Fedora 20 you can download the .zip version of JBoss AS 7 from here:

  http://download.jboss.org/jbossas/7.1/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final.zip

Uncompress it somewhere:

  unzip boss-as-7.1.1.Final.zip -d /usr/share

Then you can modify the engine configuration to use that version of the application server instead of the default one. Go to /etc/ovirt-engine/engine.conf.d and modify the JBOSS_HOME variable in the 10-setup-jboss.conf file:

  JBOSS_HOME="/usr/share/jboss-as-7.1.1.Final"

After that restart the ovirt-engine service.

Thanks for help, but it didn't work. Although ovirt-engine.service is up, the web interface is not available. Startup generated close to 100 KB of logs, of which the following look relevant:

2014-04-07 11:25:54,886 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "en
gine.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"engine.ear
\".\"bll.jar\".component.InitBackendServicesOnStartupBean.START" => "org.jboss.msc.service.StartException in service jbo
ss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.InitBackendServicesOnStartupBean.START: Failed to start servi
ce"}}

Fedora 20 isn't currently supported, but I use it every day without problems, using the workaround I described in comment 5. Can you clean the logs, try to start again and then attach the logs? We will need /var/log/ovirt-engine/boot.log, /var/log/ovirt-engine/server.log and /var/log/ovirt-engine/engine.log.

Created attachment 883555 [details]
boot.log

Created attachment 883556 [details]
engine.log

Created attachment 883557 [details]
server.log

The relevant log message in this case is this one:

  org.postgresql.util.PSQLException: The column name ha_configured was not found in this ResultSet.

This database column was added in 3.4, so this means that the version of the engine that you are using doesn't match the database schema. Either you updated the packages without re-running "engine-setup" or you recovered an old database backup.

Oh, operator error. After I run "engine-setup   --jboss-home=/usr/share/jboss-as-7.1.1.Final" it indeed worked.
Thank you for this workaround!

closing this as its not supported yet, and we'll track this properly in the future.

I just did 'cd /usr/share; ln -s wildfly jboss-as'

So far so good...

nm, fails to start with Wildfly:

[root@vm-130 tmp]# less /var/log/ovirt-engine/boot.log 
11:56:59,862 INFO  [org.jboss.modules] JBoss Modules version 1.3.0.Final
11:57:01,179 INFO  [org.jboss.msc] JBoss MSC version 1.2.0.Beta1
11:57:01,272 INFO  [org.jboss.as] JBAS015899: WildFly 8.0.0.Final "WildFly" starting
11:57:01,798 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
Caused by: javax.xml.stream.XMLStreamException: JBAS014674: Failed to load module org.jboss.as.web
        at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:155) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:325) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:137) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper.jar:1.1.0.Final]
        at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper.jar:1.1.0.Final]
        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        ... 3 more
Caused by: java.util.concurrent.ExecutionException: java.lang.UnsupportedOperationException: JBAS013452: Legacy extension 'org.jboss.as.web' is not supported on servers running this version. The extension is only supported for use by hosts running a previous release in a mixed-version managed domain
        at java.util.concurrent.FutureTask.report(FutureTask.java:122) [rt.jar:1.7.0_55]
        at java.util.concurrent.FutureTask.get(FutureTask.java:188) [rt.jar:1.7.0_55]
        at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:147) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        ... 9 more
Caused by: java.lang.UnsupportedOperationException: JBAS013452: Legacy extension 'org.jboss.as.web' is not supported on servers running this version. The extension is only supported for use by hosts running a previous release in a mixed-version managed domain
        at org.jboss.as.controller.extension.AbstractLegacyExtension.initializeParsers(AbstractLegacyExtension.java:82) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:183) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:69) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:127) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:124) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
        at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_55]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads.jar:2.1.0.Final]

This was good enough for the very specific case I wanted to test (just needed to run engine-setup). The service starts fine using the JBoss AS7 workaround from comment #5.