Intermittent failure when in 'poecli cfg -s'

[rothcar]

There appears to be some sort of timing/race condition between poecli set and poecli cfg -s. If the poed config is saved shortly after a recent set command the port settings are not correctly reflected in the saved config. In all cases the actual poed state is correct (the poecli set command did work).

Try the following:

poecli set -e 1 -p 1-48
poecli cfg -s
grep -c "enable" /etc/poe_agent/poe_perm_cfg.json
poecli set -e 0 -p 1-48
poecli cfg -s
grep -c "enable" /etc/poe_agent/poe_perm_cfg.json
...

That is, if you repeatedly enable then disable all ports, with a config-save in-between, you should see alternately '0' and '48' printed out above. What actually happens is that the number of enabled ports is incorrect (not the expected '0' or '48') and there is a corresponding error in the poed systemd journal to the effect of "unable to save config".

[leonchiang]

Because the poecli cfg -s command action is copy the /run/poe_runtime_cfg.json to /etc/poe_agent/poe_perm_cfg.json,
it need waiting the /run/poe_runtime_cfg.json file updated in approximately 4~8s after last set command exit.
We've update the waiting flow in poecli cfg save/load, you can check the last PR #22