Comments (12)
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
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.
from kubernetes.
/sig apps architecture
/cc @kubernetes/release-team-release-signal
from kubernetes.
/cc @alculquicondor @soltysh @janetkuo
from kubernetes.
The tests failed [FAILED] as Conformance test suite needs a cluster with at least 2 nodes.
/cc @ameukam
- This may be an infra problem according to the failing reason.
Or can we skip if the infra is flaky when we don't have enough nodes to run the test?
/sig k8s-infra
from kubernetes.
@pacoxu There were 3 instances created and deleted:
I0304 04:46:53.400815 3239 deployer.go:155] deleted instance id: i-0b5893d63f85b60bc
I0304 04:46:53.718314 3239 deployer.go:155] deleted instance id: i-098bba2873b0ff3df
I0304 04:46:54.032940 3239 deployer.go:155] deleted instance id: i-097b5ecb2c80639c4
I think this meet Conformance node requirement. What the failing error that suggests it's an infrastructure problem ?
from kubernetes.
@dims is currently working a lot on this.
from kubernetes.
Kubernetes e2e suite: [It] [sig-architecture] Conformance Tests should have at least two untainted nodes [Conformance]
{ failed [FAILED]
Conformance requires at least two nodes In [It] at:
Expected
<int>: 1
to be >
<int>: 1
k8s.io/kubernetes/test/e2e/architecture/conformance.go:45 @ 03/03/24 17:38:46.024 }
I0303 17:39:59.427966 61877 daemon_set.go:140] pods: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"15763"},"items":null}
< Exit [AfterEach] [sig-apps] Daemon set [Serial] - k8s.io/kubernetes/test/e2e/apps/daemon_set.go:122 @ 03/03/24 17:39:59.45 (55ms)
> Enter [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] - k8s.io/kubernetes/test/e2e/framework/node/init/init.go:34 @ 03/03/24 17:39:59.45
I0303 17:39:59.450363 61877 helper.go:121] Waiting up to 7m0s for all (but 0) nodes to be ready
< Exit [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] - k8s.io/kubernetes/test/e2e/framework/node/init/init.go:34 @ 03/03/24 17:39:59.461 (11ms)
> Enter [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] - k8s.io/kubernetes/test/e2e/framework/metrics/init/init.go:35 @ 03/03/24 17:39:59.461
< Exit [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] - k8s.io/kubernetes/test/e2e/framework/metrics/init/init.go:35 @ 03/03/24 17:39:59.461 (0s)
> Enter [DeferCleanup (Each)] [sig-apps] Daemon set [Serial] - dump namespaces | framework.go:218 @ 03/03/24 17:39:59.461
STEP: dump namespace information after failure - k8s.io/kubernetes/test/e2e/framework/framework.go:297 @ 03/03/24 17:39:59.461
STEP: Collecting events from namespace "daemonsets-3276". - k8s.io/kubernetes/test/e2e/framework/debug/dump.go:42 @ 03/03/24 17:39:59.461
STEP: Found 0 events. - k8s.io/kubernetes/test/e2e/framework/debug/dump.go:46 @ 03/03/24 17:39:59.472
What the failing error that suggests it's an infrastructure problem ?
Both test cases are failed for Conformance requires at least two nodes
.
gzip: stdin: invalid compressed data--format violated
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
+ [[ false == true ]]
Cloud-init v. 23.4.4-0ubuntu0~22.04.1 finished at Sun, 03 Mar 2024 16:40:23 +0000. Datasource DataSourceEc2Local. Up 69.42 seconds
https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-ec2-conformance-latest/1764326435192836096/artifacts/logs/i-026cc699a8ec50dbe/cloud-init-output.log Error in cloud-init-output.log
seems to be the root cause.
from kubernetes.
/remove-sig k8s-infra
the infra provided by sig k8s infra is working fine, the problem here is the EC2 e2e cluster bringup which is going to be one of cluster-lifecycle, cloud-provider / AWS, or sig testing.
from kubernetes.
/assign dims
from kubernetes.
It flakes in EC2: both arm and amd.
- https://testgrid.k8s.io/sig-release-master-informing#Conformance%20-%20EC2%20-%20arm64%20-%20master
- https://testgrid.k8s.io/sig-release-master-informing#Conformance%20-%20EC2%20-%20master
from kubernetes.
@pacoxu The arm EC2 has passed since 04-01 https://testgrid.k8s.io/sig-release-master-informing#Conformance%20-%20EC2%20-%20arm64%20-%20master
However, the amd one is flaking regularly. @dims do we have any updates on this, can we help support you in any way to get this closed out?
from kubernetes.
@SubhasmitaSw not for 1.30, don't want to touch it as it may break other things. it's failing in the creation of the cluster itself from what i saw, so it's not a test failure per se. So let's give it a pass - as it is still informing
from kubernetes.
Related Issues (20)
- Kubernets service not distributing traffic in equally , seeing imbalance in traffic . HOT 14
- Comments that end up in OpenAPI descriptions should be CommonMark HOT 18
- Enhancement: allow to filter what fields to return from the API HOT 9
- [Failing Test] ci-crio-cgroupv1-node-e2e-conformance (Swap Tests) HOT 3
- [Flaking Test] integration-master (goroutine leak detection) HOT 6
- [Flaking Test] ci-node-e2e (Container Lifecycle) HOT 11
- Migrate existing features to versioned feature gate HOT 4
- verification machinery for compatibility version HOT 3
- [Flaking Test] TestLog/stateful_set_logs_with_all_pods HOT 4
- Pod deleted during image pull still starts HOT 10
- ValidatingAdmissionPolicy objects have different runtime type compared to CRDValidationRules HOT 8
- `kube-proxy`'s `--healthz-bind-address` should support IPv4 and IPv6 simultaneously (dual stack) HOT 24
- Bug: securityContext appArmorProfile unconfined not working with containerd HOT 5
- The old pod log file is not deleted from the /var/log/pods/ directory HOT 14
- Job controller reports the count of terminating pods with unnecessary delay HOT 4
- tracking issue; bump pause to 3.10 HOT 4
- kubernetes-sigs / scheduler-plugins go.mod Error HOT 3
- post-kubernetes-push-image-pause failed to publish version 3.10 HOT 15
- Failure cluster [6bc9e9c5...] HOT 8
- Apiserver log `Forcing xxx watcher close due to unresponsiveness` meaning consultation HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kubernetes.