You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
:loud_sound: Maintenance scheduled for **NAMED_DAY DD. MM from START_TIME - END_TIME**.
=========================================================================
@all Be aware that you will automatically be logged out and your projects stopped and saved during the maintenance time. Affected:
* [https://staging.osparc.io](https://staging.osparc.io/)
* [https://https://staging.s4l-lite.io/](https://https://staging.s4l-lite.io//)
and on premises:
* [https://osparc-staging.speag.com](https://osparc-staging.speag.com/)
* [https://tip-staging.speag.com](https://tip-staging.speag.com/)
* [https://s4l-staging.speag.com](https://s4l-staging.speag.com/)
* [https://s4l-lite-staging.speag.com](https://s4l-lite-staging.speag.com/)
Reason: Scheduled staging-release of STAGING_NAME_AND_VERSION.
Thanks for your understanding and sorry for the inconveniences,
Your friendly oSparc Team
Releasing
Release (release draft)
Check Release CI
Check hanging sidecars. Helper command to run in director-v2 CLI simcore-service-director-v2 close-and-save-service <uuid>
in dalco migration service successfully claimed that the job is done with the correct alembic version. but in was not migrated in reality when we checked in the DB. We needed to restart the migration service.
New founding: When you re-pull the image and restart the service, it does not take the latest image!
Director v0 had a health check problem therefore it was restarting and was not able to start (assumption: docker-swarm/docker resources problems, after all other services were deployed, the scaling director to 0 and back up helped)
Clusters keeper environment variable CLUSTERS_KEEPER_EC2_SECRET_ACCESS_KEY was wrongly setup in the docker-compose.yml file therefore empty value was propagated (currently it was fixed manually in Portainer, in the next PR it will be fixed in the code)
Cluster keeper could not start because he didn't have enough resources (OPS will have a look into it)
What kind of pre-release?
master branch
Sprint Name
sevenPeaks
Pre-release version
2
Commit SHA
a4d9fec
Did the commit CI suceeded?
Motivation
What Changed
invitations
service requirements #4977 by @pcrespovdynamic-scheduler
service (⚠️ devops) #4973 by @GitHKdynamic-sidecar
receives prometheus metrics networks if defined ⚠️ #4986 by @GitHKdirector-v2
settings refactoring #4993 by @GitHKuser_id
to api server profile #5002 by @bisgaard-itisrespx
library from base requirements listing (fastapi.in
) #5003 by @pcrespovdynamic-sidecar
#5005 by @GitHKserviceName
in the e2e test #5016 by @matusdrobuliak66Devops check⚠️ devops
e2e testing check 🧪
No response
Summary 📝
make release-staging name=sevenPeaks version=2 git_sha=a4d9fecdbc53dc354a5c44fc4a2cb1d82ceab3a9
https://github.com/ITISFoundation/osparc-simcore/releases/new?prerelease=1&target=<commit_sha>&tag=staging_<sprint_name><version>&title=Staging%20<sprint_name><version>
maintenance
in every concerned deployment)Releasing
simcore-service-director-v2 close-and-save-service <uuid>
The text was updated successfully, but these errors were encountered: