Closed matusdrobuliak66 closed 1 year ago
The deployment agent on aws-prod is paused since there were faulty env-vars for the invitations service. The env-vars have been adjusted manually in portainer
We tried to put the fix in here, please double check upon releasing that especially the INVITATION_PASSWORD
is correctly set on the service's env-vars, and not truncated after the dollar sign
The deployment agent is paused, the faulty variable of AUTOSCALING_EC2_INSTANCES_PRE_PULL_IMAGES
on the autoscaling service was corrected and is now set to
["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]
I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.
The deployment agent is paused, the faulty variable of `` on the autoscaling service was corrected and is now set to
["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]
I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.
@mrnicegyu11 Maybe we should just remove those ops ones. the images are not so big I think so that should not make a huge difference.
The deployment agent is paused, the faulty variable of `` on the autoscaling service was corrected and is now set to
["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]
I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.
@mrnicegyu11 Maybe we should just remove those ops ones. the images are not so big I think so that should not make a huge difference.
Sounds good I will put this in place on aws-prod now, we can then see how it looks/feels.
New env-var is: ["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]
The deployment agent is paused, the faulty variable of `` on the autoscaling service was corrected and is now set to
["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]
I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.
@mrnicegyu11 Maybe we should just remove those ops ones. the images are not so big I think so that should not make a huge difference.
Sounds good I will put this in place on aws-prod now, we can then see how it looks/feels.
New env-var is:
["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]
Please restart the following ops-services and thus roll out the latest ops-code from osparc-ops-environments
on prod:
on aws-prod
, dalco-prod
and tip.itis.swiss
.
Grafana and Graylog Alerts need to be re-provisioned.
In order for the grafana dashboard to work, the old proper hostnames (instance
prometheus labels) need to be restored. Potentially a full teardown and recreation of the swarm is necessary for this.
See: https://github.com/ITISFoundation/osparc-ops-environments/pull/182
Please include this commit as hotfix
Invitations:
Release version
1.55.0
Commit SHA
48d29cda9cb81c570fbd329ec560eb0c2167321a
Previous pre-release
https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_Watermelon2
Did the commit CI suceeded?
Motivation
n/a
Changes
Release Issue: https://github.com/ITISFoundation/osparc-simcore/issues/4397
No response
Devops check π·
Tests assessment: e2e testing check π§ͺ
No response
Test assessment: targeted-testing ποΈ
No response
Test assessment: user-testing π§
No response
Summary π
{"start": "2023-06-23T07:00:00.000Z", "end": "2023-06-23T08:15:00.000Z", "reason": "Release v1.55.0"}
Releasing π
simcore-service-director-v2 close-and-save-service <uuid>
https://testing.osparc.speag.com/