Tuesday, 2020-10-20

*** tetsuro has joined #openstack-blazar00:03
*** tetsuro_ has joined #openstack-blazar00:12
*** tetsuro_ has quit IRC00:12
*** tetsuro_ has joined #openstack-blazar00:13
*** tetsuro has quit IRC00:16
*** tetsuro_ has quit IRC00:29
*** tetsuro has joined #openstack-blazar00:29
*** tetsuro has quit IRC00:31
*** masahito has joined #openstack-blazar02:26
*** masahito has quit IRC02:58
*** masahito has joined #openstack-blazar03:19
*** masahito has quit IRC03:21
-openstackstatus- NOTICE: We are investigating an issue with our hosted Gerrit services. We will provide an update as soon as we can. If you want to follow the latest, feel free to join #opendev03:24
*** masahito has joined #openstack-blazar03:56
-openstackstatus- NOTICE: We identified a possible vulnerability in Gerrit and are investigating the potential impact on our services. Out of an abundance of caution we have taken our OpenDev hosted Gerrit system offline. We will update with more information once we are able.04:29
*** masahito has quit IRC06:10
*** masahito has joined #openstack-blazar06:12
*** masahito has quit IRC07:03
-openstackstatus- NOTICE: We identified a possible vulnerability in Gerrit and are investigating the potential impact on our services. Out of an abundance of caution we have taken our OpenDev hosted Gerrit system offline. We will update with more information once we are able.08:35
*** ChanServ changes topic to "We identified a possible vulnerability in Gerrit and are investigating the potential impact on our services. Out of an abundance of caution we have taken our OpenDev hosted Gerrit system offline. We will update with more information once we are able."08:35
*** priteau has joined #openstack-blazar08:45
-openstackstatus- NOTICE: Update on gerrit downtime: After investigation, we believe the incident is related to a compromised Gerrit user account rather than a vulnerability in Gerrit software. We are continuing to review activity to verify the integrity of git data and expect to have an additional update with possible service restoration in approximately 2 hours.11:03
*** ChanServ changes topic to "Update on gerrit downtime: After investigation, we believe the incident is related to a compromised Gerrit user account rather than a vulnerability in Gerrit software. We are continuing to review activity to verify the integrity of git data and expect to have an additional update with possible service restoration in approximately 2 hours."11:03
-openstackstatus- NOTICE: We've confirmed that known compromised identities have been reset or had their accounts disabled, and we are auditing other service accounts for signs of compromise before we prepare to restore Gerrit to working order. We will update again in roughly 2 hours.13:32
*** ChanServ changes topic to "We've confirmed that known compromised identities have been reset or had their accounts disabled, and we are auditing other service accounts for signs of compromise before we prepare to restore Gerrit to working order. We will update again in roughly 2 hours."13:32
-openstackstatus- NOTICE: Auditing is progressing but not particularly quickly. We'll keep updating every 2 hours or so.15:39
*** ChanServ changes topic to "Auditing is progressing but not particularly quickly. We'll keep updating every 2 hours or so."15:39
*** masahito has joined #openstack-blazar16:55
*** masahito has quit IRC17:00
*** langdon has quit IRC17:49
-openstackstatus- NOTICE: Gerrit is offline due to a security compromise. Please refer to https://review.opendev.org/maintenance.html or #opendev for the latest updates.17:59
*** ChanServ changes topic to "Gerrit is offline due to a security compromise. Please refer to https://review.opendev.org/maintenance.html or #opendev for the latest updates."17:59
*** priteau has quit IRC19:16
*** masahito has joined #openstack-blazar20:23
*** masahito has quit IRC20:28
*** langdon has joined #openstack-blazar22:00

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!