Yevhen Atlassian Team

You can curl jsm in a custom Jira Software Dockerfile and do smth like: RUN unzip /opt/jira-servicedesk-application-${JSM_VERSION}.obr -d /opt/jsm \ && ls /opt/jsm/dependencies/*.jar 1> /dev/null 2>&1 \ && mkdir -p ${JIRA_HOME}/plugins/installed-plugins/ \ && cp /opt/jsm/dependencies/*.jar…

Hi @Baran BÜYÜK Can you please elaborate on what exactly you're doing and what exactly fails for you?

@Venkata Kola I think you can use this guide https://confluence.atlassian.com/enterprise/infrastructure-recommendations-for-enterprise-jira-instances-on-aws-969532459.html#InfrastructurerecommendationsforenterpriseJirainstancesonAWS-Summaryofrecommendations

@James Dutton In case of an on prem OpenShift or Kube cluster you just need to make sure that the images used in DC Helm charts are available either from DockerHub or you pull, tag and push them to a private registry of choice. Other than that there should be no issues with the installation as such in air gapped envs.

Hey Michael! Do I get it right? You scaled sts to 0, deleted lock file, scaled to 1 then to 2 and the issue persists? Can both replicas use a shared volume for example? /var/atlassian/application-data/ is a local home which is persisted individually for each statefulset replica. Perhaps the two pods share it somehow?

Hi @Michael Cromer Did you check https://confluence.atlassian.com/confkb/unable-to-start-confluence-or-enable-the-usage-stats-plugin-due-to-cannot-forcefully-unlock-a-nativefslock-error-688884516.html? Looks like exactly the error you see. Permissions issues?

Interesting... I guess it depends on the K8s flavor and cloud. Say, in OpenShift I was able to set timezone on a pod level by adding a TZ env var to container env. Node time zone was indeed ignored.

I am in no way an expert in Jira but I guess if I had to solve such a problem with Nginx ingress controller I'd: * create a new service which uses a unique label (pods in the statefulset will have it) * add another path to your spec.rules.http.paths and use your new service as a backend Also there's a general requirement…

@Santhosh Reddy Singireddy you can find available DC products here https://github.com/atlassian/data-center-helm-charts/tree/main/src/main/charts As to official support, AFAIK it's Jira, Bitbucket and Confluence for sure. You'll need to reach out to support with this question as I don't want to misinform you.

@apulikkal I am sorry, I am not familiar with the framework you use. If during a test phase it needs access to K8s API...it needs it for some reason. I can only recommend using an external k8s cluster of course if you have a public one. 

@apulikkal correct, a test container that a test wants to create using K8s API. This isn't supported in pipelines for obvious reasons. I'm just explaining what happens and why it works locally for you.

@Alexander Tchaikovski I am afraid I can't suggest anything new - it's either disc space and/or permissions. Doesn't look like a k8s specific issue - just a general issue.

@apulikkal the client fails to connect to a K8s cluster and falls back to localhost:8080. I do not think you are allowed to use incluster auth in pipelines otherwise you'd get access to the actual cluster where your job pod is running. You can configure which cluster to connect to:…

Perhaps the first time you migrated cluster properties which don't work in Kube. It's just my assumption as I don't have all the data to leap to a data-proven conclusion.

@Alexander Tchaikovski it looks like K8s Hazelcast discovery does not happen. Is clustering turned on in values.yaml? Also, is this a new installation or you migrated an existing Confluence to Kube? Perhaps, there are leftovers of properties from a previous installation?

I'd say you need to backup your shared home and the database. Once done, restore it to a new database and a new shared home in your Kube cluster.

@yosser.mahfoudh I was more thinking about a new step. So your steps in the pipeline would differ by one command only. Also, I'd recommend looking at an official K8s documentation and play with kubectl and your pod yaml in the command line to better understand kubectl and cluster behavior.

@yosser.mahfoudh yes, this is what delete command is expected to do. In the next step you can apply again (I'd recommend adding a 10-15 second sleep to give apiserver time to delete the pod).

It's will delete whatever is in metadata.name in your yaml.

Yes. Perhaps, to delete the pod you don't need to run any sed against yaml. It'll be deleted as long as a pod with such a name exists in the namespace (its spec does not really matter)

That would be "kubectl delete pod $podName -n $namespace" if you're using kubectl.

@yosser.mahfoudh you will have to explicitly delete it.

@yosser.mahfoudh you can't create a new pod with the same name and you can't change name of the existing pod too since name and namespace fields are immutable. Some of the fields can be changed though.

Hmmm... you must have hit a known issue with Synchrony. Can you please try this workaround?

@Alexander Tchaikovski in your values.yaml do you have `confluence.clustering.enabled: true`? I don't see anything Hazelcast related in the logs. For example, my logs have this: 2022-04-27 06:16:58,725 INFO [hz.confluence.event-1] [confluence.cluster.hazelcast.LoggingClusterMembershipListener] memberAdded [10.6.21.43]:5701…

@Alexander Tchaikovski can you please elaborate on "how to point it to the first one"? Confluence uses Hazelcast K8s discovery and when you scale up and the 2nd pod starts without errors and passes a health check, things should happen automatically for you and a new member should join the Hazelcast cluster. Sharing logs of…

@Alberto Aragón you don't need to worry about cluster.properties. When Jira container starts an entrypoint script is executed and among other things it grabs pod IP address and writes it to cluster.properties. This way, you can add Jira nodes by scaling jira statefulset.

@asd asd though it's not officially supported I don't see why you can't deploy remote Bamboo agents to ECS. Technically, it should be like running a remote agent on a Docker host. If you want to launch agents on demand and shut them down, you'll need to write own plugin/automation for that. If you want to have remote…

@yosser.mahfoudh that would be base64 encoded kubeconfig yaml that you'd typically use when interacting with a K8s cluster using kubectl or other clients.

@kube130 it's up to a k8s admin to choose log aggregators. Fluentd sidecar is shipped with Jira Helm chart as an option. You may or may not use it. There's no golden standard in log management and we certainly can't support them all.