Page MenuHomeVyOS Platform
Create Task
Maniphest T4467

Validator Does Not Accept Signed Numbers
Closed, ResolvedPublicBUG
Actions

Description

The numeric validator does not accept signed numbers, and as a result causes errors with relative metrics in route-maps:

trae@cr01a-vyos# set policy route-map BGP-BACKBONE-OUT rule 10 set metric "+100"
      
  '+100' is not a valid number                                
      
                                                          
                                                                            
  Invalid value
  Value validation failed                                 
  Set failed                                                                                                                                                                                                                                     
[edit]

Details

Version
1.4-rolling-202205290217
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Related Objects

Event Timeline

trae32566 created this task.Jun 16 2022, 6:44 AM
c-po subscribed.Jun 16 2022, 7:06 AM

route-maps support a relative adjustment of the metric (https://github.com/vyos/vyos-1x/blob/current/interface-definitions/policy.xml.in#L1402-L1417)

The validator should support verifying also signed numbers

Signed positive not working

cpo@LR1.wue3:~$ /usr/libexec/vyos/validators/numeric --range -10-10 +4
'+4' is not a valid number
cpo@LR1.wue3:~$ /usr/libexec/vyos/validators/numeric --range -10-10 -5
/usr/libexec/vyos/validators/numeric: unknown option '-5'.
Usage: /usr/libexec/vyos/validators/numeric [OPTIONS] <number>
  --non-negative Check if the number is non-negative (>= 0)
  --positive Check if the number is positive (> 0)
  --range Check if the number is within a range (inclusive)
  --float Allow floating-point numbers
  -help  Display this list of options
  --help  Display this list of options

Signed negative not working

cpo@LR1.wue3:~$ /usr/libexec/vyos/validators/numeric --range -10-10 -- -5
/usr/libexec/vyos/validators/numeric: unknown option '--'.
Usage: /usr/libexec/vyos/validators/numeric [OPTIONS] <number>
  --non-negative Check if the number is non-negative (>= 0)
  --positive Check if the number is positive (> 0)
  --range Check if the number is within a range (inclusive)
  --float Allow floating-point numbers
  -help  Display this list of options
  --help  Display this list of options
cpo@LR1.wue3:~$ /usr/libexec/vyos/validators/numeric --range -10-10 -5
/usr/libexec/vyos/validators/numeric: unknown option '-5'.
Usage: /usr/libexec/vyos/validators/numeric [OPTIONS] <number>
  --non-negative Check if the number is non-negative (>= 0)
  --positive Check if the number is positive (> 0)
  --range Check if the number is within a range (inclusive)
  --float Allow floating-point numbers
  -help  Display this list of options
  --help  Display this list of options
c-po triaged this task as Normal priority.Jun 16 2022, 7:06 AM
c-po edited a custom field.
c-po edited a custom field.
pasik subscribed.Jun 16 2022, 3:49 PM
c-po mentioned this in rVYOSONEXa92e6b272b17: smoketest: policy: T4467: validate relative route-map metric.Jun 16 2022, 7:32 PM
jestabro subscribed.EditedJun 17 2022, 5:31 PM

One approach is linked below; to be discussed before PR.
https://github.com/vyos/vyos-utils/compare/master...jestabro:increment-decrement?expand=1

jestabro added a comment.Jun 18 2022, 12:55 AM

PR: https://github.com/vyos/vyos-utils/pull/4
Adding the additional validator to policy.xml.in allows the smoketest (above) to pass.

jestabro claimed this task.Jun 18 2022, 12:59 AM
c-po added a comment.Jun 18 2022, 6:04 AM

Tested and works correct. Thanks @jestabro

c-po closed this task as Resolved.Jun 18 2022, 6:04 AM
c-po mentioned this in rVYOSONEX300535e2b8b7: policy: T4467: bugfix relative (+/-) increase of metric.Jun 18 2022, 6:04 AM