-
Notifications
You must be signed in to change notification settings - Fork 278
🏃 migrate conformance test to Prow #759
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
🏃 migrate conformance test to Prow #759
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
recheck |
/test ? |
@sbueringer: The following commands are available to trigger jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test pull-cluster-api-provider-openstack-make-conformance |
2 similar comments
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
9 similar comments
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
/test pull-cluster-api-provider-openstack-make-conformance |
ee960cb
to
28d062b
Compare
/test pull-cluster-api-provider-openstack-make-conformance |
1 similar comment
/test pull-cluster-api-provider-openstack-make-conformance |
f67ddf3
to
662f4d8
Compare
/test pull-cluster-api-provider-openstack-make-conformance @hidekazuna @jichenjc This PR is now ready for review. Finally we will get stable e2e/conformance tests... :) |
/lgtm |
@@ -84,6 +84,14 @@ spec: | |||
echo "kubelet version: " $(kubelet --version) | |||
|
|||
echo "$LINE_SEPARATOR" | |||
users: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We moved to use OpenStack key pair, why do we need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some discussion has been previously
at least from my test, seems only this user can logon .. I might be wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasnt able to log in with the root user during testing, so I thought I make it easier by adding an additional user with pw which works in any case (also via vnc and password Login)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(because the root user ssh login is disabled)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you are not able to login to nodes due to dropbear in cirros 0.5.1.
After I copied openssh private key into bastion, I had to convert it to dropbear format by dropbearconvert command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A set of PRs blocked (waiting) for this , it's not blocking issue, can we merge this and open a follow up issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be possible. I started working on: #782
There I add e2e tests and rewrite our conformance test to be executed with ClusterAPI test framework (like e.g. in CAPA)
I try to use the OpenStack SSH KeyPair mechanism there. Let's how it goes this time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it shouldn't block this PR but I'm really wondering how the OpenStack ssh key solution works:
When I try to jump to a regular node (e.g. a control plane node):
- root has the ssh key but blocks ssh
- ubuntu does not have the ssh key in authorized keys
Anything special I have to consider when using the OpenStack keypair? (I'm just creating it in OpenStack and then trying to jump, but it cannot work if it's just added for the root user and the root user is blocked)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is OK to add an user to use VNC when running test.
I think we can not login as root user. cirros user for cirros image, ubuntu user for ubuntu image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But how do you do that with the openstack keypair feature? Cirros works for me but ubuntu does not
openstack domain list | ||
|
||
openstack flavor delete m1.tiny | ||
openstack flavor create --ram 512 --disk 1 --vcpus 1 --public --id 1 m1.tiny --property hw_rng:allowed='True' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need --property hw_rng:allowed='True'?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I'm still using devstack, I assume yes
/test pull-cluster-api-provider-openstack-make-conformance |
@jichenjc @hidekazuna review comments addressed - please take another look :) |
/test pull-cluster-api-provider-openstack-make-conformance |
@hidekazuna @jichenjc can we merge this pr? It would unblock a lot. We can continue the ssh discussion elsewhere |
Sure /hold cancel /lgtm |
/hold |
250d2bb
to
c7aec80
Compare
@hidekazuna I forgot to squash (I didn't want to have 12 commits on master :)). Can you give me another /lgtm? Thx :) |
/lgtm /hold cancel |
test-infra PR has to be approved first: kubernetes/test-infra#21069
Also includes the v1alpha4 PR until it's merged
With this PR we have a Prow-based e2e test which creates a devstack in GCP instead of OpenLab (conformance test is almost the same)
/hold