jx install eror: getting cluster from Azure: invalid character 'U' looking for beginning of value

[olblak]

Summary

Steps to reproduce the behavior

Install an aks cluster then run jx install --provider=aks

Expected behavior

I expect the cluster to be working

Actual behavior

jx install jxing,

Lets set up a Git user name and API token to be able to perform CI/CD
? Do you wish to use XXX as the local Git user for GitHub server: (Y/n) Y
? Do you wish to use XXX as the local Git user for GitHub server: Yes
Select the CI/CD pipelines Git server and user
? Do you wish to use GitHub as the pipelines Git server: (Y/n) Y
? Do you wish to use GitHub as the pipelines Git server: Yes
? Do you wish to use XXX as the pipelines Git user for GitHub server: (Y/n) Y
? Do you wish to use XXX as the pipelines Git user for GitHub server: Yes
Setting the pipelines Git server https://github.com and user name olblak.
Saving the Git authentication configuration
error: configuring the docker registry: configure cloud provider docker registry: getting cluster from Azure: invalid character 'U' looking for beginning of value

zsh: exit 1 jx install --verbose --timeout='9000' --provider=aks

Jx version

The output of jx version is:

NAME VERSION
jx 1.3.938
Kubernetes cluster v1.12.5
kubectl v1.11.0
helm client v2.9.1+g20adb27
helm server v2.9.1+g20adb27
git git version 2.20.1
Operating System "Fedora release 29 (Twenty Nine)"

Jenkins type

• [x] Classic Jenkins
• [ ] Serverless Jenkins

Kubernetes cluster

aks

Operating system / Environment

Fedora 29

[olblak]

I also tested jx create cluster aks that lead to the same issue

[olblak]

It works if I select provider kubernetes instead of AKS

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[deanesmith]

/area jenkins

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.