Description
Related Objects
Event Timeline
@akosiaris since you took care of T89640: TransparencyReport repository master in Gerrit silently made private, do you have any idea why this could be happening?
Also, would it be possible to move https://transparency.wikimedia.org/private to https://private.transparency.wikimedia.org/. Happy to raise a separate task for this if you need :)
Separate tasks for separate issues, That being said, there are issues with double subdomains for our certificates so ops will probably suggest something like transparency-private.wm
It's updating fine from what I see. Both https://gerrit.wikimedia.org/r/#/admin/projects/wikimedia/TransparencyReport-private and the repo on the server are at
commit 12f441fca87ea5ec590aef1befb10b40db5b7497
Author: Siddharth11 <siddharth2parmar@gmail.com>
Date: Wed Feb 21 11:17:38 2018 +0530
Add a new row in requests breakdown table
Change-Id: If1b977a6ca7eeb61b1afd06a9fb81458afc9c4acso the update process works just fine. Not only that, but https://transparency.wikimedia.org/private/privacy.html does indeed show the extra added entry.
Yes, please separate task.
Thanks, everyone! We spoke with @Catrope last week, and he was able to get it working again. Is there any way to determine why it happened / make sure it doesn't happen again?
Yes, please separate task.
T188362: Move "transparency.wikimedia.org/private" to "transparency-private.wikimedia.org"
If @Catrope fixed it (whatever it was), he is definitely the best person to answer that question. I am gonna close this as invalid. Feel free to reopen/add more information. Thanks!
The reason was that puppet was disabled on the instance, so puppet didn't run and therefore didn't clone.
The reason it was disabled was that we had to once do a content revert for another microsite for research and then i forgot to re-enable it later when it was possible.
The fix was that he asked on IRC and joe saw it and re-enabled puppet runs again.
The "prevent it from happening" again part is that i will try to not forget it again and always set a reason when disabling puppet. ;)
Thanks @Dzahn! We were pretty confused about what happened, so we're glad to have it explained.