Back to bug 1033249

Who When What Removed Added
RHEL Program Management 2013-11-21 19:31:29 UTC Target Release --- 4.0
Jason Guiditta 2013-11-21 20:09:32 UTC CC jguiditt
Dominic Cleal 2013-11-22 10:20:40 UTC CC dcleal
Component foreman openstack-foreman-installer
Mike Orazi 2013-11-22 21:22:00 UTC CC morazi
Assignee jomara jguiditt
Mike Orazi 2013-11-22 22:15:30 UTC Status NEW ASSIGNED
Jason Guiditta 2013-11-25 21:49:26 UTC CC sreichar
Jiri Stransky 2013-11-29 16:29:32 UTC CC jstransk
Jason Guiditta 2013-12-02 19:39:37 UTC Status ASSIGNED POST
Lon Hohberger 2013-12-05 15:52:09 UTC Status POST MODIFIED
Fixed In Version openstack-foreman-installer-0.0.23-1.el6ost
yeylon 2013-12-06 15:35:52 UTC QA Contact ajeain oblaut
errata-xmlrpc 2013-12-06 19:36:28 UTC Status MODIFIED ON_QA
Perry Myers 2013-12-07 13:43:25 UTC Blocks 1039278
Bruce Reeler 2013-12-09 07:39:36 UTC CC breeler
Flags needinfo?(jguiditt)
Ofer Blaut 2013-12-10 15:37:38 UTC Keywords OtherQA
Scott Lewis 2013-12-16 18:40:48 UTC Target Milestone --- rc
Jason Guiditta 2013-12-17 19:53:18 UTC Doc Text Feature: Add ability to configure the name of the ovs bridge and whether to expect an IP associated with this or not.

Reason: Previously there was a hardcoded assumption about the setup of the user's NIC on the networker. If the user wanted to use a different configuration than assumed, it was unsupported

Result: User can now name the bridge as desired, and decide for them selves if they wish to have an IP associated with it or not
Doc Type Bug Fix Enhancement
Flags needinfo?(jguiditt)
Martin Lopes 2013-12-18 04:07:04 UTC CC mlopes
Doc Text Feature: Add ability to configure the name of the ovs bridge and whether to expect an IP associated with this or not.

Reason: Previously there was a hardcoded assumption about the setup of the user's NIC on the networker. If the user wanted to use a different configuration than assumed, it was unsupported

Result: User can now name the bridge as desired, and decide for them selves if they wish to have an IP associated with it or not
With this update, OVS bridge name and associated IP values are no longer hardcoded assumptions. OVS bridges can now be renamed, and IP association is now optional.
Crag Wolfe 2013-12-18 22:23:39 UTC Status ON_QA VERIFIED
CC cwolfe
errata-xmlrpc 2013-12-19 17:41:30 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:38:23 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:38:23 UTC

Back to bug 1033249