Returning wrong vagrant up status

[amitkrout]

This statement ``self.assertEqual(0, rc, "Vagrant up returned non-zero exit code")` returns 0 even if openshift service failed to start.

[amitkrout]

Environment :

System Version: Windows 10
Avocado 36.0lts

Steps to reproduce

1. Download latest CDK + hyperv provider on windows 10
2. Add the box and set the proxy (PROXY="ip:port", PROXY_USER="username",  
    PROXY_PASSWORD="password") 
2. Clone  "https://github.com/projectatomic/adb-tests" and modify the config.yaml 
    vagrant_VAGRANTFILE_DIR : ".../cdk/components/rhel/rhel-ose"
     vagrant_PROVIDER : "hyperv"
     vagrant_RHN_USERNAME : "usename"
     vagrant_RHN_PASSWORD : "password"
     openshift_lib_MODULE : ".../adb-tests/cdk-testsuite/libraries/openshift/openshift.py"
     openshift_util_MODULE : ".../adb-tests/cdk-testsuite/utils/openshiftUtils.py"
3. Go to the directory "/adb-tests/cdk-testsuite/tests" and execute the command 
    "avocado run vagrant_sanity.py -m ../config/config.yaml"

The first result will be (1/8) vagrant_sanity.py:VagrantSanity.test_vagrant_up: PASS (480.73 s) but the actual log throws the failure message.

.
.
==> default: Mounting folder via SSHFS: C:/Users/cdk => /c/Users/cdk
==> default: Checking Mount..
==> default: Folder Successfully Mounted!
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: Job for openshift.service failed because the control process exited with error code. See "systemctl status openshift.service" and "journalctl -xe" for details.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.