Pipelines Error Messages

JFrog Pipelines Documentation

ft:sourceType
Paligo

This section lists commonly-encountered Pipelines error messages, possible causes, and some suggestions for resolving the errors. If you have trouble fixing any of these errors, submit a request to Support for further investigation.

Error: All resource versions are not fetched

Error

reqKick|executeStep|step|prepData|jFrogPipelinesSessionId:28be9c21-4ad6-4e3d-9411-7b9988535fd1|_getResourceVersions, 
All resource versions are not fetched. Requested resource versions: 16; received resource versions: []

Cause

After the run was triggered, but before it started running, one or more resources in the pipeline were reset. Hence, while fetching the resources associated with the run, the resource version was returned as an empty array.

Resolution

Re-run the pipeline.

When a resource is reset, it wipes out the resource version history and resets it to a single version, which is now considered the latest. This version is used for the new run.

Error: fatal: reference is not a tree

Error

fatal: reference is not a tree: 679e2fc3c2590f7dbaf64534a325ac60b4dc8689

Cause

This could be a result of using git push --force or git rebase, which deletes the commit and causes the pipeline to not run.

Resolution

Either:

  • Reset the resource and then trigger the pipeline again. To learn how to reset a resource, Refer to Resetting Resources in the UI section.

    Note

    If there are several GitRepo resources in the pipeline, this needs to be done for all of them.

or

  • Push another commit so that all the resources are updated automatically.

Error: Failed to create pvc for node

Error

Failed to create pvc for node

Cause

Either the Kubernetes configuration does not have access to create a Persistent Volume Claim (PVC) resource or Pipelines cannot connect to the provided Kubernetes host server.

Resolution

Review the Kubernetes configurationsand verify that the Kube Config provided while creating the Kubernetes Integration hasadequate permissions.

Error: SCM provider credentials do not have enough permissions

Error

The credentials provided for the integration "<integration_name>" do not have 
enough permissions. Ensure that the credentials exist and have the correct 
permissions for the provider: github.

Cause

The credentials (username and/or token) provided while creating the integration are either incorrect or insufficient.

Resolution

Ensure that the credentials provided for the SCM provider are correct and have sufficient permissions.

Error: SCM provider URL is invalid

Error

The URL provided for the integration “<integration_name>” is invalid. 
Provide a valid URL for the SCM provider and try again.

Cause

The SCM URL provided while creating the integration is incorrect.

Resolution

Ensure that the URL provided for the SCM provider is correct.

Error: SCM provider repository path is invalid

Error

The repository path "<repo_path>" is either invalid or does not exist. 
Ensure that the repository path exists and has the correct permissions 
for the integration: <integration_id>.

Cause

The repository path provided for the SCM provider is either incorrect or does not exist.

Resolution

Ensure that the repository name provided for the SCM provider is correct.

Error: Step type cannot be updated

Error

type cannot be updated from <step_type> to <step_type> in step <step_name>

Example: build/ci/pipelines.yml: type cannot be updated from Bash to Matrix in step e2e_local_tests

Cause

After the pipeline performs a sync, a step's type should not be modified, as it can cause pipeline sync errors.

Resolution

Though not recommended, if you do want to change a step's type, perform the following steps:

  1. Change the step's name and type

  2. Wait for pipeline sync

  3. After the sync completes, change the step's name back to the old name

Error: Ubuntu 16.04 not supported

Error

Ubuntu_16.04 has reached end of support. Please upgrade to a higher version.

Cause

Ubuntu Linux 16.04 LTS reached the end of its five-year LTS window on April 30th 2021 and is no longer supported by its vendor. Due to this,Pipelines no longer supports your existing Ubuntu 16 node pools.

Resolution

  • Dynamic Node Pools: Existing Ubuntu 16 dynamic pools will be automatically migrated to Ubuntu 18 provided those were created with the default build plane images. If you have any custom Ubuntu 16 node pools, they must be manually migrated to Ubuntu 18 or higher.

  • Static Node Pools: Upgrade all your existing Ubuntu 16 static node pools to Ubuntu 18 or higher.

For information about the supported Ubuntu versions, see the System Requirements Matrix.System Requirements

Error: CentOS 8.0 not supported

Error

CentOS 8 has reached end of support. Please change the OS to another supported version. 
For the list of supported versions, see System Requirements.

Cause

CentOS 8.x reached end-of-life is on December, 2021 and is no longer supported by its vendor. Due to this, Pipelines no longer supports your existing CentOS 8 node pools.

Resolution

  • Dynamic Node Pools: Existing CentOS 8.x dynamic pools will be automatically migrated to CentOS 7.0 provided those were created with the default build plane images. If you have any custom CentOS 8.x node pools, they must be manually migrated to either CentOS 7.0 or a different OS.

  • Static Node Pools: After upgrading to the next major release of Pipelines, either remove any CentOS 8.x node pools or change the machine image to a different OS.

For the list of supported OS versions, see System Requirements.System Requirements

Error: postHook returned error 422

Error

Failed to sync hook with err: Webhook creation failed for path: userName/repoName and 
integration: myGithub with err: postHook returned error 422 for userName/repoName

Cause

This is usually the result of too many webhooks. GitHub allows 20 webhooks per repository.

Resolution

In GitHub, go to the Settings | Webhooks tab for the relevant repository and delete all the failed webhooks.

Error: Connection was not successful

Error

Connection was not successful

Cause

One of the reasons for this message to appear is when the Artifactory/Distribution URL provided for the integration is incorrect.

Resolution

