azure-mgmt-network, v30.1 - Description too long for azure devops package feeds

[chrido-msft]

• azure-mgmt-network:
• 31.0.0:
• Linux:
• >3:

Describe the bug
Fetching through a azure devops feed fails because of HTTP error 400 Client Error: Bad Request - The package description exceeds the maximum length of 349608 bytes

In the last version, the description almost doubled in size

Logs when fetching a package from devops
Collecting azure-mgmt-network>=30.1 (from......)

ERROR: HTTP error 400 while getting https://pkgs.dev.azure.com///_packaging/99b96f44-e… (from https://pkgs.dev.azure.com///_packaging//pypi/simple/azure-mgmt-network/) (requires-python:>=3.10)

ERROR: Could not install requirement azure-mgmt-network>=30.1 from https://pkgs.dev.azure.com///_packaging/99b96f44-e… (from msftkube[base-envs,packaged-distribution,templates]) because of HTTP error 400 Client Error: Bad Request - The package description exceeds the maximum length of 349608 bytes. (DevOps Activity ID: 5A06F31E-E47C-448C-83F1-CFD9590BA983) for url: https://pkgs.dev.azure.com///_packaging/99b96f44-e… for URL https://pkgs.dev.azure.com///_packaging/99b96f44-e… (from https://pkgs.dev.azure.com///_packaging//pypi/simple/azure-mgmt-network/) (requires-python:>=3.10)

To Reproduce
Steps to reproduce the behavior:

1. Add pypi as upstream to azure devops
2. Fetch Version 30.1 from this feed

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[github-actions]

Thank you for your feedback. Tagging and routing to the team member(s) best able to assist.

//cc: @aznetsuppgithub

[github-actions]

🎯 Agentic Issue Triage

Summary: The azure-mgmt-network v31.0.0 wheel's package description exceeds the 349,608-byte maximum enforced by Azure DevOps artifact feeds, causing HTTP 400 errors when the package is downloaded through an Azure DevOps PyPI upstream feed.

📋 Issue Details

Package: azure-mgmt-network 31.0.0
Affected API: Package metadata / wheel description field
Scenarios:

• Fetching azure-mgmt-network>=30.1 via an Azure DevOps package feed with a PyPI upstream fails with HTTP 400: "The package description exceeds the maximum length of 349608 bytes"
• The package description reportedly approximately doubled in size from the previous version

Root ask: Reduce the package description size in the wheel metadata so it falls within Azure DevOps artifact feed limits, or investigate what changed in v31.0.0 that caused the description to exceed this limit.

🔎 Debugging / Reproduction Notes

The error originates from Azure DevOps enforcing a 349,608-byte limit on wheel metadata descriptions when caching/proxying packages through its PyPI upstream feed. The wheel itself may be valid on PyPI but is rejected when Azure DevOps attempts to ingest it.

Suggested investigation steps:

1. Inspect the METADATA file inside azure_mgmt_network-31.0.0-py3-none-any.whl to measure the description field size.
2. Compare the description/long_description content between v30.x and v31.0.0 to identify what was added (e.g., auto-generated operation lists, expanded docstrings, changelog content).
3. Evaluate whether the long_description in the package configuration can be truncated or replaced with a shorter summary for the wheel metadata.
4. Check Azure DevOps feedback channels for whether the 349,608-byte limit is configurable or has been raised in recent Azure DevOps versions.

🏷️ Label Confidence

• Category: Mgmt — Package name is azure-mgmt-network, a management-plane library
• Service: Network — Explicitly names the Azure Networking service; confirmed by multiple quality reference issues (e.g., azure-mgmt-network >=28.0.0: unittest.mock.Mock(NetworkManagementClient) object attributes not found #39460, NetworkSecurityGrouop - flowLogs is type list[str] not type list[FlowLog] #28740, Subnet update for NSG disassociates Route Table #28350) all using Mgmt + Network for this package
• Confidence: High — Package name unambiguously maps to a single category and service with no alternatives considered

👥 Owner Routing

• Matched CODEOWNERS entry: # ServiceLabel: %Network %Service Attention (line 674) — generic Network entry matches azure-mgmt-network
• AzureSdkOwners: none listed
• ServiceOwners: @aznetsuppgithub
• Routing action: Added "Service Attention" and "needs-team-attention" labels; @mentioned @aznetsuppgithub
• Scan notes: Lines 623–672 contain more-specific Network sub-service entries (Application Gateway, Bastion, CDN, DDOS Protection, DNS, ExpressRoute, Firewall, Front Door, Load Balancer, NVA, Network Watcher, Private Link, Traffic Manager, VNet NAT, VNet, Virtual WAN, VPN Gateway) — all scanned bottom-to-top before reaching the generic %Network match at line 674; none of the sub-service labels matched this issue's general Network label

Generated by Agentic Triage for issue #47788 · 37 AIC · ⌖ 14.4 AIC · ⊞ 9.6K · ◷

[msyyc]

more discussion in teams channel

[msyyc]

https://pypi.org/project/azure-mgmt-network/31.0.1/ was released with shorter changelog and you could have a try @chrido-msft

[github-actions]

Hi @chrido-msft. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.