public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Mark Schouten <mark@tuxis.nl>,
	Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox VE 7.0 (beta) released!
Date: Tue, 29 Jun 2021 12:31:14 +0200	[thread overview]
Message-ID: <a81f3332-0e34-96b8-d195-124916547ebf@proxmox.com> (raw)
In-Reply-To: <ca6e6ebc-525d-5c7a-d481-608bba6737ed@tuxis.nl>

On 29.06.21 12:06, Mark Schouten wrote:
> Hi,
> 
> Op 29-06-2021 om 11:46 schreef Thomas Lamprecht:
>> Do you have some FW rules regarding MAC-Addresses or the like?
>> As the MAC-Address selection changed in Proxmox VE 7 due to new default
>> n systemd's network link policy, as listed in our known issues[0].
> 
> There is no firewall configured on this cluster. On Stoiko's advice, I changed the systemd-link-settings and now everything works again.

Ah yeah, that advice was not posted to the list initially so I did not saw that...

> 
> I do not completely understand why that fixes it though.  Commenting out MACAddressPolicy=persistent helps, but why?
> 

Because duplicate MAC addresses are not ideal, to say the least?

I.e., quoting the second part of my original reply again:

> It's now not the one of the first port anymore, but derived from interface
> name and `/etc/machine-id`, which in combination should be unique but also
> persistent.
> 
> But, for some ISO releases (4.0 to 5.3) the machine-id for the installed host
> was not always re-generated, which could result in duplication of a MAC for
> identical named interfaces on two hosts.
> We try to actively catch and fix that on upgrade by checking if the ID is one
> of the known static ones (it's just a handful of possible IDs) on upgrade.
> 
> But if one cloned an machine (e.g., a colleague run into this in a demo
> virtualized PVE test clusters they cloned from a template) that ID will be
> duplicated and thus make problems.
> That could be easily checked by comparing the `/etc/machine-id` content and
> be fixed by re-generation[1].
> 




  reply	other threads:[~2021-06-29 10:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 13:16 Martin Maurer
2021-06-24 14:08 ` [PVE-User] Error updating Ceph from Nautilus to Octopus Ralf Storm
2021-06-29  8:05 ` [PVE-User] Proxmox VE 7.0 (beta) released! Mark Schouten
2021-06-29  8:23   ` Stoiko Ivanov
2021-06-29  8:34     ` Mark Schouten
2021-06-29  9:46   ` Thomas Lamprecht
2021-06-29 10:06     ` Mark Schouten
2021-06-29 10:31       ` Thomas Lamprecht [this message]
2021-06-29 12:04         ` Mark Schouten
2021-06-29 13:31           ` Stoiko Ivanov
2021-06-29 13:51             ` alexandre derumier
2021-06-29 14:14             ` Thomas Lamprecht
2021-07-02 20:57   ` Thomas Lamprecht
2021-07-02 21:06     ` Mark Schouten
     [not found] ` <mailman.239.1625514988.464.pve-user@lists.proxmox.com>
2021-07-06  9:55   ` Stoiko Ivanov
2021-06-29 12:27 Wolfgang Bumiller
     [not found] <kcEE.HSoMZfIyQreLVdFDq7JFjQ.AFttFk5y1wE@ckcucs11.intern.ckc-it.at>
2021-07-06 10:22 ` Stoiko Ivanov

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=a81f3332-0e34-96b8-d195-124916547ebf@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=mark@tuxis.nl \
    --cc=pve-user@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal