Unrepaired VNET 454 AR 0 has a wrong lease for VNet 455

Community Support
1

Hello,

When doing a onedb fsck I got the following messages:

[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_GLOBAL does not match:  != ::400:c3ff:fedd:ed0b. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_ULA does not match:  != ::400:c3ff:fedd:ed0b. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_GLOBAL does not match:  != ::400:c3ff:fedd:ed0c. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_ULA does not match:  != ::400:c3ff:fedd:ed0c. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_GLOBAL does not match:  != ::400:c3ff:fedd:ed0d. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_ULA does not match:  != ::400:c3ff:fedd:ed0d. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_GLOBAL does not match:  != ::400:c3ff:fedd:ed0e. This can't be fixed
[UNREPAIRED] VNet 454 AR 0 has a wrong lease for VNet 455. IP6_ULA does not match:  != ::400:c3ff:fedd:ed0e. This can't be fixed

The VNET are IPv4, VNET 455 is a reservation of 4 IPs in VNET 454.

I do not see why there is a problem with IPv6 stuffs and did not find any useful information.

Any idea?

Regards.

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.
In this case I would guess that the IP6 prefix was modified after the reservation was created.

This is not a big problem, but it’s something the admin should be aware of nonetheless.

3

Carlos Martín forum@opennebula.org writes:

Hi,

Hello,

By design, if the vnet definition is changed after a lease is assigned the IPs shown in the ‘onevnet show’ command may not match.
In this case I would guess that the IP6 prefix was modified after the
reservation was created.

But there was no IP6 prefix for that network, it was defined as IPv4
only network :-/

This is not a big problem, but it’s something the admin should be aware of nonetheless.

Noted, the admin (myself ;-)) is now aware of it :smiley:

Regards.

Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF