Wen Liang d7c14f73f0 fix: Correct attribute checks for routing rule validation ... The validation was incorrectly checking for routing rule attributes at the top-level NM module instead of the NM.IPRoutingRule class. This was causing validation failures because: libnm's API has two core aspects: 1. NMConnection/NMSetting types for handling connection profiles 2. NMClient as a cache of D-Bus objects The suppress_prefixlength and uid_range attributes are not part of the top-level NM module but belong to NM.IPRoutingRule. Updated the validation to properly check for: - set_suppress_prefixlength instead of NM_IP_ROUTING_RULE_ATTR_SUPPRESS_PREFIXLENGTH - set_uid_range instead of NM_IP_ROUTING_RULE_ATTR_UID_RANGE_START This aligns with the correct API usage and fixes the validation errors. Resolves: https://issues.redhat.com/browse/RHEL-85872 Signed-off-by: Wen Liang <liangwen12year@gmail.com>		2025-04-09 18:18:57 -04:00
..
nm	ci: Check spelling with codespell	2025-02-14 11:06:01 +00:00
__init__.py	fix most ansible-test issues, suppress the rest	2021-04-09 19:57:55 +02:00
argument_validator.py	fix: Correct attribute checks for routing rule validation	2025-04-09 18:18:57 -04:00
ethtool.py	disable pylint warning caused by use of python3 pylint	2024-06-04 18:09:20 -06:00
myerror.py	fix most ansible-test issues, suppress the rest	2021-04-09 19:57:55 +02:00
nm_provider.py	refactor: fix python black formatting	2025-01-31 08:02:52 -07:00
utils.py	refractor: Use meaningful variable	2023-12-01 13:39:57 -07:00