Verify that your Artifactory/Distribution URL provided for the integration is correct. If you find that it is incorrect, update the URL and use the Test Connection button to verify, and then save.

Error: step "step_name" cannot interrupt affinityGroup "affinity_group_name".

Error

custupd_docker: step "bundle" cannot interrupt affinityGroup "group1".
Connection was not successful

Cause

This occurs when there are multiple steps in a pipeline and the intermediate step(s) belong to a different affinity group. This interrupts the flow of the steps.

For example: There are three steps in sequence, Step AStep B, and Step CStep A and Step C are part of the affinity group Group A, but Step B is part of the affinity group Group B.

Resolution

Define all the steps and its dependencies in the same affinity group. There should not be any intermediate steps that are part of a different affinity group.

For example, do one of the following: 

  • Define Step A, Step B, and Step C in the same affinity group

  • Define Step A and Step B in the same affinity group, with Step C in a different affinity group

  • Define Step A in an affinity group, with Step B and Step C in a different affinity group

Error: Unable to get branches Ensure that the repository path exists and has the correct permissions for the integration id: 326

Error

Unable to get branches Ensure that the repository path exists and 
has the correct permissions for the integration id: 326
custupd_docker: step "bundle" cannot interrupt affinityGroup "group1".
Connection was not successful

Cause

This happens when the token has expired.

Resolution

Use Test Connection to check the connection. If the test fails, use a new token and try again.

Error: Pipeline <pipeline_name> has invalid integrations <credentials> in configuration.integrations.

Error

Pipeline <pipeline_name> has invalid integrations <credentials> in configuration 
integrations.Please check that they exist and that they are allowed to be used by this pipeline source.

Cause

The integration is not shared with the Project.

Resolution

Ensure that the integrations mentioned in the pipeline are added to or shared with the Project.

Error: One or more of the steps in this pipeline has become inconsistent since the last successful sync. Please sync your pipeline now to try and correct this.

Error

One or more of the steps in this pipeline has become inconsistent since 
the last successful sync. 
Please sync your pipeline now to try and correct thisck that they exist and 
that they are allowed to be used by this pipeline source.

Cause

The integration is not shared with the Project.

Resolution

Ensure that the integrations mentioned in the pipeline are added to or shared with the Project.

Error: Pipeline has disconnected steps

Error

Pipeline <pipeline_name> has disconnected step(s): <step_name>

Cause

This happens when the step mentioned in the error is not an input/output to any other step.

Resolution

Add the step as an input/output to another step in the pipeline.

Issue: Build is triggered on branch and master. Expectation is to trigger only on branch

Issue

Build gets triggered on branch and master on creation of PR. Expectation is to trigger pipeline only on branch

Example

resources:
  - name: {{ .Values.gitResourceName }}
    type: GitRepo
    configuration:
      gitProvider: {{ .Values.gitProvider }}
      path: {{ .Values.repoPath }}
      files:
        exclude: .jfrog-pipelines/*
      branches:
        include: {{gitBranch}}
      pullRequestTargetBranches:
        include: master
      buildOn:
        pullRequestCreate: true

Cause

This is because pullRequestTargetBranches is set to master, which causes the master branch to also get triggered.

Resolution

This can be solved using one of the following:

  • Check if gitBranch is not equal to master

    resources:
      - name: {{ .Values.gitResourceName }}
        type: GitRepo
        configuration:
          gitProvider: {{ .Values.gitProvider }}
          path: {{ .Values.repoPath }}
          files:
            exclude: .jfrog-pipelines/*
          branches:
            include: {{gitBranch}}
          {{ if ne "{{gitBranch}}" "master" }}
          pullRequestTargetBranches:
            include: master
          {{ end }}
          buildOn:
            pullRequestCreate: true

    Or

  • Disable pullRequestCreate for master branch

    resources:
      - name: {{ .Values.gitResourceName }}
        type: GitRepo
        configuration:
          gitProvider: {{ .Values.gitProvider }}
          path: {{ .Values.repoPath }}
          files:
            exclude: .jfrog-pipelines/*
          branches:
            include: {{gitBranch}}
          pullRequestTargetBranches:
            include: master
          buildOn:
            pullRequestCreate: {{ ne "{{gitBranch}}" "master" }}

Error: 'Missing body data :systemPropertyBag : gitRepoRepositoryUrl,gitRepoRepositorySshUrl,gitRepoRepositoryHttpsUrl,isPrivateRepository,repositoryProvider,gitRepoFullName',

Error

Example

'Missing body data :systemPropertyBag : gitRepoRepositoryUrl,gitRepoRepositorySshUrl,gitRepoRepositoryHttpsUrl,isPrivateRepository,repositoryProvider,gitRepoFullName',

Cause

This sync error happens if the integration used in the gitRepo resource doesn't have enough admin permissions on the repository used in the resource.

Resolution

Ensure that the credentials provided for the SCM provider are correct and have sufficient permissions.

Error: error validating "/opt/jfrog/pipelines/var/tmp/45z4c889-b85v-36c0-802e-gg9b2d77a534/node-0cf98045-ght.json": error validating data: the server has asked for the client to provide credentials; if you choose to ignore these errors, turn validation off with --validate=false

Error

Example

error validating "/opt/jfrog/pipelines/var/tmp/45z4c889-b85v-36c0-802e-gg9b2d77a534/node-0cf98045-ght.json": error validating data: the server has asked for the client to provide credentials; if you choose to ignore these errors, turn validation off with --validate=false

Cause

This error can occur if the kubeconfig file contains too many contexts and users

Resolution

Consider simplifying your kubeconfig file by including just one context and user, as having multiple contexts and users can lead to problems.