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

Disabling plugins in the Plugin Manager throws a JavaScript error due to permissions error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      When unchecking a plugin in the 'Installed' checkbox in the Plugin Manager, a JavaScript error is thrown:

      XML Parsing Error: no root element found
      Location: http://localhost:8081/pluginManager/plugin/ant/makeDisabled
      Line Number 1, Column 1:
      

      Due to empty response body.

        Attachments

          Activity

          Hide
          rtyler R. Tyler Croy added a comment -

          FWIw, easily reproducible with the jenkins/jenkins:lts-alpine container right now at 2.107.1

          Show
          rtyler R. Tyler Croy added a comment - FWIw, easily reproducible with the jenkins/jenkins:lts-alpine container right now at 2.107.1
          Hide
          danielbeck Daniel Beck added a comment -

          The URL you're trying to access requires that requests be sent using POST (like a form submission). The button below allows you to retry accessing this URL using POST. URL being accessed:</p><p><tt>http://localhost:8081/pluginManager/plugin/ant/makeDisabled</tt

          Method Not Allowed. Weird.

          right now at 2.107.1

          I hope this is just a typo 2.121.1.

          Interestingly, this is all from https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/PluginManager/installed.jelly and that specifically sends an AJAX POST request when toggling a button. Unclear how that could end up being GET. I also cannot reproduce this problem at all with lts-alpine at 2.121.2. In the wizwrd, I customized installed plugins, accepted the admin user, and set the root URL. Immediately afterwards I successfully disabled a plugin.

          Show
          danielbeck Daniel Beck added a comment - The URL you're trying to access requires that requests be sent using POST (like a form submission). The button below allows you to retry accessing this URL using POST. URL being accessed:</p><p><tt> http://localhost:8081/pluginManager/plugin/ant/makeDisabled </tt Method Not Allowed. Weird. right now at 2.107.1 I hope this is just a typo 2.121.1. Interestingly, this is all from https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/PluginManager/installed.jelly and that specifically sends an AJAX POST request when toggling a button. Unclear how that could end up being GET. I also cannot reproduce this problem at all with lts-alpine at 2.121.2. In the wizwrd, I customized installed plugins, accepted the admin user, and set the root URL. Immediately afterwards I successfully disabled a plugin.
          Hide
          danielbeck Daniel Beck added a comment -

          Needs steps to reproduce.

          Show
          danielbeck Daniel Beck added a comment - Needs steps to reproduce.
          Hide
          rtyler R. Tyler Croy added a comment -

          Verified with a fresh installation of 2.121.1.

          1. Install suggested plugins
          2. Navigate to http://localhost:8080/pluginManager/installed
          3. Open the JavaScript Error Console (F12)
          4. Click the 'Ant' checkbox
          5. Observe XML parsing error because the XMLHttpRequest returned an HTML 500 page
          Show
          rtyler R. Tyler Croy added a comment - Verified with a fresh installation of 2.121.1. Install suggested plugins Navigate to http://localhost:8080/pluginManager/installed Open the JavaScript Error Console (F12) Click the 'Ant' checkbox Observe XML parsing error because the XMLHttpRequest returned an HTML 500 page
          Hide
          danielbeck Daniel Beck added a comment -

          Via IRC, the response body is actually empty and 405 is just when looking at this in the browser error console. HTTP 500 was a typo.

          Show
          danielbeck Daniel Beck added a comment - Via IRC, the response body is actually empty and 405 is just when looking at this in the browser error console. HTTP 500 was a typo.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: