Skip to content
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

Failing tests for pull-machine-controller-e2e-hetzner #1710

Closed
ahmedwaleedmalik opened this issue Oct 5, 2023 · 1 comment
Closed

Failing tests for pull-machine-controller-e2e-hetzner #1710

ahmedwaleedmalik opened this issue Oct 5, 2023 · 1 comment

Comments

@ahmedwaleedmalik
Copy link
Member

ahmedwaleedmalik commented Oct 5, 2023

PR Reference: #1709

  • Logs for pull-machine-controller-e2e-hetzner :
=== NAME  TestHetznerProvisioningE2E/centos-1.26.9
    helper.go:298: verify failed due to error=failed to verify creation of node for MachineDeployment: failed waiting for MachineDeployment centos-1-26-9-hz-1709844180999606272 to get a node: context deadline exceeded (expected to find a node for MachineDeployment "centos-1-26-9-hz-1709844180999606272" but Machine "centos-1-26-9-hz-1709844180999606272-5f697f799c-qj74z" has no address yet, indicating instance creation at the provider failed)
=== NAME  TestHetznerProvisioningE2E/centos-1.27.6
    helper.go:298: verify failed due to error=failed to verify creation of node for MachineDeployment: failed waiting for MachineDeployment centos-1-27-6-hz-1709844180999606272 to get a node: context deadline exceeded (expected to find a node for MachineDeployment "centos-1-27-6-hz-1709844180999606272" but Machine "centos-1-27-6-hz-1709844180999606272-55db7db7f7-qbsj2" has no address yet, indicating instance creation at the provider failed)
=== NAME  TestHetznerProvisioningE2E/centos-1.28.2
    helper.go:298: verify failed due to error=failed to verify creation of node for MachineDeployment: failed waiting for MachineDeployment centos-1-28-2-hz-1709844180999606272 to get a node: context deadline exceeded (expected to find a node for MachineDeployment "centos-1-28-2-hz-1709844180999606272" but Machine "centos-1-28-2-hz-1709844180999606272-554d9c65bc-z6ngz" has no address yet, indicating instance creation at the provider failed)
--- FAIL: TestHetznerProvisioningE2E (0.00s)
    --- PASS: TestHetznerProvisioningE2E/migrateUID (16.08s)
    --- PASS: TestHetznerProvisioningE2E/ubuntu-1.26.9 (215.09s)
    --- PASS: TestHetznerProvisioningE2E/rockylinux-1.28.2 (228.63s)
    --- PASS: TestHetznerProvisioningE2E/ubuntu-1.28.2 (230.06s)
    --- PASS: TestHetznerProvisioningE2E/rockylinux-1.26.9 (243.85s)
    --- PASS: TestHetznerProvisioningE2E/rockylinux-1.27.6 (245.14s)
    --- PASS: TestHetznerProvisioningE2E/ubuntu-1.27.6 (1758.74s)
    --- FAIL: TestHetznerProvisioningE2E/centos-1.26.9 (2103.83s)
    --- FAIL: TestHetznerProvisioningE2E/centos-1.27.6 (2104.67s)
    --- FAIL: TestHetznerProvisioningE2E/centos-1.28.2 (2105.38s)
FAIL
FAIL	github.com/kubermatic/machine-controller/test/e2e/provisioning	2105.611s
FAIL
@ahmedwaleedmalik ahmedwaleedmalik changed the title Failing tests for pull-machine-controller-e2e-aws-ebs-encryption-enabled and pull-machine-controller-e2e-hetzner Failing tests for pull-machine-controller-e2e-hetzner Oct 5, 2023
@ahmedwaleedmalik
Copy link
Member Author

This is no longer required since we removed the support for CentOS with Hetzner through #1725

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant