-
Notifications
You must be signed in to change notification settings - Fork 16
Investigate the behaviour of Openshift features on CI #415
Comments
@hferentschik I have updated the test to successfully run
as I found it is related to minimum memory requirement for Openshift #420 . However, there is one test case which still need to be investigated.
We can keep this issue open till we found the reason of the above test case failure. |
We also found that there is some wait time (~20s in dev machine) required in between We need to investigate the root cause for this delay requirement. |
Even the CDK OpenShift test fails after upgrading to the latest CDK box. |
For the record, the initial problem was that the tests were not configured to run against CDK. Hence, it looked like they were running and passing, but in reality they got skipped. This was hidden by issue #419. We were using the default pretty formatter without coloring which did not indicate which tests got run and which test got skipped. |
It seems there is a regression in the OpenShift service startup which leads to the fact that the OpenShift status is not directly "running" after a successful 'vagrant up'. |
So using CDK 2.2, the Vagrant configuration from adb-atomic-developer-bundle and running:
I get:
OpenShift service is reported to be running. Then running a few seconds later:
So the OpenShift provisioning seems to return too early. This is consistent with the behavior we see in the tests. |
It does not matter whether I use:
or just
|
And this is only seen with CDK 2.2 but not CDK 2.1. |
AFAICT yes |
CDK 2.1 behavior:
|
CDK 2.2 with
|
@budhrg so you are saying that with calling systemctl directly it works? In this case we are dealing with a sccli bug, right? |
@budhrg If it works with systemctl we can change the Vagrant config in the respective feature files to use systemctl. At least this is better than a "random" sleep. We can add a comment to the issue in developer-bundle and update the tests once we have a fix there. WDYT? |
@budhrg nice digging ;-) |
Blocked on projectatomic/adb-utils#194 |
We don't have to be blocked, right? See #415 (comment) |
But don't you think it is like diverting from actual behavior? I feel like we are doing some hack on our tests to make it pass 😄 WDYT? @LalatenduMohanty |
This is for sure better than a sleep. Also the tests are about service-manager not about the VM. For our purposes we need a properly provisioned OpenShift. If we can get this vis systemctl so be it. I also rather do this and have the CDK tests running opposed to skipping them completely atm. |
@hferentschik Somehow now I am not able to get Even same reported by CI too https://ci.centos.org/job/vagrant-service-manager-budh/20/console Locally it is passing now sometimes. Even tests are passing locally
Don't know whats happening in CI. 😕 |
It seems it does not fail in cases where the tests are wrong, eg When I evaluate and run
bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0 --path #{ENV['VAGRANT_HOME']}/oc
should fail, but did not.We can temporarily change the CI job to build one of our forks on which we can introduce some obvious test errors. We need to verify that this will result in test failures.
The text was updated successfully, but these errors were encountered: