-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add worker node to run test operator on uni04delta-ipv6 deployments #403
Add worker node to run test operator on uni04delta-ipv6 deployments #403
Conversation
Hi @gmarcian. Thanks for your PR. I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/605f01ec091f444fb44e5598bc3cf611 ✔️ noop SUCCESS in 0s |
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/77b345f8b27c4b94894fb0ec2736c3a9 ✔️ noop SUCCESS in 0s |
7fd9d21
to
04d698a
Compare
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/cb8f76a23e4040518b98dade07c4f325 ✔️ noop SUCCESS in 0s |
rhoso-architecture-validate-uni04delta-ipv6 fails here
https://softwarefactory-project.io/zuul/t/rdoproject.org/build/26179debe63644d6bff1fc3873e5d9dd |
Is this still a draft? Has it been tested upstream and downstream? |
918e4d2
to
77ff71b
Compare
77ff71b
to
52f9c6c
Compare
I see that test failed. Shouldn't it pass before we merge it? |
So all uni04delta-ipv6 deployments will be able to run with four OCP nodes; i.e. 3 masters and 1 new worker node introduced by this patch? I see it's following the pattern used here: @arxcruz I'm assuming our testing nodes have the resources to handle the exta node. @tosky I'm assuming this won't cause problems for storage related tests in this DT. I'm OK with it provided we have the resources to handle it and others who depend on uni04delta-ipv6 are OK with it. |
I also echo John's question. |
@abays , @fultonj, a lot of tobiko tests failed, but IMO these failures are unrelated to this change. Part of them relate to some tobiko issue, another failures are since vms, created by these tests, are unreachable via their floating IPs, which is because of ipv6/ipv4 misconfiguration. |
So, it seems to be ready now. [4] https://gitlab.cee.redhat.com/ci-framework/ci-framework-jobs/-/merge_requests/1187 |
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.
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fultonj, gmarcian 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 |
Build succeeded (gate pipeline). ✔️ noop SUCCESS in 0s |
1100a50
into
openstack-k8s-operators:main
…er_unidelta_ipv6 Add worker node to run test operator on uni04delta-ipv6 deployments In order to run disruptive tests on the uni04delta env, We need to have a worker node dedicated for the test operator. Thus we can ensure that test pods won't be affected by the failures. Running disruptive tests is part of HA testing of the system. Please see OSPRH-7602 Reviewed-by: Andrew Bays <[email protected]> Reviewed-by: John Fulton <[email protected]>
Cherry-pick pull request #403 from gmarcian/add_worker_unidelta_ipv6 Add worker node to run test operator on uni04delta-ipv6 deployments In order to run disruptive tests on the uni04delta env, We need to have a worker node dedicated for the test operator. Thus we can ensure that test pods won't be affected by the failures. Running disruptive tests is part of HA testing of the system. Please see OSPRH-7602 Reviewed-by: Andrew Bays [email protected] Reviewed-by: John Fulton [email protected] Reviewed-by: Andrew Bays <[email protected]>
Please please next time squash all the changes, otherwise the git history becomes complicated to follow. This is a request to the reviewers too. |
Do you mean have Zuul squash everything when it merges, or ask the author to squash their commits? |
I would be more for "have the author present a clean history", as there may be cases where the original commits need to be preserved. But that's up to you. |
@tosky Ack. Can it be done from the github PR GUI? |
I'll leave the answer to others who know the github GUI, but I would say: no. Better rebase locally, you have more control (the operation is a local rebase of the history): https://about.gitlab.com/blog/2020/11/23/keep-git-history-clean-with-interactive-rebase/ (yes, the article is from gitlab.com, but it describes the step to execute with the git CLI tool). |
In order to run disruptive tests on the uni04delta env, We need to have a worker node dedicated for the test operator.
Thus we can ensure that test pods won't be affected by the failures.