Back to bug 1007417

Who When What Removed Added
Mike Burns 2013-09-12 13:01:04 UTC Priority high urgent
Assignee mburns fdeutsch
Severity high urgent
Fabian Deutsch 2013-09-12 13:12:35 UTC Status NEW ASSIGNED
Ying Cui 2013-09-13 01:53:51 UTC CC ycui
Ying Cui 2013-09-13 01:55:08 UTC CC cshao, gouyang, hadong, huiwa, leiwang
Fabian Deutsch 2013-09-13 07:32:59 UTC Link ID oVirt gerrit 19204
Fabian Deutsch 2013-09-13 16:44:11 UTC Status ASSIGNED POST
Mike Burns 2013-09-30 18:09:41 UTC Status POST MODIFIED
Fixed In Version ovirt-node-3.0.1-2.el6
errata-xmlrpc 2013-10-02 15:12:33 UTC Status MODIFIED ON_QA
Cheryn Tan 2013-11-08 00:25:05 UTC CC fdeutsch
Flags needinfo?(fdeutsch)
Cheryn Tan 2013-11-08 00:29:21 UTC Flags needinfo?(fdeutsch)
Guohua Ouyang 2013-11-11 08:48:04 UTC Status ON_QA VERIFIED
Charlie 2013-11-26 04:47:09 UTC CC cboyle
Doc Text When the hypervisor got approved on the manager it changed its state to Non Responsive. This was caused by the port being opened but the change not being saved saved. This lead to a situation where the iptables service got restarted and
overwritten/closed the previously opened ports.

Now the configuration is saved (and persisted) after a port is opened.
Charlie 2013-11-26 04:55:38 UTC Doc Text When the hypervisor got approved on the manager it changed its state to Non Responsive. This was caused by the port being opened but the change not being saved saved. This lead to a situation where the iptables service got restarted and
overwritten/closed the previously opened ports.

Now the configuration is saved (and persisted) after a port is opened.
When the hypervisor got approved on the manager it changed its state to Non Responsive. This was caused by the port being opened but the change not being saved saved. This lead to a situation where the iptables service got restarted and
overwritten/closed the previously opened ports. Now the configuration is saved (and persisted) after a port is opened.
Charlie 2013-11-26 04:57:23 UTC Doc Text When the hypervisor got approved on the manager it changed its state to Non Responsive. This was caused by the port being opened but the change not being saved saved. This lead to a situation where the iptables service got restarted and
overwritten/closed the previously opened ports. Now the configuration is saved (and persisted) after a port is opened.
When the hypervisor got approved on the manager it changed its state to Non Responsive. This was caused by the port being opened but the change not being saved saved. This lead to a situation where the iptables service got restarted and overwrote/closed the previously opened ports. Now the configuration is saved (and persisted) after a port is opened.
Fabian Deutsch 2013-12-11 08:30:59 UTC Flags needinfo?(fdeutsch) needinfo?(fdeutsch)
errata-xmlrpc 2014-01-21 15:32:22 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2014-01-21 19:49:53 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-01-21 14:49:53 UTC

Back to bug 1007417