public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Tiomet Pelston via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Tiomet Pelston <tiometpelston@gmail.com>
Subject: [pve-devel] [PATCH common 0/1] fix #5623: ovs other_config set to 0 not saved in network config
Date: Wed, 23 Oct 2024 18:48:48 +0200	[thread overview]
Message-ID: <mailman.516.1729702171.332.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 5531 bytes --]

From: Tiomet Pelston <tiometpelston@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH common 0/1] fix #5623: ovs other_config set to 0 not saved in network config
Date: Wed, 23 Oct 2024 18:48:48 +0200
Message-ID: <20241023164849.3027-1-tiometpelston@gmail.com>

When configuring an OVS network device via web interface, 
setting an OVS option with value=0 will be disregarded on save.

Example:
Create an OVS Bond with the following OVS option:

other_config:bond-rebalance-interval=0

This will be purged from the config although it is a valid setting.
The same happens for any other config like "other_config:<anything>=0".

Further details:
https://forum.proxmox.com/threads/ovs-other_config-set-to-0-gets-filtered-from-network-config.150504/

Tiomet Pelston (1):
  fix #5623: ovs other_config set to 0 not saved in network config

 src/PVE/INotify.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.43.0



[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

                 reply	other threads:[~2024-10-23 16:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=mailman.516.1729702171.332.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=tiometpelston@gmail.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