DB fsck errors upgrading from 4.6.1-2 to 4.12.1-1

Community Support
1

Hi,
After upgrading from 4.6.1-2 to 4.12.1-1 I get the error below after the DB fsck.
Is this a problem?

  Regards,
    Gerry

VNet 4 AP 0 has wrong lease for VM3373. IP6_Link does not match fe80:XXXX !=. This can’t be fixed

2

Hi,

By design, if the vnet definition is changed after a lease is assigned the IPs shown in the ‘onevnet show’ command may not match the real one assigned to the VM, as shown in ‘onevm show’.
This is not a big problem, just something to be aware of.

3

Hi Carlos,

Thanks for the reply. I not sure I fully understand what’s happening here. It looks to me than in version 4.6 IPv6 fe80:: leases were assigned to VMs even though there are no IPv6 definitions in the VNet. Is it the case that version 4.12 fixes this and does not assign IPv6 leases if there are no IPv6 definitions in the VNet?

    Regards,
      Gerry