Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1065172

Summary: [RFE][neutron]: Child processes status on agents
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-neutronAssignee: Miguel Angel Ajo <mangelajo>
Status: CLOSED UPSTREAM QA Contact: Ofer Blaut <oblaut>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: chrisw, lpeer, majopela, markmc, nyechiel, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/agent-child-processes-status
Whiteboard: upstream_milestone_kilo-3 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 11:26:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1106489    

Description RHOS Integration 2014-02-14 05:07:34 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/agent-child-processes-status.

Description:

Poll/wait for child processes status in order to report using the mechanism provided
in the agent-service-status blueprint:

https://blueprints.launchpad.net/neutron/+spec/agent-service-status

We could add a thread that checks periodically (configurable parameter)
for the child processes being alive, if they die, we start notifying this 
condition.

Specification URL (additional information):

None

Comment 1 Nir Yechiel 2014-03-06 13:51:59 UTC
Updating based on u/s status

Comment 2 Miguel Angel Ajo 2014-07-14 11:41:05 UTC
I'm setting this bug as duplicate, since we are addressing this on a different bz.
bz#1106489

Comment 3 Miguel Angel Ajo 2014-07-14 11:42:03 UTC
(In reply to Miguel Angel Ajo from comment #2)
> I'm setting this bug as duplicate, since we are addressing this on a
> different bz.
> bz#1106489

It makes more sense to set this one as a blocker on the other.

Comment 4 lpeer 2015-03-19 11:26:43 UTC
This RFE was automatically opened to track status of upstream development.
At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.