Page MenuHomePhabricator

TransparencyReport-private is not auto deploying
Closed, ResolvedPublic

Description

From @siddharth11's email

Yeah, I just checked, the changes aren't live. It seems the deployment process has changed. Previously, any change pushed to TransparencyReport-private repository used to auto-deploy after an hour.

Gerrit repo: https://gerrit.wikimedia.org/r/#/admin/projects/wikimedia/TransparencyReport-private
Website: https://transparency.wikimedia.org/private

Event Timeline

Prtksxna created this task.Feb 26 2018, 3:40 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 26 2018, 3:40 AM

@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 :)

Peachey88 added a subscriber: Peachey88.

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

akosiaris triaged this task as Medium priority.Feb 26 2018, 12:30 PM

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: If1b977a6ca7eeb61b1afd06a9fb81458afc9c4ac

so the update process works just fine. Not only that, but https://transparency.wikimedia.org/private/privacy.html does indeed show the extra added entry.

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

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?

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

Yes, please separate task.

T188362: Move "transparency.wikimedia.org/private" to "transparency-private.wikimedia.org"

akosiaris closed this task as Invalid.Feb 27 2018, 11:04 AM

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?

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!

Dzahn added a subscriber: Dzahn.Feb 27 2018, 10:21 PM

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. ;)

Dzahn changed the task status from Invalid to Resolved.Feb 27 2018, 10:22 PM

Thanks @Dzahn! We were pretty confused about what happened, so we're glad to have it explained.