-
Notifications
You must be signed in to change notification settings - Fork 87
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
🐛 Clusterclass e2e test fix #1671
🐛 Clusterclass e2e test fix #1671
Conversation
…configs Signed-off-by: Patryk Strusiewicz-Surmacki <[email protected]>
Signed-off-by: Patryk Strusiewicz-Surmacki <[email protected]>
Hi @p-strusiewiczsurmacki-mobica. Thanks for your PR. I'm waiting for a metal3-io 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/test-infra repository. |
/ok-to-test |
/metal3-centos-e2e-integration-test-main |
/test metal3-centos-e2e-integration-test-main |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kashifest 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 |
/test metal3-centos-e2e-integration-test-main |
The link to the centos e2e points to completely different PR. Anyways, ubuntu passed, |
@tuminoid: Overrode contexts on behalf of tuminoid: metal3-centos-e2e-integration-test-main 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. |
This PR is a followup to #1405
It fixes issues with redundant test env related vars and configs that couses the test to fail at start. Those were removed in #1624 and should be also removed for clusterclass.
Also, it tries to fix issue with
{{ ds.meta_data.hostname }}'
reference reported in the comment here.It seems that, according to the cluster-api repository,
NodeRegistration.Name
defaults to hostname, so I believe referencing hostname explicitly here is redundant and minght be deleted.