From: Harald Leithner <leithner@itronic.at>
To: pve-devel@pve.proxmox.com
Subject: Re: [pve-devel] Same migration IP on multiple devices
Date: Fri, 22 Jan 2021 08:47:04 +0100 [thread overview]
Message-ID: <1f3fd747-5609-1b78-6fe3-6c5801a898e6@itronic.at> (raw)
In-Reply-To: <d9eb13fd-98ee-ab2f-4460-8dbad883b792@itronic.at>
[-- Attachment #1.1.1: Type: text/plain, Size: 2482 bytes --]
Hi,
issues still exists any eta for a fix?
pve-manager 6.3-3, kernel 5.4.78-2-pve
thx
Harald
Am 30.04.2020 um 11:43 schrieb Harald Leithner:
> Hi,
>
> seams the problem still exists in current version
> (pve-manager/6.1-8/806edfe1 (running kernel: 5.3.18-3-pve))
>
> Did you have time to check this again?
>
> thx
>
> Harald
>
> Am 26.11.2019 um 15:22 schrieb Harald Leithner:
>> Hi,
>>
>> good to know and thx for the fix. I think the same is true for creating
>> a ceph mon from the gui.
>>
>> You get an error message if you create a ceph mon complaining about
>> multiple ips. This can be overridden in the console with --mon-address
>> but maybe should be fixed too.
>>
>> also your fix will not work (untested) because the last proxmox update
>> introduced the same check in 2 other files.
>>
>> Files I patch:
>> /usr/share/perl5/PVE/Cluster.pm
>> /usr/share/perl5/PVE/CLI/pvecm.pm
>> /usr/share/perl5/PVE/QemuServer.pm
>>
>> thx
>>
>> Harald
>>
>> Am 26.11.2019 um 13:55 schrieb Thomas Lamprecht:
>>> Hi,
>>>
>>> On 11/26/19 1:39 PM, Harald Leithner wrote:
>>>> one of my 3 nodes clusters has a full mesh. While trying to migrate a VM
>>>> I get the error message "could not get migration ip: multiple IP address
>>>> configured for <ipaddress>"
>>>>
>>>> This only happens when the migration IP is configured on more then one
>>>> device.
>>>>
>>>> This is the suggested configuration for a full mesh at
>>>> https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server
>>>>
>>>> Removing the check from the source works without problems, is there
>>>> anything I miss?
>>>>
>>>
>>> No, you're right, this is a legitimate case which got caught by the
>>> check by mistake. Instead of removing it, I refined it to ignore
>>> multiple addresses as long as they're identical to each other.
>>>
>>> Much thanks for reporting!
>>>
>>> cheers,
>>> Thomas
>>>
>>
>>
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel@pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
--
ITronic
Harald Leithner
Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Mobil: +43-699-123 78 4 78
Mail: leithner@itronic.at | itronic.at
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
parent reply other threads:[~2021-01-22 7:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <d9eb13fd-98ee-ab2f-4460-8dbad883b792@itronic.at>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f3fd747-5609-1b78-6fe3-6c5801a898e6@itronic.at \
--to=leithner@itronic.at \
--cc=pve-devel@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.