Why vdsm script reset network configuration on every reboot based on predefined bond interface after updating from Red Hat Gluster Storage 3.0 Update 3 to Red Hat Gluster Storage 3.0 Update 4 ?

Issue

• Why vdsm script reset network configuration on every reboot based on predefined bond interface ?

• Service vdsmd failed to start after upgrading from RHS 3.0 Update 3 to RHS 3.0 Update 4,

~ Snippet from terminal:

[root@rhs3 ~]# service vdsmd start
initctl: Job is already running: libvirtd
vdsm: Running mkdirs
vdsm: Running configure_coredump
vdsm: Running configure_vdsm_logs
vdsm: Running wait_for_network
vdsm: Running run_init_hooks
vdsm: Running upgraded_version_check
vdsm: Running check_is_configured
libvirt is already configured for vdsm
vdsm: Running validate_configuration
SUCCESS: ssl configured to true. No conflicts
vdsm: Running prepare_transient_repository
vdsm: Running syslog_available
vdsm: Running nwfilter
vdsm: Running dummybr
vdsm: Running load_needed_modules
vdsm: Running tune_system
vdsm: Running test_space
vdsm: Running test_lo
vdsm: Running unified_network_persistence_upgrade
vdsm: Running restore_nets
Traceback (most recent call last):
  File "/usr/share/vdsm/vdsm-restore-net-config", line 137, in <module>
    restore()
  File "/usr/share/vdsm/vdsm-restore-net-config", line 123, in restore
    unified_restoration()
  File "/usr/share/vdsm/vdsm-restore-net-config", line 66, in unified_restoration
    persistentConfig.bonds)
  File "/usr/share/vdsm/vdsm-restore-net-config", line 91, in _filter_nets_bonds
    bonds[bond]['nics'], net)
KeyError: u'bond0'
vdsm: stopped during execute restore_nets task (task returned with error code 1).
vdsm start                                                 [FAILED]