Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48345

Cloud statistics is still counting the hours even after terminated the Azure VM agents

XMLWordPrintable

      Hi Team,

       

      Have terminated the Azure VM agent but Cloud stat is still counting the hours of Azure VM agent. It is simply using the resources on Jenkins and don't have clue to terminate this

       

      Attached the screen shot

        1. jenkins.cloud.log
          7 kB
        2. Screen Shot 2017-12-01 at 1.12.20 PM.jpg
          Screen Shot 2017-12-01 at 1.12.20 PM.jpg
          103 kB
        3. Screen Shot 2017-12-04 at 10.08.40 AM.jpg
          Screen Shot 2017-12-04 at 10.08.40 AM.jpg
          99 kB
        4. Screenshot at 2018-03-05 10-53-07.png
          Screenshot at 2018-03-05 10-53-07.png
          56 kB
        5. Screenshot at 2018-03-19 16-37-37.png
          Screenshot at 2018-03-19 16-37-37.png
          80 kB

          [JENKINS-48345] Cloud statistics is still counting the hours even after terminated the Azure VM agents

          Sabitha Sathesh added a comment -

          Any update how to clean this data?

          Sabitha Sathesh added a comment - Any update how to clean this data?

          Henti Smith added a comment -

          I have a similar problem. Machine was provisioned, job executed and then deleted after idle, but the cloud statistics page shows it still provisioning. 

          H

          Henti Smith added a comment - I have a similar problem. Machine was provisioned, job executed and then deleted after idle, but the cloud statistics page shows it still provisioning.  H

          Chenyang Liu added a comment -

          Seems if the issues happen, it will hang in provisioning. Did your guys ever meet that the status hang in other states(Launch, Operation)

          Chenyang Liu added a comment - Seems if the issues happen, it will hang in provisioning. Did your guys ever meet that the status hang in other states(Launch, Operation)

          Sabitha Sathesh added a comment -

          No i have not seen status hang in other states (Launch, Operation)

          Sabitha Sathesh added a comment - No i have not seen status hang in other states (Launch, Operation)

          Henti Smith added a comment -

          25 days and still showing. 

          I've attached logs of the 25 day machine. 

          jenkins.cloud.log

          H

          Henti Smith added a comment - 25 days and still showing.  I've attached logs of the 25 day machine.  jenkins.cloud.log H

          Chenyang Liu added a comment -

          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?

          Chenyang Liu added a comment - 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?

          Henti Smith added a comment -

          zackliu, Sounds good to me. 

          Henti Smith added a comment - zackliu , Sounds good to me. 

          Chenyang Liu added a comment -

          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. 

          Chenyang Liu added a comment - 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. 

          Henti Smith added a comment -

          We are using Once strategy without shutdown, so each VM is used once and then deleted. 

          Henti Smith added a comment - We are using Once strategy without shutdown, so each VM is used once and then deleted. 

          Azure DevOps added a comment -

          Fixed in 0.7.0

          Azure DevOps added a comment - Fixed in 0.7.0

            zackliu Chenyang Liu
            sabithasathesh Sabitha Sathesh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: