VMs with ebtables VNM after upgrade 6.10->7.2

Product Support Installation & Configuration
1

Hi all,

I have a long-running OpenNebula setup, which I have upgraded from 6.10 to 7.2 few days ago. Between these versions, the ebtables VNM which I used on my VNets has been deprecated and disappeared. So I changed all my VNets from ebtables to bridge. This allowed me and my users to instantiate new VMs. But they are unable to deploy previously undeployed VMs using these VNets, because the information that they use the ebtables VNM is probably stored somewhere inside the VM config. So even though the VNet itself uses the bridge VNM, trying to deploy an existing VM fails while trying to execute non-existing remotes/vnm/ebtables/pre script.

How can I convert the existing VMs from ebtables to bridge?

As a band-aid, I created a symlink ebtables -> bridge in remotes/vnm, increased the VERSION number and ran onehost sync.

Thanks!

-Yenya

2

Hello,

May you check with onevm show --all VM_ID if there is any ebtables related info on the VMs?
In that case, can you check if a onevm updateconf VM_ID allows you to modify the related params?

In the meantime, the symlink should be a valid workaround

Cheers!

3

Yes, there is the following in the NIC section:

NIC=[
AR_ID="0",
BRIDGE="br503",
BRIDGE_TYPE="linux",
CLUSTER_ID="101,104,105",
FILTER_IP_SPOOFING="YES",
... local addressing omitted ...
MODEL="virtio",
NAME="NIC0",
NETWORK_ID="7",
NETWORK_UNAME="oneadmin",
NIC_ID="0",
SECURITY_GROUPS="0",
TARGET="one-17000-0",
VN_MAD="ebtables" ]

So, what is the recommended way of batch-updating ~2000 of my VMs? Is there a cleaner way than

onevm list --json | jq -r '.VM_POOL.VM[].ID' | while read id
do
    onevm show --all --json $id | jq .VM.TEMPLATE > template
    grep -q ebtables template || continue
    echo "Editing VM $id"
    sed 's/ebtables/bridge/g' < template | onevm update --json $id
done

Thanks!

-Yenya

4

@brunorro - onevm updateconf does not update the NIC configuration. onevm nic-update $vm_id $nic_index is supposed to do it. However, I ran it for my machine which has VN_MAD=ebtables, edited s/ebtables/bridge/, but when I saved the text and exit the text editor, nothing happened, and subsequent onevm show --all and onevm nic-update still have VN_MAD=ebtables.

According to onevm man-page, running nic-update should re-plug the NIC inside the VM, but in dmesg from inside of the VM, no hotplug event is received.

EDIT: I discovered CONTEXT_ALLOW_ETH_UPDATES option in oned.conf, but even when set to YES (and restarting oned) it behaves the same.

Any other ideas how to get rid of no-longer present VN_MAD? Thanks!