lighthouse: Errors on `subctl verify` when running with Globalnet
What happened:
Running subctl verify on 0.12.0-rc1 test day, the clusters are installed with Globalnet.
Got the following errors:
• Failure [295.955 seconds]
[discovery] Test Service Discovery Across Clusters
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/service_discovery.go:42
when a pod tries to resolve a service in a specific remote cluster by its cluster name
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/service_discovery.go:74
should resolve the service on the specified cluster [It]
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/service_discovery.go:75
Failed to verify if service IP is discoverable. expected execution result "" to contain "172.30.17.231"
Unexpected error:
<*errors.errorString | 0xc00018bea0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
occurred
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
------------------------------
• Failure [285.577 seconds]
[discovery] Test Headless Service Discovery Across Clusters
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/headless_services.go:37
when a pod tries to resolve a headless service in a remote cluster
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/headless_services.go:40
should resolve the backing pod IPs from the remote cluster [It]
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/headless_services.go:41
Failed to service IP verification. expected execution result "" to contain "242.1.255.252"
Unexpected error:
<*errors.errorString | 0xc00018bea0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
occurred
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
------------------------------
• Failure [279.380 seconds]
[discovery] Test Stateful Sets Discovery Across Clusters
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:34
when a pod tries to resolve a podname from stateful set in a remote cluster
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:37
should resolve the pod IP from the remote cluster [It]
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:38
Failed to service IP verification. expected execution result "" to contain "242.1.255.252"
Unexpected error:
<*errors.errorString | 0xc00018bea0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
occurred
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
------------------------------
• Failure [280.104 seconds]
[discovery] Test Stateful Sets Discovery Across Clusters
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:34
when a pod tries to resolve a podname from stateful set in a local cluster
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:43
should resolve the pod IP from the local cluster [It]
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:44
Failed to service IP verification. expected execution result "" to contain "242.0.255.252"
Unexpected error:
<*errors.errorString | 0xc00018bea0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
occurred
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
------------------------------
• Failure [280.258 seconds]
[discovery] Test Stateful Sets Discovery Across Clusters
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:34
when the number of active pods backing a stateful set changes
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:49
should only resolve the IPs from the active pods [It]
github.com/submariner-io/lighthouse@v0.12.0-rc1/test/e2e/discovery/statefulsets.go:50
Failed to service IP verification. expected execution result "" to contain "242.1.255.250"
Unexpected error:
<*errors.errorString | 0xc00018bea0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
occurred
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
------------------------------
Summarizing 6 Failures:
[Fail] [discovery] Test Service Discovery Across Clusters when a pod tries to resolve a service in a specific remote cluster by its cluster name [It] should resolve the service on the specified cluster
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
[Fail] [discovery] Test Headless Service Discovery Across Clusters when a pod tries to resolve a headless service in a remote cluster [It] should resolve the backing pod IPs from the remote cluster
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
[Fail] [discovery] Test Headless Service Discovery Across Clusters when a pod tries to resolve a headless service in a specific remote cluster by its cluster name [It] should resolve the backing pod IPs from the specified remote cluster
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
[Fail] [discovery] Test Stateful Sets Discovery Across Clusters when a pod tries to resolve a podname from stateful set in a remote cluster [It] should resolve the pod IP from the remote cluster
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
[Fail] [discovery] Test Stateful Sets Discovery Across Clusters when a pod tries to resolve a podname from stateful set in a local cluster [It] should resolve the pod IP from the local cluster
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
[Fail] [discovery] Test Stateful Sets Discovery Across Clusters when the number of active pods backing a stateful set changes [It] should only resolve the IPs from the active pods
github.com/submariner-io/shipyard@v0.12.0-rc1/test/e2e/framework/framework.go:513
Ran 24 of 41 Specs in 2129.496 seconds
FAIL! -- 18 Passed | 6 Failed | 0 Pending | 17 Skipped
[] E2E failed
Full log: log.txt
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
-
Diagnose information (use
subctl diagnose all): All passed -
Gather information (use
subctl gather): gather.tar.gz -
Cloud provider or hardware configuration: AWS, OCP 4.9
-
Install tools:
-
Others:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (17 by maintainers)
Commits related to this issue
- Fix valid ClusterId check Current check for validating ClusterId allows `.` in clustername. Instead it should follow Label Names validations as defined in https://kubernetes.io/docs/concepts/overview... — committed to vthapar/submariner-operator by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to vthapar/lighthouse by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to submariner-io/lighthouse by vthapar 5 years ago
- Fix valid ClusterId check Current check for validating ClusterId allows `.` in clustername. Instead it should follow Label Names validations as defined in https://kubernetes.io/docs/concepts/overview... — committed to submariner-io/submariner-operator by vthapar 5 years ago
- Fix valid ClusterId check Current check for validating ClusterId allows `.` in clustername. Instead it should follow Label Names validations as defined in https://kubernetes.io/docs/concepts/overview... — committed to sridhargaddam/submariner-operator by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to vthapar/lighthouse by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to vthapar/lighthouse by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to Jaanki/lighthouse by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to Jaanki/lighthouse by vthapar 5 years ago
- Add validations for ClusterID Check if ClusterID is valid DNS1123 Label and exit with error if not. Invalid ClusterID causes errors when replying to DNS queries for service discovery. Fixes #707 Sig... — committed to submariner-io/lighthouse by vthapar 5 years ago
- Fix valid ClusterId check Current check for validating ClusterId allows `.` in clustername. Instead it should follow Label Names validations as defined in https://kubernetes.io/docs/concepts/overview... — committed to anfredette/submariner-operator by vthapar 5 years ago
- Fix valid ClusterId check Current check for validating ClusterId allows `.` in clustername. Instead it should follow Label Names validations as defined in https://kubernetes.io/docs/concepts/overview... — committed to submariner-io/submariner-operator by vthapar 5 years ago
I believe in
subctl joinwould make the most sense, and obviously in the agent as you specified that it’ll throw an error. If we need it in other agents I guess it could make sense somewhat, but realistically they dont use the name for DNS so it doesnt matter, so I’d focus on the places where it matters.