Description of problem:
bonding-defaults.json (https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/bonding-defaults.json;hb=HEAD) provides some defaults for bonds.
As these are vendor/vdsm provided defaults it should not live inside /var/lib, rather in /usr/lib where a vendor can put his defaults.
/etc/vdsm/bonding-defaults.json could then be a place, which a user can use to override the defaults provided by vdsm.
Some background: this bug was opened when testing Vdsm in a container, where /var/lib is created afresh on startup.
/var/lib/vdsm/bonding-defaults.json is shipped with Vdsm only because creating it on Vdsm startup has conflicted with a currently-running NetworkManager (see commit message of http://gerrit.ovirt.org/33403).
Until NetworkManager is convinced not to touche our reference bond, we'd better move the json file to /usr/lib/vdsm.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
How this bug should be tested? Thanks
verify that `rpm -ql vdsm |grep /var/lib/vdsm` is empty, yet `vdsm-tool dump-bonding` works, as well as Vdsm as a whole.
Verified on - vdsm-4.17.999-909.git28d724a.el7.centos.noarch
oVirt 4.0.0 has been released, closing current release.