Open Bug 1414278 Opened 4 years ago Updated 10 months ago

Scripts can't update wiki.m.o anymore: The intoken parameter has been deprecated

Categories

(Release Engineering :: Release Automation: Other, defect, P2)

defect

Tracking

(Not tracked)

People

(Reporter: u504868, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [releaseduty])

Attachments

(1 file)

Attached file wiki_failure.html
Steps to reproduce
1. Either, run end_to_end_reconfig.sh[1] with the wiki option. This should perform a buildbot reconfig
2. Or, run update_merge_day_wiki.sh[2]

Results:

> ERROR: Could not retrieve edit token
>    Ran: curl -b '/tmp/cookie-jar.7e79riJa4M' -s -d action=query -d prop=info -d intoken=edit -d titles=Template:NextReleaseDate 'https://wiki.mozilla.org/api.php'
>    Output retrieved:
> **See attachment**


I don't think scenario 1 is a high priority because BB will eventually go away. We're still able to run end_to_end_reconfig.sh without any wiki update.

Scenario 2 is less convenient. But still, we can update the wiki pages by hand.

[1] https://dxr.mozilla.org/build-central/source/tools/buildfarm/maintenance/end_to_end_reconfig.sh
[2] https://dxr.mozilla.org/build-central/source/tools/buildfarm/maintenance/update_merge_day_wiki.sh
Couldn't update wiki as part of mergeduty for 59.0. I think multiple things are broken. If we care about this, we should take it along in the fixes we're doing in bug 1432655.
Blocks: 1432655
Priority: -- → P2
Duplicate of this bug: 1083332
:jcristau noticed [1] hasn't been updated since we shipped 61. I just changed the value to match the upcomfing 62 release.

[1] https://wiki.mozilla.org/Template:NextReleaseDate
Daniel Hartnell was kind to offer support one release cycle ago but that slipped off my radar. Might be worth investing some time in fixing the scripts so that we can automate this step as part of mergeduty.

:danielh - are you still available to start a conversation here in order to eventually fix these scripts on our side? This is not high priority but would be nice to get done within 62.0 or 63.0 releases.
Flags: needinfo?(dhartnell)
To clarify, what we'd want is more details on what changed under the hood; then we can adjust the scripts to ideally fix this and go back to automation. manual work is hard :)
Hey Mihai!

Sorry, just saw this request. I'll have a chance to respond tomorrow with additional details I might be forgetting. In short, I think our upgrade to MediaWiki 1.27 resulted in a change to the login action which seems to have impacted some people.

https://www.mediawiki.org/wiki/API:Login#The_login_action

More information about the current version can be seen here:

https://wiki.mozilla.org/Special:Version
Flags: needinfo?(dhartnell)
(In reply to Daniel Hartnell [:danielh] from comment #6)
> Hey Mihai!
> 
> Sorry, just saw this request. I'll have a chance to respond tomorrow with
> additional details I might be forgetting. In short, I think our upgrade to
> MediaWiki 1.27 resulted in a change to the login action which seems to have
> impacted some people.
> 
> https://www.mediawiki.org/wiki/API:Login#The_login_action
> 
> More information about the current version can be seen here:
> 
> https://wiki.mozilla.org/Special:Version

No worries! Sounds good. I'll have a look at that mediawiki update to see what happened in the scripts.
For some reason this entirely dropped from my radar, sorry about it.
Coming back to the pool of [releaseduty].
Blocks: 1666321

I wonder if the maintainer of wiki.m.o could run a cron job that reads a json file somewhere. That json file could have all the versions specified.
(Or, even easier for us, we could point them to the various version files in-tree, and have them poll a URL for each variable.)

You need to log in before you can comment on or make changes to this bug.