Daniel Folch

## Update Located the cause of the signing problem, it seems that the GH actions machine does not have tty causing the signing process to fail.

Removing ETA as we're prioritizing other issues.

## Update After reviewing some related issue from different repositories: https://github.com/goreleaser/goreleaser-action/issues/201 https://github.com/robvanderleek/create-issue-branch/issues/338 https://github.com/actions/runner/issues/667 https://github.com/hashicorp/terraform-website/issues/1549 https://github.com/actions/runner/issues/241#issuecomment-556556163 We have found that the cause of the error in signing the commits seems to...

## Update Investigate errors: ### Comment 1 https://github.com/wazuh/wazuh-packages/issues/862#issuecomment-1352119199 Tested command: ``` yum list wazuh-manager.x86_64 --showduplicates ``` in CentOS 7 and verified that it returns the same output as when using...

## Update Fix error in [comment 1](https://github.com/wazuh/wazuh-packages/issues/862#issuecomment-1352119199) and test new `wazuh-install.sh`. Force packages to maintain old `jvm.options` to solve [comment 3](https://github.com/wazuh/wazuh-packages/issues/862#issuecomment-1353093357).

## Update Disable shard allocation before upgrading Wazuh indexer. ``` curl -X PUT "https://:9200/_cluster/settings" -u : -k -H 'Content-Type: application/json' -d' { "persistent": { "cluster.routing.allocation.enable": "primaries" } } ' ```...

## Update We added a second parameter to the `-up` option, now the user needs to introduce the password for the `admin` user of the indexer to upgrade it. commit:...

## Update After discussing with the team we have decided to add a check before upgrading any component. ### Indexer 1. Check if the cluster is green 2. If it...

## Update Test the latest changes with the upgrade check forcing errors.

On Hold due to: https://github.com/wazuh/support/issues/4