Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-339

Plugins site api: Cannot index with new data

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I am currently testing plugins.jenkins deployment on infra.

      But I recently got systematically  500 errors each time I do another request than <api>/info.

      I am using docker image: jenkinsciinfra/plugin-site:47-df13c8

      with following informations

      REST_API_URL=<set to an api url other than localhost>

      DATA_FILE_URL= "https://ci.jenkins.io/job/Infra/job/plugin-site-api/job/generate-data/lastSuccessfulBuild/artifact/plugins.json.gzip"

      Logs output -> https://gist.github.com/olblak/9a452e0a24fe1875e4dc57345186a2fd

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          mmccaskill Michael McCaskill added a comment - - edited

          Line 61 is the flag here. The API is unable to ingest the file from DATA_FILE_URL because that image has a different version of the plugins.json. This is part of the checks in link ElasticsearchPrepareDatastoreService. The intention is to protected the running API from attempting to ingest files it cannot. Almost exclusively this will be because the mappings have changed.

          The real fix for this is to either

          1. Fix the master job so that you can get an updated image that will accept the DATA_FILE_URL
          2. Generate your own data and serve it up
          Show
          mmccaskill Michael McCaskill added a comment - - edited Line 61 is the flag here. The API is unable to ingest the file from DATA_FILE_URL because that image has a different version of the plugins.json . This is part of the checks in link ElasticsearchPrepareDatastoreService . The intention is to protected the running API from attempting to ingest files it cannot. Almost exclusively this will be because the mappings have changed. The real fix for this is to either Fix the master job so that you can get an updated image that will accept the DATA_FILE_URL Generate your own data and serve it up
          Hide
          Permalink
          mmccaskill Michael McCaskill added a comment -

          Let me know if this is unclear or confusing. I'm happy to help but I don't have any access to the actual infrastructure so I imagine I'm of limited help.

          Show
          mmccaskill Michael McCaskill added a comment - Let me know if this is unclear or confusing. I'm happy to help but I don't have any access to the actual infrastructure so I imagine I'm of limited help.
          Hide
          Permalink
          olblak Olivier Vernin added a comment -

          It was exactly that.

          As master branch is correctly building, everything is working fine.

          For future, It  may be interesting to not use 'latest' but specific version to keep track versions compatibility between 'data file url'  and 'docker image version'

           

          Show
          olblak Olivier Vernin added a comment - It was exactly that. As master branch is correctly building, everything is working fine. For future, It  may be interesting to not use 'latest' but specific version to keep track versions compatibility between 'data file url'  and 'docker image version'  
          Hide
          Permalink
          olblak Olivier Vernin added a comment -

          everything is working fine as master branch is building correctly,

          Show
          olblak Olivier Vernin added a comment - everything is working fine as master branch is building correctly,

            People

            Assignee:
            mmccaskill Michael McCaskill
            Reporter:
            olblak Olivier Vernin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: