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

Restricted clouds not visible in folder configuration

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • kubernetes-plugin
    • None
    • Jenkins 2.361.1 (also tested on 2.356 and 2.359)
      kubernetes-plugin 3704.va_08f0206b_95e (3663.v1c1e0ec5b_650 and 3651.v908e7db_10d06)

      We have a few kubernetes clusters configured as "restricted clouds", and only a few folders have permissions to use them.

      This week we changed an unrelated configuration in one of those folders, and the folder suddenly lost permissions to use the restricted cloud.

      Inspecting the `config.xml` of that folder, we noticed that the section `org.csanchez.jenkins.plugins.kubernetes.KubernetesFolderProperty` was entirely missing. Other folders, which haven't been modified, still had that section, so we could at least restore the functionality by manually editing the broken `config.xml`

      The folder configuration in the jenkins UI shows the following:

          [JENKINS-69014] Restricted clouds not visible in folder configuration

          I'm encountering the same issue, however they do show up with regular Folders here, I'm only having the issue with the Multibranch Pipeline or GitHub Organization Folder projects. Which is definitely a regression as I have originally set it up using these organization folders / multibranch pipelines.

          Versions of Jenkins core and plugins I'm using:

          • Jenkins: 2.346.3
          • Folders Plugin: 6.740.ve4f4ffa_dea_54 
          • Pipeline: Multibranch: 716.vc692a_e52371b_
          • GitHub Branch Source Plugin: 1687.v7618247e672d
          • Kubernetes plugin: 3704.va_08f0206b_95e 

          I would say the Pipeline: Multibranch and Kubernetes plugins would be the main suspects in that case, I'll try to downgrade things to see what's still working (which is a challenge in itself as it does not allow me to downgrade plugins that have dependents).

          Henno Schooljan added a comment - I'm encountering the same issue, however they do show up with regular Folders here, I'm only having the issue with the Multibranch Pipeline or GitHub Organization Folder projects. Which is definitely a regression as I have originally set it up using these organization folders / multibranch pipelines. Versions of Jenkins core and plugins I'm using: Jenkins: 2.346.3 Folders Plugin: 6.740.ve4f4ffa_dea_54   Pipeline: Multibranch: 716.vc692a_e52371b_ GitHub Branch Source Plugin: 1687.v7618247e672d Kubernetes plugin: 3704.va_08f0206b_95e   I would say the Pipeline: Multibranch and Kubernetes plugins would be the main suspects in that case, I'll try to downgrade things to see what's still working (which is a challenge in itself as it does not allow me to downgrade plugins that have dependents).

          Indeed, it works with regular folders.

          Our issue is with multibranch folders created by the GitLab Branch Source plugin (Version 633.ved9984f943da_)

          Giuseppe Iannello added a comment - Indeed, it works with regular folders. Our issue is with multibranch folders created by the GitLab Branch Source plugin (Version 633.ved9984f943da_)

          As of today, running latest plugins version, the issue seems to be solved. hennobitfactory can you confirm?

          Giuseppe Iannello added a comment - As of today, running latest plugins version, the issue seems to be solved. hennobitfactory can you confirm?

          giannello Yes confirmed working again here as well. I suppose this fixed it: https://github.com/jenkinsci/kubernetes-plugin/pull/1243

          Henno Schooljan added a comment - giannello Yes confirmed working again here as well. I suppose this fixed it: https://github.com/jenkinsci/kubernetes-plugin/pull/1243

          Dietmar added a comment -

          I have the same problem.  When a Jenkins adminsitrator sets up a restricted Kubernets cloud configuration in the job, I can't see it as a normal user. When I then save the job configuration the entry is lost and has to be added back by an administrator. This is reproducible.

          Jenkins: 2.387.1

          Kubernets-Plugin: Kubernetes pluginVersion3896.v19b_160fd9589

          Folder Plugin: cloudbees-folder@6.800.v71307ca_b_986b

          Dietmar added a comment - I have the same problem.  When a Jenkins adminsitrator sets up a restricted Kubernets cloud configuration in the job, I can't see it as a normal user. When I then save the job configuration the entry is lost and has to be added back by an administrator. This is reproducible. Jenkins: 2.387.1 Kubernets-Plugin: Kubernetes pluginVersion3896.v19b_160fd9589 Folder Plugin: cloudbees-folder@6.800.v71307ca_b_986b

          Confirming similar problem on latest Jenkins

          Oleg Zheltyannikov added a comment - Confirming similar problem on latest Jenkins

          Laura added a comment -

          Confirmed, we have the same issue as reported by dietmarpradler - the original issue reported by giannello is fixed, but the restricted clouds are still lost when saved by a non-admin.

          Laura added a comment - Confirmed, we have the same issue as reported by dietmarpradler - the original issue reported by giannello is fixed, but the restricted clouds are still lost when saved by a non-admin.

            Unassigned Unassigned
            giannello Giuseppe Iannello
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: