Skip to content

Arc-enabled Kubernetes custom location creation failing after AZ CLI upgraded to 2.70.0 version #30982

@chintalavr

Description

@chintalavr

Describe the bug

Arc-enabled Kubernetes custom location creation failing after AZ CLI upgraded to 2.70.0 version when running below command to create custom location. This is working fine until version 2.69.0

Related command

az customlocation create

Errors

az : ERROR: The command failed with an unexpected error. Here is the traceback:
At line:1 char:1

  • az customlocation create --name 'jumpstart-cl' `

   + CategoryInfo          : NotSpecified: (ERROR: The comm... the traceback::String) [], RemoteException
   + FullyQualifiedErrorId : NativeCommandError

ERROR: 'CredentialAdaptor' object has no attribute 'signed_session'
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 666, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 734, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 703, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 336, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 120, in handler
File "C:\Users\arcdemo.azure\cliextensions\customlocation\azext_customlocation\custom.py", line 70, in create_customlocation
   return sdk_no_wait(no_wait, cl_client.create_or_update, resource_group_name=resource_group_name,
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/util.py", line 744, in sdk_no_wait
File "C:\Users\arcdemo.azure\cliextensions\customlocation\azext_customlocation\vendored_sdks\azure\mgmt\extendedlocation\v2021_08_15\operations_custom_locations_operations.py", line 378, in create_or_update
   raw_result = self._create_or_update_initial(
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\arcdemo.azure\cliextensions\customlocation\azext_customlocation\vendored_sdks\azure\mgmt\extendedlocation\v2021_08_15\operations_custom_locations_operations.py", line 330, in _create_or_update_initial
   response = self._client.send(request, stream=False, **operation_config)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msrest/service_client.py", line 336, in send
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msrest/pipeline/init.py", line 197, in run
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msrest/pipeline/init.py", line 150, in send
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\msrest/pipeline/requests.py", line 65, in send
AttributeError: 'CredentialAdaptor' object has no attribute 'signed_session'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues

Issue script & Debug output

az customlocation create --name 'jumpstart-cl'                         --resource-group $Env:resourceGroup
                        --namespace arc                         --host-resource-id $connectedClusterId
                        --cluster-extension-ids $extensionId `
                        --kubeconfig $Env:KUBECONFIG

Expected behavior

Custom location resource must be created successfully without any issues

Environment Summary

{
"azure-cli": "2.70.0",
"azure-cli-core": "2.70.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"arcdata": "1.5.21",
"connectedk8s": "1.10.7",
"customlocation": "0.1.3",
"k8s-extension": "1.6.3"
}
}

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Service AttentionThis issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions