-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tinkerers-ci test suites are failing due to observability-platform #3827
Comments
After updating the observabiliy secrets on Currently, there are 2 remaining issues on the MC :
|
So @giantswarm/team-rocket added an additional worker node today, which lead to some pods to schedule but unfortunately, most of the By trying to release some of the memory by lowering memory requests on |
@QuentinBisson did some additional investigations and found out that As a temporary hot fix, Quentin created a PR to allow |
This workaround is sadly not accepted by the majority of team atlas |
Herve said he was ok (even though releuctant) in today's standup :) |
@AverageMarcus the observability platform is running on grouse, closing for now, let's reopen if we still have issues |
The Tinkerers-ci test suites are failing on CAPV and CAPVCD due to the observability-platform, most likely due to the object storage issues we are facing right now with the recent migration of all CAPV and CAPVCD buckets CRs from
glippy
togaggle
.After the migration, the object-storage-operator is struggling to work correctly on
gaggle
so solving this would most likely help, if not solve, the tinkerers-ci issue as well.See the related incident for more details : https://gigantic.slack.com/archives/C087RGMRPDZ
The text was updated successfully, but these errors were encountered: