Bug 403729 - [datamanager] policy flushing doesn't return srv connection status
Summary: [datamanager] policy flushing doesn't return srv connection status
Status: RESOLVED FIXED
Alias: None
Product: Mihini
Classification: IoT
Component: Agent (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P1 normal (vote)
Target Milestone: 0.9 M1   Edit
Assignee: Fabien Fleutot CLA
QA Contact: Robert Jacolin CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-19 05:17 EDT by Robert Jacolin CLA
Modified: 2013-05-22 10:57 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Jacolin CLA 2013-03-19 05:17:12 EDT 
one advantage to have a synchronous call to srvcon.connect() when flushing a policy is to have the result of data pushing to srv.
For now the result of srvcon.connect() is discarded. 
The result should be pushed to Flush users (i.e. to triggerpolicy callers through EMP)
Comment 1 Fabien Fleutot CLA 2013-04-04 06:39:55 EDT 
There seems to be a confusion, in the bug description, between connections and triggering:

* agent.srvcon.connect() will force a connection to the server, primarily to poll for incoming data, but won't trigger any data sending from the agent to the server;

* triggering a policy won't necessary force a connection, if as a result of the triggering no data needs to be sent to the server.

However, agent.srvcon.connect() should indeed return the connection status.
Comment 2 Fabien Fleutot CLA 2013-04-04 09:08:51 EDT 
done