backup import issue

I am importing a backup from another server of mine. The virt version is the same but it is coming from ubuntu 16.04 lts to ubuntu 18.04 lts. The issue i am seeing is it is trying to import onto an existing ipv6 address instead of the next available. ipv4 is a shared address ans is not throwing an error.
Adding IPv6 address 2604:4100:2:7:0:0:0:3 .. .. IPv6 address failed! : Failed to add IPv6 address : SIOCSIFADDR: File exists Here is another error inside of virt: No virtual servers containing 2604:4100:2:7:0:0:0:3 were found.

however that ip is assigned to: 2604:4100:0002:0007:0000:0000:0000:3 (Dedicated IP) aminerdetail.com

why is virt trying to stomp on an existing ipv6 address?

Status: 
Closed (fixed)

Comments

I went and manually removed all of the imported domains and i had to manually clear multiple .3 entries in the networking file. I then added .3 back to AMD and the others got allocated properly. So it borked itself the first time but worked properly the second.

I tried importing one of the domains(it is a single 4.5 gig archive made by virt) and it incremented the ipv6 correctly. Only when i try to import all of them at once..the first one increments..then the rest attempt to stack on top of the same ip..even though i have the restore options set to assign an individual ipv6 address

after i cleared things out now it is stuck on .5 Adding IPv6 address 2604:4100:2:7:0:0:0:5 .. .. IPv6 address failed! : Failed to add IPv6 address : SIOCSIFADDR: File exists

i have attached a couple of screenshots of what it is doing to the netplan and the restore settings i am using(and have used many times in the past). this is a freh install so any anomalies are most likely bugs.

here's some more errors: No virtual servers containing 2604:4100:2:7:0:0:0:5 were found.

except for this: 2604:4100:2:7:0:0:0:5 (Dedicated IP) 21 virtual servers

the domains did not exist on the server before the import.

i have also attached what the netplan looks like after removing hte imported domsins..which i will manually cleanup after this.

Ah, so the real issue is that IP allocation isn't taking into account allocations made during the same restore?

i wound up nuking the box because of other non-virt issues(web1). will report back if it reoccurs.