tree 015a29b81d341889b5605a52a532132760761931
parent 3efbe2df75807571305b24447d323056b4f03a5e
author Gunnar Mills <gmills@us.ibm.com> 1527888296 -0500
committer Gunnar Mills <gmills@us.ibm.com> 1528982359 -0500

Add reload 4 seconds after network set success

Since an IPV4 interface (e.g. IP address, gateway, or netmask) edit
is a delete then an add and the GUI can't calculate the interface
id (e.g. 5c083707) beforehand and it is not returned by the REST
call, reload the page after an edit, which makes another REST call.

Do this for all network changes, instead of just IPV4 interface
edits due to the possibility of a set network failing even
though it returned success, openbmc/openbmc#1641.

This REST call also updates dataService and old_interface
which is used to know which data has changed if the user
continues to edit network settings.

The issue this is solving is the GUI deletes the old IPV4
interface (5c083707), creates a new one (4d9b1add), then
let's say the user modifies the IPV4 interface again without
a refresh, the GUI doesn't know what old IPV4 interface to
delete (i.e. the GUI doesn't know to delete 4d9b1add).

Choose 4 seconds to give the network manager time to set
the network.

Tested: Did the above scenario.
Change-Id: I36cb438b12eb6540dc74f235f8f134df67e60389
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>