Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect to null failed: null #34

Closed
mordf opened this issue Feb 4, 2019 · 13 comments
Closed

Connect to null failed: null #34

mordf opened this issue Feb 4, 2019 · 13 comments

Comments

@mordf
Copy link

mordf commented Feb 4, 2019

When i'm clicking on TEST CONNECTION button i'm getting: Connect to null failed: null

The credentials are fine since it recognizes my AKS clusters when i'm putting them.

@aysahu
Copy link

aysahu commented Feb 4, 2019

Hi,

I am also facing similar issue with plugin version 0.4.1, Jenkins version 1.150.2, error logs below.

Feb 04, 2019 11:02:54 PM WARNING com.microsoft.jenkins.containeragents.KubernetesCloud$ProvisionCallback call Error in provisioning; slave=com.microsoft.jenkins.containeragents.KubernetesAgent[checkout-qtz3r], template=com.microsoft.jenkins.containeragents.PodTemplate@1455fb53: java.lang.NullPointerException

Feb 04, 2019 11:02:54 PM WARNING com.microsoft.jenkins.containeragents.KubernetesCloud deletePod Failed to terminate pod for slave checkout-qtz3r java.lang.NullPointerException at com.microsoft.jenkins.containeragents.KubernetesService.getKubernetesClient(KubernetesService.java:223) at com.microsoft.jenkins.containeragents.KubernetesCloud.connect(KubernetesCloud.java:101) at com.microsoft.jenkins.containeragents.KubernetesCloud.deletePod(KubernetesCloud.java:285) at com.microsoft.jenkins.containeragents.KubernetesAgent$1.run(KubernetesAgent.java:100) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

@torumakabe
Copy link

Same here. @mordf @aysahu What version of AKS do you use? I use 1.12.4.

@aysahu
Copy link

aysahu commented Feb 5, 2019

@torumakabe I am using 1.11.5 with VNET enabled.

@mordf
Copy link
Author

mordf commented Feb 5, 2019

I’m also using 1.11.5

@mordf mordf closed this as completed Feb 5, 2019
@mordf
Copy link
Author

mordf commented Feb 5, 2019

I’m also using 1.11.5

@kristianhald
Copy link

We used AKS version 1.11.2, then upgraded to 1.11.6 to try an fix the issue.
Also tried creating a Jenkins server using the Microsoft template from Azure Marketplace with an AKS 1.12.4. Same error.

When I press the 'Test Connection' button, I can see that I get an error in the Activity Log for the resource group:
image

@torumakabe
Copy link

@kristianhald I got the same message "Could not find role name clusterAdmin". So I tested all versions of API by calling them directly. Then, 2018-08-01-preview only failed with the same error.

@aysahu
Copy link

aysahu commented Feb 7, 2019

Hey,

Anyone is working on our issue or it is just no body is listening us ?

@torumakabe
Copy link

torumakabe commented Feb 7, 2019

@aysahu It seems the cause is that this plugin dynamically get the latest version API of AKS. The latest preview API published last week and it does not support get accessProfile. Azure team is making a hotfix to mitigate this issue.
jenkinsci/azure-acs-plugin#16 (comment)

@aysahu
Copy link

aysahu commented Feb 7, 2019

@torumakabe Thanks for information.

@mordf
Copy link
Author

mordf commented Feb 7, 2019

@torumakabe Thanks a lot for the update

@kristianhald
Copy link

Our Jenkins is working again with AKS.

Azure has deployed a hotfix for the latest API change.
https://github.com/Azure/AKS/releases/tag/2019-02-07

As I understand the change, they have made an endpoint, deprecated instead of removing it completely. The endpoint will be removed at a later date, so the plugin will probably need an update for this.

@mordf
Copy link
Author

mordf commented Feb 12, 2019

Working for me as well, closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants