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

oVirt marks the network as not synchronized if you specify the gateway address #952

Open
patrick-lomakin opened this issue Jun 20, 2024 · 2 comments
Labels

Comments

@patrick-lomakin
Copy link

Affected version

  • oVirt Engine: 4.5.7-0.master.20240610091440.git1043c13207.el9
  • Host OS Variant: AlmaLinux 9.4
  • VDSM version: vdsm-4.50.5.1-1.el9
  • Additional relevant package versions:

Describe the bug
From my observations, when adding a new network, the VDSM service automatically configures the host network interface with multiple static routes are used instead of the default gateway to the default gateway. The default gateway field remains empty in the host interface settings. It is also empty in the host settings through the control panel. With this configuration, Ovirt does not show that the network is not synchronized, but if no gateway is specified, the new address is unavailable from the Ovirt virtual machine. If you specify the default gateway in the network settings of the desired host, from the Ovirt virtual machine to the address from the new network on the host is pinged and everything works as it should. But after setting the default gateway, the network is marked as not synchronized. Also note that the ovirtmgmt network is also not synchronized after a clean installation.

To reproduce

  1. Login to oVirt Engine Admin Dashboard
  2. Create new network
  3. Attach new network to the host and set static IP with static default gateway
  4. New host network shows as sync-out network

Expected behavior
The network is saved and remains synchronized

Screenshots
Screenshot_new_host_network
Screenshot_ovirt_networks

Additional context

@kandadeepak
Copy link

kandadeepak commented Jul 15, 2024

You can try with workaround 49eaf70

I got the answers from #944

@dupondje
Copy link
Member

Commit oVirt/vdsm@49eaf70
And it's not a workaround, its a proper fix :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants