openshift application container versions
I whipped up a brute force little script and ran it on our staging openshift 4 cluster. It just gets all running pods and does oc rsh into each and looks at /etc/os-release. For a few of these that aren't running yet in stg, I looked at prod (like toddlers). Here's the results and some comments in between. I can work on upgrading some of these, but would be nice if application owners update their own applications. ;) asknot "platform:f34" blockerbugs "platform:el8" bodhi "platform:f36" "platform:f36" "platform:f36" "platform:f36" bugzilla2fedmsg "platform:el8" community-metrics compose-tracker "platform:f36" coreos-cincinnati "platform:f35" datagrepper "platform:el8" datanommer "platform:el8" discourse2fedmsg "platform:el8" docsbuilding "platform:f34" ^ This should get updated. docstranslation ^ No running pods, but cronjobs use f34. Should be updated elections "platform:el8" fasjson "platform:f35" fedocal "platform:el8" fedora-packages-static ^ debian 11 in the solr pod ^ fedora 34 in the static pod, should get updated flask-oidc-dev "platform:el8" flatpak-indexer "platform:el8" "platform:el8" "platform:f36" greenwave "platform:f33" "platform:f33" "platform:f33" ^ Needs update. ipsilon-website ^ Alpine Linux v3.16 (is this current? no idea) koschei "platform:f35" "platform:f35" "platform:f35" "platform:f35" "platform:f35" "platform:f35" languages "platform:el8" mdapi "platform:f31" "platform:f31" ^ Definitely needs update. message-tagging-service "platform:f29" ^ Definitely needs update. messaging-bridges "platform:el8" "platform:el8" "platform:el8" monitor-gating "platform:f31" ^ Definitely needs update. mote "platform:f36" "platform:f36" "platform:el9" noggin "platform:el8" noggin-centos "platform:el8" oraculum "platform:el8" "platform:el8" "platform:el8" "platform:el8" "platform:el8" release-monitoring "platform:f36" "platform:f36" "platform:f36" resultsdb "platform:f35" "platform:f35" resultsdb-ci-listener "platform:f36" review-stats ^ just cronjobs, fedora:36 silverblue PRETTY_NAME="Fedora 27 (Twenty Seven)" ^ very much needs updating. testdays "platform:el8" "platform:el8" the-new-hotness "platform:f36" toddlers PRETTY_NAME="Alpine Linux v3.16" ^ is this current? transtats "platform:f34" "platform:f34" ^ needs updating. waiverdb "platform:f34" "platform:f34" ^ needs updating. websites ^ cron jobs, fedora:34. Needs updating. zezere "platform:el8" signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
> However, fas is still there, so when we take down the cluster, badges > will break. Ideally we would fix that before we take down the old > cluster, but I don't want to leave it running there too long. > I'll check if there's an easyfix for badges' reliance on FAS. It may not be that much work. (famous last words) A. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
On Mon, Jun 27, 2022 at 10:19:51AM +0200, Michal Konecny wrote: > Is the automatic deployment from GitHub by webhook still an issue or was > this solved? You mean https://pagure.io/fedora-infrastructure/issue/10603 ? Not yet, but I will try and do that this week... kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openshift 3->4 moves status and info needed
Is the automatic deployment from GitHub by webhook still an issue or was this solved? Michal On 24. 06. 22 23:19, Kevin Fenzi wrote: On Thu, Jun 23, 2022 at 05:45:49PM -0700, Kevin Fenzi wrote: ok. So we are down to: elections - moved in stg, but it crashes there. Bcotton was going to look, but he's dealing with a family emergency. Is anyone else able to take a look at it? It looks like it just doesn't start processing fast enough and openshift kills it. This was a port issue, got it fixed on the openshift side and it's moved now. fedocal - moved in stg, but authentication isn't working. It says that the 'redirect_uri' is invalid, but I cannot for the life of me see where. It looks right in config, it looks right on ipsilon. The prod one on openshift 3 looks the same. ;( Abompard: might you be able to take a look? Got this sorted with the help of Patrick and Darknao. Turns out the default in openshift 4 is for routers to 'append' the hostname on to proxy headers. Since the cluster is behind our already existing layer of proxies, it was re-writing the header to be application.fedoraproject.org.application.fedoraproject.org. Changing that to having it leave the forwarded header alone got it all working. fedocal is moved in prod and stg. koschei - mizdebsk was going to move this, but I might just try and do so tomorrow. I would think it would be pretty easy. mizdebsk went and did this this morning. koschei is all moved. So... thats it. All the things I know we want to keep are off the cluster. However, fas is still there, so when we take down the cluster, badges will break. Ideally we would fix that before we take down the old cluster, but I don't want to leave it running there too long. Thanks to everyone who helped get this done! Next step on openshift is some best practices, and look for an email from me listing what os versions we are using for each app (spoiler, we have a bunch of out of date ones). kevin ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
