Bug 1071306 - upgrade from 3.3.z + AIO to 3.4.0 cause AIO iptables rules to be dropped
Summary: upgrade from 3.3.z + AIO to 3.4.0 cause AIO iptables rules to be dropped
Keywords:
Status: CLOSED DUPLICATE of bug 1109326
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 3.6.0
Assignee: Yedidyah Bar David
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-28 13:15 UTC by Sandro Bonazzola
Modified: 2014-10-13 06:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-13 06:14:41 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)
setup logs of the upgrade (2.34 MB, text/x-log)
2014-02-28 13:15 UTC, Sandro Bonazzola 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.