[JIRA] (JENKINS-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu commented on JENKINS-51016 Re: Azure VM can't start (infinte loop) Jie Shen maintains the plugin now. Could you help to take a look. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu assigned an issue to Jie Shen Jenkins / JENKINS-51016 Azure VM can't start (infinte loop) Change By: Chenyang Liu Assignee: Chenyang Liu Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Chenyang Liu commented on JENKINS-49576 Re: Failure creating provisioned agent after successful provisioning Please try the new version we released yesterday 0.7.1. I think the problem should be fixed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu commented on JENKINS-51016 Re: Azure VM can't start (infinte loop) I think it should be some bugs in retention strategy to lead to the issue. When the agent went online, canRecycle become true. So, set idle time to zero should make the vm start correctly. But there's no perfect work around except waiting to change the code. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu updated an issue Jenkins / JENKINS-51016 Azure VM can't start (infinte loop) Change By: Chenyang Liu Attachment: image-2018-04-26-21-23-05-219.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51016) Azure VM can't start (infinte loop)
Title: Message Title Chenyang Liu commented on JENKINS-51016 Re: Azure VM can't start (infinte loop) What your vm limit means? Because from the logs, it shows the vm shutdown by retention strategy. Seems extend the idle time in configuration is a work around. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title Chenyang Liu commented on JENKINS-50850 Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0 You said "This happened for all VMs being provisioned". Is it means the plugin can't provision any VMs since restart? After restarting, are there already a lot of VMs in Azure? Actually we only change the way to create storage account in the 0.7.0. We didn't change the ARM template. So I can't give you a clear reason why it happened now. But you can try to catch full ARM template in the deployment in portal. If there's something different, it may give me some hint. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title Chenyang Liu commented on JENKINS-50850 Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0 Seems it's also a problem in Azure side. AllocationFailed I don't know how large the size you chose. But you can do some tests to verify whether it's a plugin's problem or not. You can create the same size vm through Azure Portal directly, and try to use plugin to provision VMs on the another region. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title Chenyang Liu assigned an issue to Chenyang Liu Jenkins / JENKINS-50850 createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0 Change By: Chenyang Liu Assignee: Azure DevOps Chenyang Liu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50850) createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
Title: Message Title
Chenyang Liu commented on JENKINS-50850
Re: createProvisionedAgent: Deployment Failed after upgrade to Version 0.7.0
From the logs, it seems you exceed the core limit in your subscription. Please add the quota limits Deployment Failed: Microsoft.Compute/virtualMachines:jenkins-linux-8-core-build-slaveb939d10 - Conflict - {error={code=OperationNotAllowed, message=Operation results in exceeding quota limits of Core. Maximum allowed: 350, Current in use: 344, Additional requested: 8. Please read more about quota increase at http://aka.ms/corequotaincrease.}}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50478) Add support for data disks
Title: Message Title Chenyang Liu assigned an issue to Chenyang Liu Jenkins / JENKINS-50478 Add support for data disks Change By: Chenyang Liu Assignee: Dave Tucker Chenyang Liu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50478) Add support for data disks
Title: Message Title Chenyang Liu commented on JENKINS-50478 Re: Add support for data disks It looks good to me. Please feel free to open a PR. For the risky part, let's keep in contact and do more test to make sure it works well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50410) Periods of high load cause "Invalid virtual machine image" exceptions
Title: Message Title Chenyang Liu commented on JENKINS-50410 Re: Periods of high load cause "Invalid virtual machine image" exceptions From Azure Docs "For each subscription and tenant, Resource Manager limits read requests to 15,000 per hour and write requests to 1,200 per hour. " You said high usage, so how many VMs do you provision in one hour. And if the frequency is really high so that hit the limit, we seems nothing can do to solve it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49473) Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure
Title: Message Title Chenyang Liu commented on JENKINS-49473 Re: Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure Do you means you can't even delete the vm manually or can't be deleted by plugin automatically? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Chenyang Liu commented on JENKINS-49576 Re: Failure creating provisioned agent after successful provisioning Are you using "Shutdown Only" strategy? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48345) Cloud statistics is still counting the hours even after terminated the Azure VM agents
Title: Message Title Chenyang Liu commented on JENKINS-48345 Re: Cloud statistics is still counting the hours even after terminated the Azure VM agents Did you ever use "Shutdown Only" strategy? We found a bug when using "Shutdown Only" VMs, so that it will lead to a lot of never end cloud statistics events. We will fix it in the next version release. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49021) Stopped but not suspended Azure VM Agent is not restarted
Title: Message Title Chenyang Liu commented on JENKINS-49021 Re: Stopped but not suspended Azure VM Agent is not restarted From my tests today, suspended or not is not the key point, we don't check whether it's suspended when try to reuse the VM. We shutdown the VM and set EligibleForReuse=true. Also we restart the VM and set EligibleForReuse=false. I think there is some multi-thread problems between these two processes. EligibleForReuse fall into a mess so that cause some of these problems. I will add some synchronized logic and keep testing. The logs show there's really a mess after restarting the Jenkins Master, I will keep investigating. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49021) Stopped but not suspended Azure VM Agent is not restarted
Title: Message Title Chenyang Liu commented on JENKINS-49021 Re: Stopped but not suspended Azure VM Agent is not restarted Carsten Wickner We try to fix this issue, but I tried many time, it always works well. So, please provide me more details. Does the issue happen more frequently when there are more nodes? Will the issue happen when using SSH? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48345) Cloud statistics is still counting the hours even after terminated the Azure VM agents
Title: Message Title Chenyang Liu commented on JENKINS-48345 Re: Cloud statistics is still counting the hours even after terminated the Azure VM agents Previously, I thought only when provision process being terminated by accident will cause the issue. However, it seems a success provision will also cause this problem from your logs. I don't know how to reproduce this issue when all the provision processes are good. So, my solution is to detect whether an uncompleted cloud statistics can map to a planned node to running node. Then mark the trace to complete or failed according to whether the node is exiting. Can you accept this solution? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43028) Request to add support for Azure Managed Disks
Title: Message Title Chenyang Liu commented on JENKINS-43028 Re: Request to add support for Azure Managed Disks Nathan Lindop From 0.4.7 we start to support managed disk. If you means custom managed disk support, we haven't support it, it's JENKINS-48076. But we will support it in the next release version. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48345) Cloud statistics is still counting the hours even after terminated the Azure VM agents
Title: Message Title Chenyang Liu commented on JENKINS-48345 Re: Cloud statistics is still counting the hours even after terminated the Azure VM agents Seems if the issues happen, it will hang in provisioning. Did your guys ever meet that the status hang in other states(Launch, Operation) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41569) Pipeline hangs waiting for resume on an agent which never was
Title: Message Title Chenyang Liu closed an issue as Fixed Jenkins / JENKINS-41569 Pipeline hangs waiting for resume on an agent which never was Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32568) Add custom-data to Azure slave deployment
Title: Message Title Chenyang Liu closed an issue as Fixed It's a very old issue. If there's also a problem in the latest plugin, please feel free to reopen and leave commends. Jenkins / JENKINS-32568 Add custom-data to Azure slave deployment Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.
[JIRA] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Chenyang Liu closed an issue as Fixed It's a very old problem. If there's also a issue in the latest plugin, please feel free to reopen and leave commends Jenkins / JENKINS-30014 Builds hang, Jenkins still browseable Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-48253) Empty list of existing Storage Account Names
Title: Message Title Chenyang Liu commented on JENKINS-48253 Re: Empty list of existing Storage Account Names Billy Sheppard You need to do some change in storageAccountType or ResourceGroupName to let Jenkins UI to reload the existing storage account. Or you can save your configuration and reopen the global configuration, then the account will also be reloaded. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49107) Deployments to resource groups are never cleaned up, resource group eventually refuses further deployments, plugin stops working
Title: Message Title Chenyang Liu closed an issue as Fixed It should be fixed in 0.6.0. If the issue also exists, please leave comment. Jenkins / JENKINS-49107 Deployments to resource groups are never cleaned up, resource group eventually refuses further deployments, plugin stops working Change By: Chenyang Liu Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-49473) Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure
Title: Message Title Chenyang Liu commented on JENKINS-49473 Re: Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure Seems you had deleted the cloud in configuration at that time, so got a NullPointerException. Did you meet the same issue later. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49212) Windows sshInit.ps1 doesn't work on Windows Server Core
Title: Message Title Chenyang Liu resolved as Fixed Jenkins / JENKINS-49212 Windows sshInit.ps1 doesn't work on Windows Server Core Change By: Chenyang Liu Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Chenyang Liu assigned an issue to Chenyang Liu Jenkins / JENKINS-49725 Windows SSH init broken, as of 2018-02-22 Change By: Chenyang Liu Assignee: Azure DevOps Chenyang Liu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Chenyang Liu commented on JENKINS-49725 Re: Windows SSH init broken, as of 2018-02-22 Thanks, we will fix it immediately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Chenyang Liu commented on JENKINS-49576 Re: Failure creating provisioned agent after successful provisioning That's a very strange log, because the launching must be after the provision returns "succeeded". Thus, I can only guess the reason. Do you running multiple Jenkins master and one of it is copied from another. Also you can give me a file with full logs, and can you reproduce the issue stably? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Chenyang Liu commented on JENKINS-49576 Re: Failure creating provisioned agent after successful provisioning Seems the reason is exceeding the deployment timeout. You can try to change the deployment timeout to a larger number in cloud configuration and retry. Also if you find your deployment costs too much time, you can try to change your VM size(e.g. DS2V2). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
