Troubleshoot Editing and Pushing Content - Administrator Guide - EoL - 6.10 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Product
Cortex XSOAR
Version
6.10
Creation date
2022-10-13
Last date published
2024-07-14
Category
Administrator Guide
End of Life > EoL
Abstract

Troubleshoot editing and pushing content to Cortex XSOAR remote repository.

The following instructions describe how to troubleshoot when editing and pushing your content to the remote repository.

Invalid Signatures When Committing

When you push your content to the remote repository, you might receive the following error message: Error: Commits musthave valid signatures.

This occurs when your Git server configuration requires that every commit must have a signature.

  1. Connect to the remote repository server using SSH.

  2. Run the following commands:

    • git--global config user.signingKey KEYID where KEYID is your key ID.

    • git --global config commit.gpgSign true

GIT Version Out-of-Date

When you push your content to the remote repository, you might receive the following error message: error GIT: failedexecuting [rebase [--exec=git log --max-count=1 --pretty=format:%H;printf'>';grep -o "\w\{40\}" .git/rebase-merge/done | tail -n 1 --strategyrecursive --strategy-option theirs --onto stag --root stag_workspace]]

This occurs when you have an outdated Git version on your server. You must have at least version 2.21.0.

To update your Git version:

  1. Export the custom content by going to SettingsAboutTroubleshootingCustom contentExport.

    This exports the state of the current content.

  2. Turn off the remote repository feature on the dev server.

  3. On your server, either download and install an updated RPM package of the Git client, or run the Demsito installer again.

  4. Turn on the remote repository feature on the dev server.

  5. Import the previously exported content.

    This restores the local content.