[system-tests] Add a test case for rebooting a node with LACP and other supported types of bonds

[Bogdan Dobrelya]

Original bug to be covered by this test https://bugs.launchpad.net/fuel/+bug/1453139

The test case is:
1) Create HA Neutron VLAN with 3 controllers with LACP (802.3ad layer2 slow) bonds and put management interfaces
inside of the bond.
2) Deploy env and check OSTF ha and sanity. It should pass.
3) Reboot any controller node and check connectivity via management network. It should present.

The test case should be applicable for all supported OS and bond types.

[Artem Panchenko (apanchenko-8)]

@Bogdan,

in order to test LACP bonds on VMs we need to have a support of bonding feature on hypervisor host. It requires Open vSwitch installed on node and also a lot of modifications in fuel-devops code are needed. So we can't implement such tests in 6.1 release scope, moving to 7.0.

[Bogdan Dobrelya (bogdando)]

Note, this is not a dup of https://bugs.launchpad.net/fuel/+bug/1319413.
I believe, this test case should be included into the acceptance testing of the 6.1, either manual or auto.

[Artem Panchenko (apanchenko-8)]

Created a case in 'Manual Release Acceptance 7.0' test suite which covers nodes reboot (with configured LACP bond) and verification of network settings. Nodes reboot with other supported types of bonds will be checked by automated tests.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/214724

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/214724
Committed: https://git.openstack.org/cgit/stackforge/fuel-qa/commit/?id=1fc6c84672957f08c149a02a6364f1df5ce5f5c8
Submitter: Jenkins
Branch: master

commit 1fc6c84672957f08c149a02a6364f1df5ce5f5c8
Author: Artem Panchenko <email address hidden>
Date: Wed Aug 19 20:17:12 2015 +0300

    Add net settings check after slaves restart

    In tests for bonding feature add additional steps
    after environment deployment:

      9. Save network configuration from slave nodes
     10. Reboot all environment nodes
     11. Verify that network configuration is the same
         after reboot

    Also fix error with incorrect network assignment to
    bonded interfaces (use 'private' instead of 'fixed').

    Change-Id: I34254d5df3a70fea58b993fd482d7e9de96ac77e
    Partial-bug: #1453702
    Closes-bug: #1485582