Upgrading to 16.11.3 gives: Error while processing content unencoding: invalid stored block lengths
Summary
After patching our Gitlab EE 16.11.2 instance to version 16.11.3 we get an error when pulling a git repo or starting a Gitlab pipeline showing the following message:
Error while processing content unencoding: invalid stored block lengths
Steps to reproduce
Rollout Gitlab EE 16.11.2 in a Kubernetes environment via Helm. Create a gitrepo containing data and a valid .gitlab-ci.yml. Patch to version 16.11.3 via Helm and start a pipeline or pull the gitrepository.
Configuration used
(Please provide a sanitized version of the configuration used wrapped in a code block (```yaml))
certmanager:
install: false
gitlab:
gitaly:
extraEnv: []
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitaly
persistence:
accessMode: ReadWriteOnce
enabled: true
storageClass: null
resources: {}
gitlab-exporter:
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-exporter
resources: {}
gitlab-shell:
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-shell
resources:
requests:
cpu: 50m
memory: 50M
migrations:
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-toolbox-ee
sidekiq:
hpa:
cpu:
targetAverageValue: 350m
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-sidekiq-ee
maxReplicas: 4
minReplicas: 3
registry:
enabled: false
resources:
limits:
memory: 4Gi
requests:
cpu: 900m
memory: 2Gi
toolbox:
backups:
cron:
enabled: true
extraArgs: --skip artifacts --skip registry --skip uploads --skip lfs --skip
packages --skip external_diffs --skip terraform_state --maximum-backups
5
persistence:
enabled: true
size: 300Gi
storageClass: ""
resources:
limits:
cpu: 3
memory: 16Gi
requests:
cpu: 1
memory: 1Gi
schedule: 0 7 * * *
objectStorage:
config:
key: config
secret: minio-s3cfg
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-toolbox-ee
persistence:
enabled: true
size: 300Gi
storageClass: ""
psql:
host: gitlab-db-rw
registry:
enabled: false
resources: {}
webservice:
hpa:
cpu:
targetAverageValue: 1600m
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-webservice-ee
ingress:
enabled: false
maxReplicas: 3
maxUnavailable: 1
minReplicas: 2
registry:
enabled: false
resources:
limits:
memory: 3Gi
requests:
cpu: 500m
memory: 2.5Gi
workerProcesses: 2
workhorse:
image: registry.gitlab.com/gitlab-org/build/cng/gitlab-workhorse-ee
resources: {}
global:
appConfig:
artifacts:
bucket: sp-gitlab-artifacts
connection:
secret: rails-s3
backups:
bucket: sp-gitlab-backup
tmpBucket: sp-gitlab-recovery-tmp
cron_jobs:
pipeline_schedule_worker:
cron: '*/5 * * * *'
defaultProjectsFeatures:
containerRegistry: false
enableUsagePing: false
externalDiffs:
bucket: sp-gitlab-mr-diffs
connection:
secret: rails-s3
lfs:
bucket: sp-gitlab-lfs
connection:
secret: rails-s3
omniauth:
allowSingleSignOn:
- keycloak
autoLinkLdapUser: false
autoLinkSamlUser: false
autoSignInWithProvider: keycloak
blockAutoCreatedUsers: false
enabled: true
externalProviders:
- keycloak
providers:
- key: provider
secret: oidc-provider
syncProfileAttributes:
- name
- email
syncProfileFromProvider:
- keycloak
packages:
bucket: sp-gitlab-packages
connection:
secret: rails-s3
enabled: false
pseudonymizer:
bucket: sp-gitlab-pseudo
connection:
secret: rails-s3
terraformState:
bucket: sp-gitlab-terraform-state
connection:
secret: rails-s3
enabled: true
time_zone: UTC
uploads:
bucket: sp-gitlab-uploads
connection:
secret: rails-s3
usernameChangingEnabled: false
busybox:
image:
repository: harbor.xxxx.com/sp/busybox
tag: latest
certificates:
image:
repository: registry.gitlab.com/gitlab-org/build/cng/certificates
hosts:
domain: dev.xxx.com
gitlab:
name: gitlab.dev.xxx.com
minio:
https: true
name: gitlab-minio.dev.xxx.com
ingress:
class: nginx
configureCertmanager: false
enabled: false
initialRootPassword:
key: password
secret: gitlab-gitlab-initial-root-password
kas:
enabled: false
kubectl:
image:
repository: registry.gitlab.com/gitlab-org/build/cng/kubectl
minio:
enabled: false
psql:
database: gitlab-db
host: gitlab-db-pooler
password:
key: password
secret: gitlab-db-user-password
port: 5432
username: gitlab
railsSecrets:
secret: gitlab-rails-secret
registry:
bucket: sp-gitlab-registry
enabled: false
minio:
image: harbor.xxxx.com/docker-hub/minio/minio
imageTag: latest
minioMc:
image: harbor.xxxx.com/docker-hub/minio/mc
tag: latest
persistence:
enabled: true
size: 10Gi
storageClass: null
nginx-ingress:
enabled: false
postgresql:
install: false
metrics:
enabled: false
volumePermissions:
securityContext:
runAsUser: 1001
prometheus:
install: false
redis:
global:
imageRegistry: harbor.xxxx.com/docker-hub
master:
persistence:
enabled: true
storageClass: null
resources:
limits:
cpu: 200m
memory: 200Mi
requests:
cpu: 100m
memory: 200Mi
metrics:
resources: {}
registry:
deployment:
livenessProbe:
timeoutSeconds: 5
enabled: false
image:
repository: registry.gitlab.com/gitlab-org/build/cng/gitlab-container-registry
ingress:
annotations:
cert-manager.io/cluster-issuer: letsencrypt-issuer-cloudflare
enabled: true
tls:
secretName: registry-tls
resources: {}
storage:
key: config
secret: registry-s3
shared-secrets:
selfsign:
image:
repository: registry.gitlab.com/gitlab-org/build/cng/cfssl-self-signCurrent behavior
Not able to pull gitrepository or start Gitlab pipelines after patch. Error while processing content unencoding: invalid stored block lengths
Expected behavior
Being able to pull gitrepository or start gitlab pipeline.
Versions
- Chart: 7.11.3
- Platform:
- Self-hosted: OpenShift
- Kubernetes: (
kubectl version)- Client Version: v1.30.0
- Server Version: v1.26.13+8f85140
- Helm: (
helm version)- version.BuildInfo{Version:"v3.11", GitCommit:"", GitTreeState:"", GoVersion:"go1.20.1"}
Relevant logs
No relevant logs