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

fix(vmip): fix bug with create VirtualMachineIPAddress in different namespace, when VirtualMahineIPAddressLease 'Released' #290

Closed
wants to merge 1 commit into from

Conversation

LopatinDmitr
Copy link
Contributor

Description

  • Add more context for this case.

Why do we need it, and what problem does it solve?

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

…amespace, when VirtualMahineIPAddressLease 'Released'

- add reque after 30s
- fix message in recording event

Signed-off-by: Dmitry Lopatin <[email protected]>
@LopatinDmitr LopatinDmitr force-pushed the refactor/vmip/add-log-message branch from 04149fb to 2773161 Compare August 17, 2024 10:11
@LopatinDmitr LopatinDmitr changed the title refactor(vmip): add log message when VirtualMachineIPAddressLease is bound to another VirtualMachineIPAddress Commits on Aug 17, 2024 fix(vmip): fix bug with create VirtualMachineIPAddress in different namespace, when VirtualMahineIPAddressLease 'Released' Aug 19, 2024
@LopatinDmitr LopatinDmitr changed the title Commits on Aug 17, 2024 fix(vmip): fix bug with create VirtualMachineIPAddress in different namespace, when VirtualMahineIPAddressLease 'Released' fix(vmip): fix bug with create VirtualMachineIPAddress in different namespace, when VirtualMahineIPAddressLease 'Released' Aug 19, 2024
@LopatinDmitr LopatinDmitr deleted the refactor/vmip/add-log-message branch August 19, 2024 07:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant