-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use PSI for running OpenShift 3.x tests #4288
Comments
If we manage to address #4242 elegantly (that is, odo code becoming more clear and maintainable w.r.t supporting multiple service backends - Svc Cat and Operator Hub), we can simply run the Service Catalog tests on minikube as proposed in #4287. All we will then have to do is bring up Svc Cat on minikube . IMO, that's what we should target. I don't see any other reason why we would want to test things on OCP 3.x. @kadel @girishramnani @mik-dass is there anything else we test on 3.x? |
$ minishift openshift component add service-catalog
$ minishift openshift component add automation-broker
$ minishift openshift component add template-service-broker This is ALL you need to enable Service Catalog on a Minishift VM. |
The following need to be achieved:
Create image: ssh to the image using the releng-key: Had problems to ssh:
Resolved by changing permissions on the local lib/common/releng-key file from 0644 to 0600
Install docker:
Setup Minishift by following:
Install minishift:
|
Error starting minishift:
Resolved by creating a GitHub API token (personal in this case) and add the env variable MINISHIFT_GITHUB_API_TOKEN using that token. |
Checking on it |
To setup virtualization env following:
|
|
sudo virsh net-start default Downloading ISO 'https://github.com/minishift/minishift-centos-iso/releases/download/v1.17.0/minishift-centos7.iso' |
As per https://www.docker.com/increase-rate-limits: If you are affected by these changes you will receive this error message: |
Trying a bit later:
|
after a while it gets operational
|
|
All tests for test-cmd-project PASSED All tests for test-cmd-service FAILED . Running them manually to check why they are failing
Moving along:
|
Tests are now passing on PSI minishift:
|
@rnapoles-rh I tried replicating the steps you mentioned above but
Might be I am doing something silly and end up with rate limit. Could please summarise e2e process/step in a single comment. |
Steps to setup OpenStack Linux VM:
Steps to run tests (scripts/minishift-all-tests.sh):
|
I am having problems to get minishift started: |
Created issue #4410 to track work for Jenkins configuration for running tests on PSI minishift |
For the issue of pulling images from docker.io, can you PTAL if But I could be wrong. |
Exploring |
Anjan suggested to use CDK. When starting minishift it timeouts waiting for condition:
Others have seen this problem (related to slow network connection: |
Went back to standard minishift due to the CDK (3.11) issues.
Checking with the PSI people |
I was able to bypass the docker pull limit by logging in to docker within the minishift VM and in the PSI vm itself, then exporting all required images by running:
Found this minishift issue where people were able to resolve this issue with fedora31. I will try on a fedora31 PSI VM |
When running provision-hosts.sh I get the following (debugging):
|
I was able to move forward from the previous errors, the ocp-ansible-machine instance got created, then it fail due to timeout waiting for it, so I ran the provision-hosts.sh script again and then it created the ocp-dns-machine. Failed again due to timeout, ran it again and now I get the following, note I changed the permissions on releng-key and releng-key pub to 600 and still get this:
|
3.11 provisioning failing with the following after creating all VM instances:
following up with Zeeshan Just started exploring cluster deployment in the ibm cloud. IBM cloud account created. Checking with Karel about budget. |
Onboarded to the IBM Cloud. Currently reviewing guidelines, documentation, and troubleshooting permissions. |
Created 4.7 cluster in the IBM Cloud. Looking on how to provision a 3.11 cluster (depreciated in IBM Cloud). Also checking how to onboard a robot account. Once we get a robot account in the IBM Cloud we can start using these clusters. |
|
Closing this issue as we don't support 3.11 and hence doesn't make sense to have test running on it. |
OpenShift 3.11 tests that were earlier working on Travis need to run on PSI infrastructure. This is mainly required to test Service Catalog.
/area testing
/priority high
Work pending for Sprint 198:
The required scrips are pending review in PR #4406. Once merged the corrsponding Jenkins job will be enabled to complete the setup for first run.
Acceptance criteria:
The text was updated successfully, but these errors were encountered: