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

Cloud-statistics records does not reflect cloud removals

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • cloud-stats-plugin
    • None
    • Jenkins Version 2.73.1

    Description

      I removed a specific docker cloud from the configure page on page in jenkins however the cloud-stats plugin still shows it.

      Right now inside the configure page there is no cloud with that specific name - yet the cloud-stats plugin still shows the docker cloud.

      Shouldn't it be removed once we remove the cloud?

      Attachments

        Activity

          The records will be rotated once replaced by new provisioning attempts. There is a way to improve this as you suggested by detecting cloud deletion but we can not detect cloud rename (and tell renames from deletions/creations) so I prefer to keep this the way it is. Another thing is we can not detect this for templates that are not covered by Cloud API at all.

          I am keeping this open as I am not quite satisfied with the way things are. Consider last cloud is deleted and the records keep hanging there forever.

          olivergondza Oliver Gondža added a comment - The records will be rotated once replaced by new provisioning attempts. There is a way to improve this as you suggested by detecting cloud deletion but we can not detect cloud rename (and tell renames from deletions/creations) so I prefer to keep this the way it is. Another thing is we can not detect this for templates that are not covered by Cloud API at all. I am keeping this open as I am not quite satisfied with the way things are. Consider last cloud is deleted and the records keep hanging there forever.

          Thanks Olivier - I will keep watching this issue.

          jlouisfoster James Louis-Foster added a comment - Thanks Olivier - I will keep watching this issue.

          Hi Oliver,

          We have provisioned hundreds of new docker containers but the old Dockerhost still remains. Any specific way to manually remove it? 

          jlouisfoster James Louis-Foster added a comment - Hi Oliver, We have provisioned hundreds of new docker containers but the old Dockerhost still remains. Any specific way to manually remove it? 

          I know something like that can happen when the activity is not considered completed - presumably because it has leaked in PROVISIONING state. The easiest way to go from here is to edit the .xml file while Jenkins is down and remove the offending entry. The fix for this bug is on my todo and will hopefully be released soon.

          olivergondza Oliver Gondža added a comment - I know something like that can happen when the activity is not considered completed - presumably because it has leaked in PROVISIONING state. The easiest way to go from here is to edit the .xml file while Jenkins is down and remove the offending entry. The fix for this bug is on my todo and will hopefully be released soon.
          zxiiro Thanh Ha added a comment -

          We are seeing this issue as well. Is there still plans to resolve this?

          zxiiro Thanh Ha added a comment - We are seeing this issue as well. Is there still plans to resolve this?
          winnerwbx Andy Wang added a comment -

          My workaround:

          I tried to delete some of the xml elements which should be removed in in org.jenkinsci.plugins.cloudstats.CloudStatistics.xml but the Jenkins crashed after login. 

          So I came up an idea to delete everything in that file and restart Jenkins. It didn't crash. And all the cloud statistics history is gone. I'm OK with this because what's matters most is to display the latest provisioning status and remove the annoying old cloud status which should have been removed long ago.

          winnerwbx Andy Wang added a comment - My workaround: I tried to delete some of the xml elements which should be removed in in org.jenkinsci.plugins.cloudstats.CloudStatistics.xml but the Jenkins crashed after login.  So I came up an idea to delete everything in that file and restart Jenkins. It didn't crash. And all the cloud statistics history is gone. I'm OK with this because what's matters most is to display the latest provisioning status and remove the annoying old cloud status which should have been removed long ago.

          People

            olivergondza Oliver Gondža
            jlouisfoster James Louis-Foster
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: