Skip to content

periodic-containerdisks-push-nightly failing centos stream 9 test, VMI does not have guest agent connected #73

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

Closed
lyarwood opened this issue Aug 1, 2023 · 4 comments
Labels
kind/bug lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@lyarwood
Copy link
Member

lyarwood commented Aug 1, 2023

/kind bug

What happened:

https://testgrid.k8s.io/kubevirt-containerdisks-periodics#periodic-containerdisks-push-nightly

https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/periodic-containerdisks-push-nightly/1685832720493580288

time="2023-07-31T02:07:41Z" level=info msg="Creating VM" name=centos-stream version=9
W0731 02:07:41.780670   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
time="2023-07-31T02:07:41Z" level=info msg="Waiting for VM to be ready" name=centos-stream version=9
W0731 02:07:41.784713   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:42.788045   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:43.788761   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:44.788526   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:45.788450   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:46.787684   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:47.788580   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:48.788540   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:49.789033   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:50.788317   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:51.788267   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:52.787753   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:53.788362   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
W0731 02:07:53.790649   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
time="2023-07-31T02:07:53Z" level=info msg="Running tests on VMI" name=centos-stream version=9
time="2023-07-31T02:12:44Z" level=error msg="Failed to verify containerdisk" error="an error on the server (\"Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \\\"centos-stream-5tcgh\\\": VMI does not have guest agent connected\") has prevented the request from succeeding" name=centos-stream version=9
W0731 02:12:44.097382   19413 warnings.go:70] kubevirt.io/v1alpha3 is now deprecated and will be removed in a future release.
time="2023-07-31T02:12:44Z" level=error msg="an error on the server (\"Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \\\"centos-stream-5tcgh\\\": VMI does not have guest agent connected\") has prevented the request from succeeding" name=centos-stream version=9
time="2023-07-31T02:12:44Z" level=info msg="Writing results file"
time="2023-07-31T02:12:44Z" level=warning msg="an error on the server (\"Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \\\"centos-stream-5tcgh\\\": VMI does not have guest agent connected\") has prevented the request from succeeding"
time="2023-07-31T02:12:44Z" level=error msg="artifact centos-stream:9 failed in stage verify: an error on the server (\"Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \\\"centos-stream-5tcgh\\\": VMI does not have guest agent connected\") has prevented the request from succeeding" name=centos-stream version=9
time="2023-07-31T02:12:44Z" level=info msg="Writing results file"
time="2023-07-31T02:12:44Z" level=fatal msg="artifact centos-stream:9 failed in stage verify: an error on the server (\"Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \\\"centos-stream-5tcgh\\\": VMI does not have guest agent connected\") has prevented the request from succeeding"
hack/kubevirtci.sh down
make[1]: Entering directory '/home/prow/go/src/github.com/kubevirt/containerdisks/cluster-up'
./cluster-up/down.sh
selecting podman as container runtime
make[1]: Leaving directory '/home/prow/go/src/github.com/kubevirt/containerdisks/cluster-up'
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after podman in container.
================================================================================
Cleaning up after podman
/usr/local/bin/runner.sh: line 50: wait: pid 30 is not a child of this shell
================================================================================
Done cleaning up after podman in container.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • KubeVirt version (use virtctl version):
  • Kubernetes version (use kubectl version):
  • common-templates version:
  • VM or VMI specifications:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

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

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

@kubevirt-bot kubevirt-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 Nov 29, 2023
@kubevirt-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot
Copy link
Contributor

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants