Page MenuHomeVyOS Platform

Problem in qos policy random-detect
Open, LowPublicBUG

Description

Can't create qos policy random-detect.

To reproduce:

set qos policy random-detect QOS
set qos interface eth1 egress QOS

Commit:

vyos@vyos# commit
[ qos ]
VyOS had an issue completing a command.

We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):
- Contact us using the online help desk if you have a subscription:
  https://support.vyos.io/
- Make sure you are running the latest version of VyOS available at:
  https://vyos.net/get/
- Consult the community forum to see how to handle this issue:
  https://forum.vyos.io
- Join us on Slack where our users exchange help and advice:
  https://vyos.slack.com

When reporting problems, please include as much information as possible:
- do not obfuscate any data (feel free to contact us privately if your 
  business policy requires it)
- and include all the information presented below

Report time:      2024-04-11 08:34:00
Image version:    VyOS 1.5-rolling-202403250019
Release train:    current

Built by:         [email protected]
Built on:         Mon 25 Mar 2024 02:22 UTC
Build UUID:       84776b7b-9db0-4cf4-ac05-9a6fcf1e9128
Build commit ID:  e765407943321f

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  QEMU
Hardware model:   Standard PC (i440FX + PIIX, 1996)
Hardware S/N:     
Hardware UUID:    882d898a-d47e-4361-b4da-03fe4b8f7adb

Traceback (most recent call last):
  File "/usr/libexec/vyos/conf_mode/qos.py", line 235, in <module>
    c = get_config()
        ^^^^^^^^^^^^
  File "/usr/libexec/vyos/conf_mode/qos.py", line 115, in get_config
    max_thr = int(qos['policy'][policy][p_name]['precedence'][precedence]['maximum_threshold'])
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'maximum_threshold'



[[qos]] failed
Commit failed

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

HollyGurza changed Issue type from Unspecified (please specify) to Bug (incorrect behavior).
HollyGurza changed the subtype of this task from "Task" to "Bug".Thu, Apr 11, 9:38 AM