Bug 2497926 - Please update pysnmp in epel9 from 7.1.16 to 7.1.21 (epel10 spec rebuilds unchanged)
Summary: Please update pysnmp in epel9 from 7.1.16 to 7.1.21 (epel10 spec rebuilds unc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: pysnmp
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: fedepell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-08 01:00 UTC by Markus Hilger
Modified: 2026-07-10 00:36 UTC (History)
4 users (show)

Fixed In Version: pysnmp-7.1.21-4.el9
Clone Of:
Environment:
Last Closed: 2026-07-10 00:36:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Reproducer with logs and 7.1.21 from epel10 rebuild on el9 (8.31 KB, text/plain)
2026-07-08 01:00 UTC, Markus Hilger
no flags Details

Description Markus Hilger 2026-07-08 01:00:57 UTC
Created attachment 2147993 [details]
Reproducer with logs and 7.1.21 from epel10 rebuild on el9

Description of problem:
pysnmp 7.1.16 in EPEL9 breaks bulk walks with lookupMib=False which is a very
common operation. This is fixed in 7.1.21 which is in epel10 already. See
pysnmp changelog:
https://docs.lextudio.com/pysnmp/v7.1/changelog#revision-7-1-21-released-on-jun-19-2025
The pysnmp 7.1.21 epel10 spec rebuilds for epel9 without any issues.
Therefore, please update pysnmp to 7.1.21 in epel9 using the epel10 spec.

Version-Release number of selected component (if applicable): python3-pysnmp-7.1.16-2.el9

How reproducible: Always

Steps to Reproduce: 
1. On RHEL 9 with EPEL9: dnf install python3-pysnmp net-snmp (any SNMP v2c agent works, e.g. a local snmpd with 'rocommunity public')
2. Run the attached reproducer.py against the agent: python3 reproducer.py 127.0.0.1 public
3. The bulk walk crashes after the first response PDU.

Actual results:
  File ".../pysnmp/hlapi/v3arch/asyncio/cmdgen.py", line 951, in bulk_walk_cmd
    *[ObjectType(varBinds[-1][0], Null(""))],
  File ".../pysnmp/smi/rfc1902.py", line 869, in __init__
    raise SmiError(
pysnmp.smi.error.SmiError: initializer should be ObjectIdentity instance, not
<ObjectName value object, ..., payload [1.3.6.1.2.1.1.9.1.2.3]>

(Full log attached: reproducer-el9.log)

Expected results:
The walk completes: "walk finished OK, 10 varbinds" — as it does with 7.1.21.

Additional info:
Root cause: with lookupMib=False, bulk_walk_cmd builds the continuation
GETBULK from the previous response's raw ObjectName (cmdgen.py:951) instead
of an ObjectIdentity.

Verified: the epel10 SRPM (pysnmp-7.1.21-4, which already carries
license_toml_as_table_pre_pep_639.patch — needed since flit_core 3.9 on el9
rejects the PEP 639 license field) rebuilds unchanged on el9, installs
against stock python3-pyasn1 0.4.8 and python3-cryptography 36.0.1, and the
reproducer passes (rebuild log attached: pysnmp-rebuild-el9-v2.log).
A plain version bump of the epel9 spec does NOT build for that reason.

Comment 1 Fedora Update System 2026-07-08 03:23:53 UTC
FEDORA-EPEL-2026-8176642395 (pysnmp-7.1.21-4.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-8176642395

Comment 2 Fedora Update System 2026-07-09 01:25:37 UTC
FEDORA-EPEL-2026-8176642395 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-8176642395

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2026-07-10 00:36:55 UTC
FEDORA-EPEL-2026-8176642395 (pysnmp-7.1.21-4.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.