search

kubevirt / kubevirt-ansible

Set of Ansible roles & playbooks for KubeVirt deployment
Apache License 2.0
91 stars 72 forks source link

vendor update to kubevirt v0.17.0 #619

Closed duyanyan closed 5 years ago

duyanyan commented 5 years ago

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #

Special notes for your reviewer:

Release note:

none
duyanyan commented 5 years ago

@cynepco3hahue @lukas-bednar @kbidarkar

duyanyan commented 5 years ago

@nellyc @dollierp

nellyc commented 5 years ago

@duyanyan do you know why the std ci is failing?

duyanyan commented 5 years ago

@nellyc seems it failed in web-ui deployment during setting up the 3.11 env. FAILED - RETRYING: Wait until Web UI is ready: 'v1.4.0-13' (1 retries left). @gbenhaim could you please kindly give some help for this? Thanks

kubevirt-bot commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

/close

kubevirt-bot commented 5 years ago

@kubevirt-bot: Closed this PR.

In response to [this](https://github.com/kubevirt/kubevirt-ansible/pull/619#issuecomment-542659507): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.