From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH pve-network] fix permissions && use new /sdn/zones/<zone>/<vnet> path
Date: Tue, 13 Jun 2023 09:35:49 +0200 [thread overview]
Message-ID: <1686641685.auk1pnonog.astroid@yuna.none> (raw)
In-Reply-To: <05b9adcd98e1452aefa508f9c91b8a4116773561.camel@groupe-cyllene.com>
On June 12, 2023 5:29 pm, DERUMIER, Alexandre wrote:
> Le lundi 12 juin 2023 à 16:36 +0200, Fabian Grünbichler a écrit :
>> one more thing I realized while testing that might be worthy of a
>> follow
>> up - if you configure SDN, but for some reason, your
>> /etc/network/interfaces is missing the "source .." line, the error
>> handling behaviour is very strange:
>> - vnets are displayed in the resource tree next to zones
>> - no proper indication about the root cause
>
> Yes, I have see that recently (also on pve7), when vnet is in error,
> it's displayed in the tree.
> I don't remember to have implemented this, the vnet should be masked
> from the tree, and the zone should have an error icon.
> (and the vnet error message should be displayed in the zone panel)
>
> I'll be busy all the week (pve training week session), I'm not sure
> to be able to send patch this week.
thanks for the patch(es), I'll take a look later today!
prev parent reply other threads:[~2023-06-13 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 1:24 [pve-devel] " Alexandre Derumier
2023-06-12 14:36 ` [pve-devel] applied: " Fabian Grünbichler
2023-06-12 15:29 ` DERUMIER, Alexandre
2023-06-13 7:35 ` Fabian Grünbichler [this message]
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=1686641685.auk1pnonog.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@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