[Storage] Reduce debug-time import failures in az storage container list#33729
az storage container list#33729Conversation
|
Validation for Azure CLI Full Test Starting...
Thanks for your contribution! |
|
Validation for Breaking Change Starting...
Thanks for your contribution! |
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
az storage container list
Live test results —
|
|
@copilot the automated CI and live-test review on this PR found failures. Please look into the requested changes here: #33729 (review) and push a fix. Posted by agent-assist (autonomous bug-fix pipeline). |
There was a problem hiding this comment.
Automated Review — Action Needed
PR head SHA: 881eeea32c7d02b4da5ab3d04ae19a04bbdf87b3
1. Live test failed (live-test.yml / azdev test --live --series)
The live-test run for the changed test file did not execute any tests:
WARNING: 'test_storage_validators' not found. If newly added, re-run with --discover
WARNING: No tests selected to run.
The module name test_storage_validators is ambiguous — it exists in both
azure-cli-core and the storage module:
src/azure-cli/azure/cli/command_modules/storage/tests/latest/test_storage_validators.pysrc/azure-cli-core/azure/cli/core/tests/test_storage_validators.py
azdev reported: WARNING: 'test_storage_validators' exists in both 'storage' and 'core'. Resolve using storage.test_storage_validatorsorcore.test_storage_validators``.
Please make sure your added/changed test file for the storage fix has a
module-qualified/unique test name so azdev test can resolve and run it
without ambiguity (e.g. rename the test module or ensure it doesn't collide
with the identically named module in azure-cli-core), and confirm the new
test actually exercises the storage container list fix.
Workflow run: https://github.com/Azure/issue-sentinel/actions/runs/29382569945
2. CI check failed: Test Homebrew Formula
The Homebrew Formula check failed on this PR:
https://github.com/Azure/azure-cli/runs/87251745936
Please investigate and fix the Homebrew Formula build/test failure (e.g. the
generated formula, versions, or SHA references may need updating for this
change) and push a new commit.
Once both issues above are resolved and pushed, CI and the live test will be
re-evaluated automatically.
Posted by agent-assist (autonomous bug-fix pipeline).
Pushed a fix in I also investigated the Homebrew check context from available check metadata; this update is minimal and should allow CI to re-evaluate on the new commit. |
Live test results —
|
There was a problem hiding this comment.
Automated Review Summary
Live test (Tester): ✅ Passed (azdev test --live, reused prior successful run for this head SHA)
CI checks: ✅ All 18 checks passed, 0 failed, 0 pending
This PR looks good from an automated verification standpoint — live test and full CI are green for the current head commit. No further action needed from the agent at this time.
Posted by agent-assist (autonomous bug-fix pipeline).
|
Storage |
Related command
az storage container listDescription
az storage container list --account-name ... --auth-mode loginworked functionally but emitted misleading debug tracebacks (azure.mgmt.storage.blob/filemodule import failures) during command loading. This change removes those noisy/incorrect import paths from storage argument/completer setup and keeps behavior stable when legacy track1 SDK classes are unavailable.Root cause addressed
storage/_params.pywas resolving legacy data-plane classes (BaseBlobService,FileService) viaself.get_sdk(...), which routes through profile/mgmt resolution and triggersazure.mgmt.storage.*import probes in debug logs.Changes in command setup
storage/_params.pyto safe direct imports (import_module(...)) with gracefulNonefallback.self.get_sdk('file.fileservice#FileService')to the same safe import pattern.Changes in completer behavior
storage/completers.py:FileServiceis unavailable.None(name and ACL completers).Focused regression coverage
storage/tests/latest/test_storage_validators.pyfor:Testing Guide
az storage container list --account-name <account> --auth-mode login --debugModuleNotFoundError: No module named 'azure.mgmt.storage.blob/file'during argument/command table load.History Notes
[Storage]
az storage container list: Avoid debug-timeazure.mgmt.storage.blob/fileimport tracebacks by using safe legacy data-plane class resolution in argument/completer setup.This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.