Bug 1071306

Summary: upgrade from 3.3.z + AIO to 3.4.0 cause AIO iptables rules to be dropped
Product: [Retired] oVirt Reporter: Sandro Bonazzola <sbonazzo>
Component: ovirt-engine-installerAssignee: Yedidyah Bar David <didi>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: medium    
Version: 3.4CC: alonbl, bugs, dfediuck, gklein, iheim, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-13 06:14:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
setup logs of the upgrade none

Description Sandro Bonazzola 2014-02-28 13:15:20 UTC
Created attachment 869059 [details]
setup logs of the upgrade

- installed 3.3.4 RC with AIO
- created a VM
- connected with spice
- shutdown the vm
- enabled 3.4.0-rc repo
- yum update
- engine-setup
- start the vm
- cannot connect anymore with spice

checked iptables, ports are not opened anymore.

workaround should be re-deploy the host. but if I do that, ovirt-host-deploy will remove iptables rules opening NFS ports.
So the only workaround is add again the missing ports by hand.

Comment 1 Alon Bar-Lev 2014-02-28 14:40:21 UTC
I do not think that upgrade was ever supported for aio.

Anyway, the iptables rules should be modified by setup not the host-deploy, and should include the aio rules if ever was installed.

Comment 2 Yedidyah Bar David 2014-10-13 06:14:41 UTC
bug 1109326 is on nfs ports, but the solution there is let the user review iptables changes, so applies here too.

*** This bug has been marked as a duplicate of bug 1109326 ***