cloudmarker / cloudmarker

91%

master: 84%

LAST BUILD ON BRANCH clouderror

branch: clouderror

CHANGE BRANCH

x

Reset

• clouderror
• 0.1.0
• alertdocs
• apidocindent
• audit-version
• auditemails
• azcloud
• azstorage
• azurecloud
• azurecloud-exception
• azvm_record_type
• azwebapp
• badges
• baseconfig
• bracket
• buckets
• build-matrix
• changelog
• clioptions
• common-plugins-config
• consistency
• copy-ext
• copyext
• cov_clean
• dependabot/pip/cryptography-3.3.2
• dependabot/pip/httplib2-0.18.0
• dependabot/pip/httplib2-0.19.0
• dependabot/pip/pyyaml-5.4
• dependabot/pip/rsa-4.7
• dependabot/pip/urllib3-1.26.5
• dist
• docfixes
• doctest-fix
• email_debug_param_from_config
• emailbody
• emaildocs
• empty-port
• esstore
• firewalleventtest
• firewallnorm
• firewallruleevent
• fix-esstore-done
• fix-unused-input-queue
• fix_cloud_worker
• fixbuild
• fixcoverage
• fixindent
• freeze
• gcpcloudlogs
• gcpcloudtest
• iam_policy
• ignore-virtual-machines
• ioworkers
• key_file_name_fix
• lint
• load_yaml_safely
• log
• logfixes
• logger-defaults
• logging-levels
• master
• maxrecs
• mock-records
• mockplugins
• mongodbdefaults
• mongodbfix
• mongodbtests
• multiprocessing
• pluginframework
• pluginloader
• readable-version
• readme
• remove-email-config
• removefirewallevent
• rename_logger
• renameparams
• requirements
• rest
• reuse-mock
• rm-venv
• slackalert
• smtpssl
• sphinx
• sphinx-rst-update
• splunkfixes
• splunkhecstore_docs
• splunkhectokentest
• splunkstore
• sub_id_rename
• tests
• travis
• userconfig
• userdoc
• userecordterm
• verdev
• webapp
• worker-com-fields
• worker-error-handling
• workerlogs

Build # 760

Build Type

Pull #132

travis-ci-com

Committed by web-flow

Commit Message

Handle CloudError while iterating on VMs in AzVM

The `CloudError` exception may be raised while iterating on the virtual
machines iterator in this line of code:

    for vm_index, vm in enumerate(virtual_machines_iter):

An example of such an error is:

        msrestazure.azure_exceptions.CloudError: Azure Error:
        DisallowedOperation
        Message: The current subscription type is not permitted to
        perform operations on any provider namespace. Please use a
        different subscription.

This is currently correctly handled in `AzCloud` because `AzCloud`
iterates on each resource iterator inside a `try` block in its
`_get_record()` function. A similar approach is used in this fix to
resolve this issue.

Pull Request Pull Request #132: Handle CloudError while iterating on VMs in AzVM

Run Details

372 of 419 branches covered (88.78%)

Branch coverage included in aggregate %.

20 of 20 new or added lines in 1 file covered. (100.0%)

1874 of 2051 relevant lines covered (91.37%)

2.74 hits per line