Bug 1224804 - Summary: [offline] pull iptables-services where available
Summary: Summary: [offline] pull iptables-services where available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-host-deploy
Classification: oVirt
Component: General
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-3.6.0-rc
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On: 1224799
Blocks: 1230107
TreeView+ depends on / blocked
 
Reported: 2015-05-25 19:39 UTC by Alon Bar-Lev
Modified: 2016-04-19 10:54 UTC (History)
11 users (show)

Fixed In Version: OVIRT 3.6.0-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-19 10:54:55 UTC
oVirt Team: Infra
Embargoed:
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 41410 0 master MERGED offline: pull iptables-services where available Never

Description Alon Bar-Lev 2015-05-25 19:39:02 UTC 
Required for rhel-7.1 and fc-21(?)
Comment 1 Lukas Svaty 2015-11-26 15:22:22 UTC 
verified in  ovirt-host-deploy-offline-1.4.0-1.el7ev
Comment 2 Sandro Bonazzola 2015-11-27 07:49:24 UTC 
Since oVirt 3.6.0 has been released, moving from verified to closed current release.
Comment 3 Fabian Deutsch 2016-04-19 10:18:09 UTC 
Reopening, because this now needs to be handled by host-deploy (-offline was dropped).
Comment 4 Red Hat Bugzilla Rules Engine 2016-04-19 10:18:18 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 5 Sandro Bonazzola 2016-04-19 10:54:55 UTC 
Please open a new bug.
Avoiding to waste one hour restoring all the previous values in the BZ:

Target Release: 1.4.0
Target Milestone: ovirt-3.6.0-rc
Flags: ovirt-3.6.0+
Summary: [offline] pull iptables-services where available
Note You need to log in before you can comment on or make changes to this bug.