<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Here is the latest update from the opendev infrastructure team on
the gerrit outage.</p>
<p> <a moz-do-not-send="true" href="http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html">http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html</a></p>
<p>In short</p>
<p>- The gerrit service was taken offline for a time, but has since
been restored.</p>
<p>- They ask that you review the <a moz-do-not-send="true" href="https://login.launchpad.net/activity">activity logs</a> on
your account. Check for access times or originating ip addresses
that look wrong. <br>
</p>
<p>- They ask that you re-review the diffs for commits submitted
since October first. They have collected the diffs at <a moz-do-not-send="true" href="https://static.opendev.org/project/opendev.org/gerrit-diffs/">https://static.opendev.org/project/opendev.org/gerrit-diffs/</a>
. They are organized by repo and branch. If you have submitted
code, or you are a core reviewer that has approved a code merge,
please take the time to re-review the submission. Do you remember
approving the submission? Has the submission been tampered with.
If you are a code submitter and still have access to your local
working git, perhaps generate your own diffs and compare it to the
upstream diffs. <br>
</p>
<p>- Users (if any) of the Gerrit HTTP API will find that there old
passwords have been purged. You'll need to set a new password to
regain access.</p>
<p>I think Bill has volunteered to set up some way to track that all
the gits have been re-reviewed.</p>
<p><br>
</p>
<p>Scott Little<br>
</p>
</body>
</html>