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

[Flakey CI] Cluster Network Addons Operator when operator in version 0.18.0 is installed and supported spec configured should transition reported versions while being upgraded to version 99.0.0 #462

Closed
omeryahud opened this issue Jul 12, 2020 · 8 comments
Labels
triage/build-watcher Discovered by a kubevirt build-watcher. Pay attention to these issues to keep CI healthy.

Comments

@omeryahud
Copy link

omeryahud commented Jul 12, 2020

/triage build-officer
/kind bug

What happened:
Flakefinder reported the flaky test

Cluster Network Addons Operator when operator in version 0.18.0 is installed and supported spec configured should transition reported versions while being upgraded to version 99.0.0

In these Prow jobs:

The timeout appears to be pretty long (20 minutes)

What you expected to happen:
The test should pass

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

Anything else we need to know?:

Environment:

@kubevirt-bot kubevirt-bot added the triage/build-watcher Discovered by a kubevirt build-watcher. Pay attention to these issues to keep CI healthy. label Jul 12, 2020
@kubevirt-bot
Copy link
Collaborator

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 10, 2020
@kubevirt-bot
Copy link
Collaborator

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 9, 2020
@kubevirt-bot
Copy link
Collaborator

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
Collaborator

@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.

@kubevirt-bot kubevirt-bot reopened this Feb 5, 2021
@kubevirt-bot
Copy link
Collaborator

@dhiller: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Happened here: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/773/pull-e2e-cluster-network-addons-operator-lifecycle-k8s/1357214102761508864

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.

@kubevirt-bot kubevirt-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 5, 2021
@kubevirt-bot
Copy link
Collaborator

Issues triaged by the build watcher close after 14d of inactivity.
Reopen the issue with /reopen.

/close

@kubevirt-bot
Copy link
Collaborator

@kubevirt-bot: Closing this issue.

In response to this:

Issues triaged by the build watcher close after 14d of inactivity.
Reopen the issue with /reopen.

/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
triage/build-watcher Discovered by a kubevirt build-watcher. Pay attention to these issues to keep CI healthy.
Projects
None yet
Development

No branches or pull requests

3 participants