Most fallout from last weekend outage have been resolved. If you still experience issues, feel free to (re-)open tickets about said issues.
Thanks for your patience while those issues were worked out.
Please be assured that a postmortem about this major incident will be posted once the summer break is over (next week).
Regards,
Mikaël Barbero
Manager — Release Engineering and Technology | Eclipse Foundation 🐦 @mikbarbero
Hi, Eclipse Foundation staff is on summer break this week and therefore connectivity is limited for some of us, including the IT team. I currently cannot asses which issues are still the aftermath of the outage on Sunday. I will be able to take a look in a few hours.
Obviously the timing of the outage, M2 week and the EF summer break is very unfortunate. We will try to asses and hopefully fix the issues as soon as we can.
Regards, Fred Given that Wayne announced on the committer mailing list last Friday that
FYI, the Eclipse Foundation will be shut down for the entire first week of August (2-6). During this time period, the EMO IP Team will not process CQs and responses to email requests to the EMO, EMO IP Team, and EMO Records teams will be delayed.
I suspect that people are really not reachable even in case of an infrastructure disaster.
I think the best we can do right now is to learn from the post-mortem and implement mitigations afterwards.
Best Sebastian
Christoph , I can only speculate about what's going on but speculation will
get us nowhere. Suffice to say that I am deeply and fundamentally
concerned both by the state of our infrastructure and even more so
by the complete silence from the Foundation. I have tried to reach out yesterday to gain more information, and
to suggest that information be posted to the community, but so far
without success... It would appear to me that we will not be able to get m2
completed today because I'm not sure any of us can do a build and
promote the results right now. Certainly I cannot, at this point,
do any of my usual activities for m2, no new version of Oomph, no
new installers, no product catalog updates...
Regards,
Ed
On 04.08.2021 08:52, Christoph Läubrich
wrote:
>
but I guess there is still a major problem with eclipse.org
infrastructure.
It would be good to have at least some more information, the
status page says 'A fix has been implemented and we are monitoring
the results' but this is two days old and still we see massive
outages, updatesites are broken, CI builds are even not running,
we get bug reports about broken functionality, that's really
annoying and frustrating.
Am 03.08.21 um 18:17 schrieb Andrey Loskutov:
See https://www.eclipsestatus.io/
Some basic website functionality seem to be restored, but
mailing lists / message sending seem to be still broken across
different services.
I received few random (I guess not all) mails from bugzilla, but
I guess there is still a major problem with eclipse.org
infrastructure.
Am 2. August 2021 14:02:03 MESZ schrieb Laurent Goubet
<laurent.goubet@xxxxxxx>:
Hello,
All builds we started this morning (5 hours ago CEST) have
failed with
issues trying to reach download.eclipse.org in one way or
another, two
examples of which are:
- |Caused by: java.io.FileNotFoundException:
https://download.eclipse.org/releases/2019-09/compositeContent.jar|
-|||java.io.FileNotFoundException: Neither
https://download.eclipse.org/tools/orbit/downloads/drops/R20190602212107/repository/compositeContent.jar
nor
https://download.eclipse.org/tools/orbit/downloads/drops/R20190602212107/repository/compositeContent.xml|
When we tried to access these repositories through a browser,
we
initially got a 403 error.
|https://download.eclipse.org/releases/2019-09| now seems to
partially
load (all icons are broken) but
|https://download.eclipse.org/tools/orbit/downloads/drops/R20190602212107/repository
|still gives us a 403.
Could we get any status update on the issue and upcoming fix?
Regards,
--
Kind regards,
Andrey Loskutov
https://www.eclipse.org/user/aloskutov
Спасение утопающих - дело рук самих утопающих
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
|