Skip to content

"az aks addon list" always returns "enabled:false" for virtual-node addon even when the addon is actually enabled. #5098

@thiruma0203

Description

@thiruma0203

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name
az aks addon list Extension Name: aks-preview. Version: 0.5.63.

Errors:
az aks addon list command always returns "enable:false" for virtual-node addon. REST API returns "enalble:", but CLI displays result as "enable:false"


> az aks addon list -g TestRG -n TestCluster --debug
# REST API returns the addon status to be "enabled:true" in debug trace.
   "addonProfiles": {
    "aciConnectorLinux": {
     "enabled": true,            <<<<<<<
     "config": {
      "SubnetName": "VirtualNodeSubnet"
     },


#However, CLI displays "enabled:false". It appears to be matching with "aciConnector" instead of "aciConnectorLinux".

  {
    "api_key": "aciConnector",
    "enabled": false,           <<<<<<<<<
    "name": "virtual-node"
  },

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

  • Run az aks addon enable --addon virtual-node -n TestCluster -g TestRG --subnet-name VirtualNodeSubnet in advance to enable virtual-node addon.
  • Run az aks addon list -n TestCluster -g TestRG--debug to check output.

Expected Behavior

"enabled:true" is displayed when the addon is enabled.

Environment Summary

Linux-5.4.0-1085-azure-x86_64-with-glibc2.28 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.10.5
Installer: DEB

azure-cli 2.38.0

Extensions:
aks-preview 0.5.63
ai-examples 0.2.5
ssh 1.1.2

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

Metadata

Metadata

Assignees

Labels

AKSAuto-AssignAuto assign by botCXP AttentionThis issue is handled by CXP team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-author-feedbackMore information is needed from author to address the issue.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions