Community resources
Community resources
Community resources
Install with Helm chart - Error 404 to reach UI and for health check
Hello,
I'm trying to installa bitbucket instance on my instance.
I'm using helm-chart v 1.17.2 to install a bitbucket data center v 8.16.2.
My pod has a running status but :
- I can't reach UI (error 404)
- Health check is on error :
- Readiness probe failed: HTTP probe failed with statuscode: 404
- Readiness probe failed: Get "http://11.32.30.2:7990/bitbucket/status": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
- Readiness probe warning: Probe terminated redirects, Response body:
I assume to make something wrong but I don't know what.
Looking at pod logs :
Could this WARNS generate the error ?
Last lines of the log without erorr
2024-03-26 12:32:35,067 INFO [spring-startup] c.a.b.i.s.c.j.c.HealthCheckRunner New health check registered: VersionCheck
2024-03-26 12:32:35,067 INFO [spring-startup] c.a.b.i.s.c.j.c.HealthCheckRunner New health check registered: KnownIssueCheck
2024-03-26 12:32:35,131 INFO [spring-startup] c.a.b.i.s.c.c.DefaultClusterJobManager Registering job for StartupChecksJob
2024-03-26 12:32:35,167 INFO [spring-startup] c.a.b.i.s.c.j.c.HealthCheckRunner New health check registered: AuthenticationCheck
2024-03-26 12:32:35,168 INFO [spring-startup] c.a.b.i.s.i.e.DefaultIndexEventQueueProcessor Event queue processor has been started
2024-03-26 12:32:35,209 INFO [spring-startup] c.a.b.i.s.c.j.c.HealthCheckRunner New health check registered: SearchIndexCheck
2024-03-26 12:32:50,146 INFO [Caesium-1-3] c.a.b.i.s.i.jobs.StartupChecksJob Running startup jobs for search
2024-03-26 12:42:34,536 INFO [bcma-3] c.a.b.p.b.a.AnalyticsEventDispatcher Analytics event dispatching job started jobId=e0d62ccb-c199-4a31-835a-e4a4cadf3ca3
2024-03-26 12:42:34,543 INFO [bcma-3] c.a.b.p.b.a.AnalyticsEventDispatcher Analytics event dispatching finished jobId=e0d62ccb-c199-4a31-835a-e4a4cadf3ca3, total time PT0.006504S.
On elasticsearch, all seems ok. For the pod, I can curl my remote elastic instance
bitbucket@bitbucket-0:~/log$ curl http://dev-elastic.xxxx.xxx.xx:9200
{
"name" : "develasticsearch",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "pzlTcndoS5GAlAsLlzDTtQ",
"version" : {
"number" : "7.17.10",
"build_flavor" : "default",
"build_type" : "deb",
"build_hash" : "fecd68e3150eda0c307ab9a9d7557f5d5fd71349",
"build_date" : "2023-04-23T05:33:18.138275597Z",
"build_snapshot" : false,
"lucene_version" : "8.11.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
My helm values file is defined like this
replicaCount: 1
ordinals:
enabled: false
start: 0
image:
repository: atlassian/bitbucket
pullPolicy: IfNotPresent
tag: "8.16.2"
serviceAccount:
create: false
role:
create: false
name: bitbucket
clusterRole:
create: false
roleBinding:
create: false
clusterRoleBinding:
create: false
database:
url: jdbc:postgresql://${postgresHost}:5432/bitbucket
driver: org.postgresql.Driver
credentials:
secretName: bitbucket-database
usernameSecretKey: db_username
passwordSecretKey: db_password
volumes:
localHome:
persistentVolumeClaim:
create: false
customVolume:
persistentVolumeClaim:
claimName: "bitbucket-localhome-pv-claim"
mountPath: "/var/atlassian/application-data/bitbucket"
sharedHome:
persistentVolume:
create: false
additional:
- name: bitbucket-secrets
csi:
driver: secrets-store.csi.k8s.io
readOnly: true
volumeAttributes:
secretProviderClass: bitbucket-secrets
ingress:
create: false
host: bitbucket.${clusterFqdnCdmOnly}
path: /
bitbucket:
useHelmReleaseNameAsContainerName: true
service:
port: 80
sshPort: 7999
type: ClusterIP
contextPath: /bitbucket
annotations: {}
securityContextEnabled: true
securityContext:
fsGroup: 2003
runAsUser: 2003
runAsNonRoot: true
containerSecurityContext:
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
setPermissions: true
additionalVolumeMounts:
- name: bitbucket-secrets
mountPath: /vault
readOnly: true
ports:
http: 7990
ssh: 7999
hazelcast: 5701
license:
secretName: bitbucket-license
secretKey: key
sysadminCredentials:
secretName: bitbucket-system
usernameSecretKey: username
passwordSecretKey: password
displayNameSecretKey: displayName
emailAddressSecretKey: emailAddress
displayName: bitbucket-secops-dev
readinessProbe:
enabled: true
startupProbe:
enabled: true
livenessProbe:
enabled: true
elasticSearch:
baseUrl: http://dev-elastic.xxxx.xxxx.xx:9200
credentials:
secretName: bitbucket-elastic
usernameSecretKey: elastic_user
passwordSecretKey: elastic_pwd
resources:
jvm:
maxHeap: "1g"
minHeap: "512m"
container:
requests:
cpu: "1"
memory: "512Mi"
If anybody has an idea on how to resolve tih situation, it would be so great.
Thanks by advance
Antoine
