jfrog / JFrog-Cloud-Installers

Template to deploy Artifactory Enterprise cluster.
Apache License 2.0
78 stars 140 forks source link

Update playbook fails, but after a restart Artifactory is fine #385

Closed bbaassssiiee closed 6 months ago

bbaassssiiee commented 6 months ago

Is this a request for help?:


BUG REPORT

Each time the version of Artifactory changes the upgrade self-test fails. Maybe a timeout?

Which installer: Ansible

Which product and version (eg: ansible & collection version - 7.24.2): 7.84.10

Which operating system and version(eg: ubuntu & version - 20.4): RHEL8

Which product license (Enterprise/Pro): Enterprise

JFrog support reference (if already raised with support team): 299338

What happened: Playbook fails on timeout of

TASK [jfrog.platform.artifactory : Make sure artifactory is up and running] ****
task path: /root/.ansible/collections/ansible_collections/jfrog/platform/roles/artifactory/tasks/upgrade.yml:171
fatal: [salvador-artifactory]: FAILED! => {"attempts": 25, "changed": false, "connection": "close", "content_length": "1617", "content_type": "application/json; charset=utf-8", "date": "Mon, 13 May 2024 18:12:27 GMT", "elapsed": 0, "json": {"router": {"message": "OK", "node_id": "Artifactory-vm", "required_service_types": ["jfrt", "jfac", "jfmd", "jffe", "jfob", "jfcon", "jfevt"], "state": "HEALTHY"}, "services": [{"message": "Service is healthy; there is at least one unhealthy service", "node_id": "Artifactory-vm", "service_id": "jfac@01hvs69ne36x6d0mzj404m1qt4", "state": "UNHEALTHY_PEER"}, {"message": "Service is healthy; there is at least one unhealthy service", "node_id": "Artifactory-vm", "service_id": "jfcon@01hvs69ne36x6d0mzj404m1qt4", "state": "UNHEALTHY_PEER"}, {"message": "Service is healthy; there is at least one unhealthy service", "node_id": "Artifactory-vm", "service_id": "jfevt@01hvs69ne36x6d0mzj404m1qt4", "state": "UNHEALTHY_PEER"}, {"message": "Get \"[http://localhost:8070/readiness\"](http://localhost:8070/readiness/%22): dial tcp 127.0.0.1:8070: connect: connection refused", "node_id": "Artifactory-vm", "service_id": "jffe@01hvs69ne36x6d0mzj404m1qt4", "state": "UNHEALTHY"}, {"message": "Service is healthy; there is at least one unhealthy service", "node_id": "Artifactory-vm", "service_id": "jfmd@01hxsjanjh2bfkq09arjrj32k4", "state": "UNHEALTHY_PEER"}, {"message": "Service is healthy; there is at least one unhealthy service", "node_id": "Artifactory-vm", "service_id": "jfob@01hvs69y0x86nf1r6j1rwb1rrw", "state": "UNHEALTHY_PEER"}, {"message": "Unexpected response status code: 500", "node_id": "Artifactory-vm", "service_id": "jfrt@01hvs69y0x86nf1r6j1rwb1rrw", "state": "UNHEALTHY"}]}, "msg": "Status code was 503 and not [200]: HTTP Error 503: Service Unavailable", "redirected": false, "status": 503, "url": "[http://127.0.0.1:8082/router/api/v1/system/health",](http://127.0.0.1:8082/router/api/v1/system/health%22,) "x_jfrog_node_id": "Artifactory-vm", "x_jfrog_service_id": "jfrou@01hvs69qpb8n6zjtz618rtkvqx"}

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

amithins commented 6 months ago

Hi @bbaassssiiee, Could you please provide the following,

  1. ansible commands that were used to upgrade in your flow
  2. detailed steps to reproduce
  3. logs
  4. upgrading from which version to which version
amithins commented 6 months ago

Looks like you have already provided the details and had a call with support, please continue to engage with them.

bbaassssiiee commented 6 months ago

We have a configuration step in our pipeline. This needs to run after deployment and before update, to install the license. A licence is required for migrations.