Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-19773

Include a message about "Sidecar cannot be disabled" in the Bitbucket logs

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Mesh
    • None
    • 10
    • 2
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      While upgrading from a version older than 8.19, we would see the below message in the browser because Mesh Sidecar was disabled in the older version:

      A fatal error has occurred

      The following problem occurred, which prevents Atlassian Bitbucket from starting:

      • The system has been configured not to use the Sidecar process for Git operations. Mesh and the Sidecar process are now required and can not be disabled anymore. Remove these properties from 'bitbucket.properties' to continue using the system:
        • mesh.enabled=false
          plugin.bitbucket-git.mesh.sidecar.enabled=false

      There's no mention of this message in the Bitbucket logs anywhere. Hence unless Bitbucket is accessible in the browser, we wouldn't know that this is even an issue.

      Bitbucket is inaccessible in the browser in situations where:

      • In a Kubernetes environment, the livenessProbe or readinessProbe are not disabled, so Bitbucket doesn't even load on the browser
      • In an on-prem setup, the proxy is causing issues, and we see a proxy 500 or 503 response code, instead of the Mesh error above.

              Unassigned Unassigned
              04f11a9d4cc8 Apoorva
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: