The wiki vm's are running fedora 40, so we should move them off that before fedora 40 goes end of life.
The process is roughly:
Alternately, we could look at migrating the wiki into openshift. This may be more work, but longer term make things nicer.
Metadata Update from @james: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
Packages:
Do note that some of those are still maintained in fedora. ;)
Only the ones that are not we need to build ourselves.
Metadata Update from @james: - Issue assigned to james
Problems:
% koji list-tagged f42-infra-stg Build Tag Built by ---------------------------------------- -------------------- ---------------- mediawiki-FedoraBadges-1.0-1.0.20190322git.fc42.2 f42-infra-stg james mediawiki-Lockdown-0-0.4.1.ce3d75b.fc42 f42-infra-stg james mediawiki-OpenIDConnect-8.0.3-2.fc42 f42-infra-stg james mediawiki-OpenIDConnectAPI-0.4-3.fc42 f42-infra-stg james mediawiki-PluggableAuth-7.1.0-1.fc42 f42-infra-stg james mediawiki-RSS-2.25.0-1.fc42 f42-infra-stg james mediawiki-fedoradocsredirect-0.0.3-3.fc42 f42-infra-stg james mediawiki-skin-fedora-0.17-1.fc42 f42-infra-stg james php-jumbojett-OpenID-Connect-PHP-0.9.0-1.fc42 f42-infra-stg james python-koji-fedoramessaging-messages-1.2.5-1.fc42 f42-infra-stg james
I unblocked the packages for f42-infra (they were all orphaned at a higher level AIUI) and did builds:
% koji list-tagged f42-infra-stg Build Tag Built by ---------------------------------------- -------------------- ---------------- mediawiki-FedoraBadges-1.0-1.0.20190322git.fc42.2 f42-infra-stg james mediawiki-Lockdown-0-0.4.1.ce3d75b.fc42 f42-infra-stg james mediawiki-OpenIDConnect-8.0.3-2.fc42 f42-infra-stg james mediawiki-OpenIDConnectAPI-0.4-3.fc42 f42-infra-stg james mediawiki-PluggableAuth-7.1.0-1.fc42 f42-infra-stg james mediawiki-RSS-2.25.0-1.fc42 f42-infra-stg james mediawiki-SpecialInterwiki-0-0.29.20080913svn.fc42 f42-infra-stg james mediawiki-backtick-code-0.0.4-9.fc42 f42-infra-stg james mediawiki-fedoradocsredirect-0.0.3-3.fc42 f42-infra-stg james mediawiki-skin-fedora-0.17-1.fc42 f42-infra-stg james php-jumbojett-OpenID-Connect-PHP-0.9.0-1.fc42 f42-infra-stg james php-rmccue-requests-2.0.6-1.fc42 f42-infra-stg james python-koji-fedoramessaging-messages-1.2.5-1.fc42 f42-infra-stg james
I think this should be all of the packages now.
All packages are currently at: https://koji.fedoraproject.org/repos/f42-infra-stg/latest/x86_64/ ... and they do install.
What do we need to schedule with QE, before staging? Pinging @adamwill anyway.
Some QE results get posted to staging wiki?
How difficult is it to get a random VM so we can try the upgrade on a non-live staging?
we have wiki integration set up on openQA staging, but I've turned all the consumers off at the moment because they kept hitting auth errors and it was annoying me. If you do the upgrade I can turn them back on and see if things work.
It looks to be working, per https://stg.fedoraproject.org/wiki/Special:Contributions/Coconut .
It seems fine now, can do the production upgrade in a few days when we are sure and have scheduled downtime.
A couple of notes:
Even though a fixed tmpwatch is in the infra repo. it still fails new installs on F42 because the infra. isn't available until post install (so don't install it during install).
We had to do the nmcli c up eth0 workaround so the NFS mount came up.
nmcli c up eth0
The Fedora theme was broken by wikimedia upgrades, so we had to workaround it for a bit and then @ryanlerch fixed the Fedora theme.
The staging wiki data is very old compared to prod. ... probably worth sync'ing to a newer version at some point.
Had a minor problem, but after that the upgrade went a lot smoother (thanks to the staging test run).
Metadata Update from @james: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.