From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-network 1/2] zones: fix status
Date: Tue, 13 Jun 2023 13:13:28 +0200 [thread overview]
Message-ID: <1686654801.ltb7sx10jx.astroid@yuna.none> (raw)
In-Reply-To: <20230612174347.1598994-2-aderumier@odiso.com>
On June 12, 2023 7:43 pm, Alexandre Derumier wrote:
> Vnets were wrongly displayed in the main tree because of this,
> and error was not set on zone
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> src/PVE/Network/SDN/Zones.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/PVE/Network/SDN/Zones.pm b/src/PVE/Network/SDN/Zones.pm
> index f8e40b1..7d70e49 100644
> --- a/src/PVE/Network/SDN/Zones.pm
> +++ b/src/PVE/Network/SDN/Zones.pm
> @@ -268,7 +268,7 @@ sub status {
> if (@{$err_msg} > 0) {
> $vnet_status->{$id}->{status} = 'error';
> $vnet_status->{$id}->{statusmsg} = join(',', @{$err_msg});
> - $zone_status->{$id}->{status} = 'error';
> + $zone_status->{$zone}->{status} = 'error';
> }
> }
>
> --
> 2.30.2
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
next prev parent reply other threads:[~2023-06-13 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 17:43 [pve-devel] [PATCH pve-network 0/2] fix zones status Alexandre Derumier
2023-06-12 17:43 ` [pve-devel] [PATCH pve-network 1/2] zones: fix status Alexandre Derumier
2023-06-13 11:13 ` Fabian Grünbichler [this message]
2023-06-12 17:43 ` [pve-devel] [PATCH pve-network 2/2] zones: status: add a special message if vnet is not generated Alexandre Derumier
2023-06-13 11:21 ` Fabian Grünbichler
2023-06-13 11:40 ` Fabian Grünbichler
2023-06-14 19:41 ` DERUMIER, Alexandre
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=1686654801.ltb7sx10jx.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