Bug 1049622

I can't reproduce this following provided steps.
Just renaming cacert.conf is not enough, I think that you should have been using also non standard ports for apache, causing updateAIA to be called in legacy module.

Reproduced upgrading from 3.1 -> 3.2 -> 3.3 using JBoss on port 8700 and 8701.
After rollback engine-setup questions differs from clean upgrade only for:

 - Host fully qualified DNS name of this server

remaining questions:
 - Do you want Setup to configure the firewall?
 - Configure an NFS share on this server to be used as an ISO Domain?
 - Configure WebSocket Proxy on this machine?
 - Would you like transactions from the Red Hat Access Plugin sent from the RHEV Manager to be brokered through a proxy server?

are there because they're introducing support for new features or features not enabled on existing setup.

Looking on why Host fully qualified DNS name of this server is asked after rollback but it doesn't seem to be a blocker IMHO.

(In reply to Sandro Bonazzola from comment #2)
> Reproduced upgrading from 3.1 -> 3.2 -> 3.3 using JBoss on port 8700 and
> 8701.
> After rollback engine-setup questions differs from clean upgrade only for:
> 
>  - Host fully qualified DNS name of this server
> 
> remaining questions:
>  - Do you want Setup to configure the firewall?
>  - Configure an NFS share on this server to be used as an ISO Domain?
>  - Configure WebSocket Proxy on this machine?
>  - Would you like transactions from the Red Hat Access Plugin sent from the
> RHEV Manager to be brokered through a proxy server?
> 
> are there because they're introducing support for new features or features
> not enabled on existing setup.
> 
> Looking on why Host fully qualified DNS name of this server is asked after
> rollback but it doesn't seem to be a blocker IMHO.

I recommend that you backup /etc before the upgrade attempt and diff -ubr to see what changed. You might find other changes that are not obvious when re-running setup but are still significant.

On upgrade FQDN is read from /etc/sysconfig/ovirt-engine on customization stage.

On failure, after rollback, /etc/sysconfig/ovirt-engine is empty and previous version is in /etc/sysconfig/ovirt-engine.rpmsave

We're missing /etc/sysconfig/ovirt-engine rollback.

Created attachment 847658 [details]
engine + server + setup logs

Reproduced by entering non valid db upgarde script
(/usr/share/ovirt-engine/dbscripts/upgrade/03_02_0470_test_me.sql which contains some randomized / meaningless strings) - system was configured with remote db.

I was asked the following questions during the 2nd upgarde try:
Host fully qualified DNS name of this server
Do you want Setup to configure the firewall
Where is the database located?

When remote option is selected - I'm getting the install message:

ATTENTION
         
          Manual action required.
          Please create database for ovirt-engine use. Use the following commands as an example:
.....


while my DB has different attribute, as it was created by previous version convention.


IMHO, this one is an urgent blocker - upgrade failure, put rhevm in non working, non upgradable state.

verified on 
rhevm-setup-3.3.0-0.45.el6ev.noarch
rhevm-3.3.0-0.45.el6ev.noarch


- Installed 3.2.5
- While installation i answered not to override httpd configuration
- mv /etc/pki/ovirt-engine/cacert.conf /etc/pki/ovirt-engine/cacert.conf.bak
- yum update rhevm-setup to 3.3
- rhevm-setup failed and rolled back to 3.2.5
-  mv /etc/pki/ovirt-engine/cacert.conf.bak /etc/pki/ovirt-engine/cacert.conf
- ran rhevm-setup again - it succeeded and did not ask too many questions

Closing - RHEV 3.3 Released

Closing - RHEV 3.3 Released

Closing - RHEV 3.3 Released