Skip to content

Conversation

@deads2k
Copy link
Contributor

@deads2k deads2k commented Nov 3, 2022

Running this patch shows me

STEP: Creating a kubernetes client 11/03/22 17:23:32.674
STEP: Building a namespace api object, basename projected 11/03/22 17:23:32.675
Nov  3 17:23:32.788: INFO: About to run a Kube e2e test, ensuring namespace is privileged
STEP: Waiting for a default service account to be provisioned in namespace 11/03/22 17:23:33.123
STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 11/03/22 17:23:33.187
[It] updates should be reflected in volume [NodeConformance] [Conformance] [Skipped:NoOptionalCapabilities] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]
  k8s.io/kubernetes@v1.25.0/test/e2e/common/storage/projected_configmap.go:123
Nov  3 17:23:33.321: INFO: Couldn't get node TTL annotation (using default value of 0): No TTL annotation found on the node
STEP: Creating projection with configMap that has name projected-configmap-test-upd-922477a5-724e-4128-ab2e-40e5d59e46b5 11/03/22 17:23:33.321
STEP: Creating the pod 11/03/22 17:23:33.357
Nov  3 17:23:33.402: INFO: Waiting up to 5m0s for pod "pod-projected-configmaps-8d3c922a-af51-4179-a604-85662dc8869d" in namespace "e2e-projected-1403" to be "running and ready"
Nov  3 17:23:33.441: INFO: Pod "pod-projected-configmaps-8d3c922a-af51-4179-a604-85662dc8869d": Phase="Pending", Reason="", readiness=false. Elapsed: 38.979578ms
Nov  3 17:23:33.441: INFO: The phase of Pod pod-projected-configmaps-8d3c922a-af51-4179-a604-85662dc8869d is Pending, waiting for it to be Running (with Ready = true)
Nov  3 17:23:35.480: INFO: Pod "pod-projected-configmaps-8d3c922a-af51-4179-a604-85662dc8869d": Phase="Running", Reason="", readiness=true. Elapsed: 2.078231078s
Nov  3 17:23:35.480: INFO: The phase of Pod pod-projected-configmaps-8d3c922a-af51-4179-a604-85662dc8869d is Running (Ready = true)
Nov  3 17:23:35.480: INFO: Pod "pod-projected-configmaps-8d3c922a-af51-4179-a604-85662dc8869d" satisfied condition "running and ready"
Nov  3 17:23:35.547: INFO: STARTING!
Nov  3 17:23:35.547: INFO: WATCH type=ADDED, name=kube-root-ca.crt
Nov  3 17:23:35.547: INFO: WATCH type=ADDED, name=projected-configmap-test-upd-922477a5-724e-4128-ab2e-40e5d59e46b5
Nov  3 17:23:35.547: INFO: WATCH type=ADDED, name=openshift-service-ca.crt
STEP: Updating configmap projected-configmap-test-upd-922477a5-724e-4128-ab2e-40e5d59e46b5 11/03/22 17:23:35.587
Nov  3 17:23:35.622: INFO: WATCH type=MODIFIED, name=projected-configmap-test-upd-922477a5-724e-4128-ab2e-40e5d59e46b5
STEP: waiting to observe update in volume 11/03/22 17:23:35.622
Nov  3 17:24:59.262: INFO: SUCCESS!
[AfterEach] [sig-storage] Projected configMap
  k8s.io/kubernetes@v1.25.0/test/e2e/framework/framework.go:187
Nov  3 17:24:59.262: INFO: WATCH type=ERROR, name=unknown
Nov  3 17:24:59.262: INFO: EXIT!
STEP: Destroying namespace "e2e-projected-1403" for this suite. 11/03/22 17:24:59.262

The direct watch sees the configmap update immediatesly, but the pod doesn't see the update on the filesystem for over a minute.

@openshift-ci openshift-ci bot requested review from bparees and soltysh November 3, 2022 21:28
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Nov 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 3, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 4, 2022

@deads2k: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node-serial 0ac6604 link false /test e2e-aws-ovn-single-node-serial
ci/prow/verify-deps 0ac6604 link true /test verify-deps
ci/prow/e2e-aws-ovn-single-node-upgrade 0ac6604 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-serial 0ac6604 link true /test e2e-aws-ovn-serial
ci/prow/e2e-openstack-ovn 0ac6604 link false /test e2e-openstack-ovn
ci/prow/e2e-gcp-ovn-image-ecosystem 0ac6604 link true /test e2e-gcp-ovn-image-ecosystem

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 3, 2023
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 6, 2023
@deads2k deads2k closed this Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants