From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Mark Schouten <mark@tuxis.nl>
Subject: Re: [PVE-User] Proxmox VE 7.0 (beta) released!
Date: Tue, 29 Jun 2021 11:46:58 +0200 [thread overview]
Message-ID: <a602b355-4209-6e75-a25c-f7a98418d29e@proxmox.com> (raw)
In-Reply-To: <0d129a03-9a70-e123-5e5a-e7862ef303ac@tuxis.nl>
Hi,
On 29.06.21 10:05, Mark Schouten wrote:
> Op 24-06-2021 om 15:16 schreef Martin Maurer:
>> We are pleased to announce the first beta release of Proxmox Virtual Environment 7.0! The 7.x family is based on the great Debian 11 "Bullseye" and comes with a 5.11 kernel, QEMU 6.0, LXC 4.0, OpenZFS 2.0.4.
>
> I just upgraded a node in our demo cluster and all seemed fine. Except for non-working cluster network. I was unable to ping the node through the cluster interface, pvecm saw no other nodes and ceph was broken.
>
> However, if I ran tcpdump, ping started working, but not the rest.
>
> Interesting situation, which I 'fixed' by disabling vlan-aware-bridge for that interface. After the reboot, everything works (AFAICS).
>
> If Proxmox wants to debug this, feel free to reach out to me, I can grant you access to this node so you can check it out.
>
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].
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].
Just noting that for completness sake, to avoid more investigation if it's
just that.
- Thomas
[0]: https://pve.proxmox.com/wiki/Roadmap#7.0-beta-known-issues
[1]: https://wiki.debian.org/MachineId#machine_id_and_cloned_systems.2C_generating_a_new_machine_id
next prev parent reply other threads:[~2021-06-29 9:47 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 [this message]
2021-06-29 10:06 ` Mark Schouten
2021-06-29 10:31 ` Thomas Lamprecht
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=a602b355-4209-6e75-a25c-f7a98418d29e@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