staging: Upgrade postgresql server

changed the description

We should consider migrating the postgresql server to kubernetes (like we currently do with the next-version environment).

The current staging db server is managed through puppet so it's currently diverged from the production one anyway (manual management).

pros:

cloudnative operator is managing the db (& it's already swh-charted)
we learn to use the cloudnative operator

cons:

(as mentioned iso with current situation) divergence from the production deployment

changed the description

We start having errors due to no longer supported version (see check-version init container for the webapps in staging) [2]

Only the webapp is victim of this.

And this is not really a critical db, so this may be the occasion to move only that one to kubernetes.

I've done that and now the webapp pods in staging are running again. So win.

I'll keep the issue open though. We do need to upgrade this database server to a most recent one.

mentioned in commit swh/infra/ci-cd/swh-charts@797b30b7

mentioned in commit swh/infra/ci-cd/swh-charts@c2c2677e

mentioned in commit swh/infra/ci-cd/swh-charts@f2fc6525

mentioned in commit swh/infra/ci-cd/swh-charts@238e2fdf

mentioned in commit swh/infra/ci-cd/swh-charts@ca9d1212

mentioned in commit swh/infra/ci-cd/swh-charts@bd18b83b

mentioned in commit swh/infra/ci-cd/swh-charts@616f5f23

mentioned in commit swh/infra/ci-cd/swh-charts@eeb2e9a6

mentioned in commit swh/infra/ci-cd/swh-charts@582d7e15

Following the email received on sysadm ml [1]. I reproduced the issue easily enough [2].

And it reminded me that the deposit displayed the same error as the staging webapp (fail to start because of the pg 12 db) and I had forgotten I wanted to fix it.

So I went and migrated the db to kubenertes too. That fixed the bevahior simply enough for the webapp early on.

[1] [swh-sysadm] Fwd: Software Heritage - deposit staging returns 500 Internal Server Error

[2]

tony@kessel:~ (staging) $ curl -u $creds https://deposit.staging.swh.network/1/servicedocument/; echo

<!doctype html>
<html lang="en">
<head>
  <title>Server Error (500)</title>
</head>
<body>
  <h1>Server Error (500)</h1><p></p>
</body>
</html>

[3]

tony@kessel:~/work/swh/sysadm-environment/swh-charts (staging) $ curl -u $creds https://deposit.staging.swh.network/1/servicedocument/; echo
<?xml version="1.0" ?>
<service xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:sword="http://purl.org/net/sword/terms/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns="http://www.w3.org/2007/app">

    <sword:version>2.0</sword:version>
    <sword:maxUploadSize>209715200</sword:maxUploadSize>

    <workspace>
        <atom:title>The Software Heritage (SWH) Archive</atom:title>
        <collection href="https://deposit.staging.swh.network/1/swh/">
            <atom:title>swh Software Collection</atom:title>
            <accept>application/zip</accept>
            <accept>application/x-tar</accept>
            <sword:collectionPolicy>Collection Policy</sword:collectionPolicy>
            <dcterms:abstract>Software Heritage Archive</dcterms:abstract>
            <sword:treatment>Collect, Preserve, Share</sword:treatment>
            <sword:mediation>false</sword:mediation>
            <sword:metadataRelevantHeader>false</sword:metadataRelevantHeader>
            <sword:acceptPackaging>http://purl.org/net/sword/package/SimpleZip</sword:acceptPackaging>
            <sword:service>https://deposit.staging.swh.network/1/swh/</sword:service>
            <sword:name>swh</sword:name>
        </collection>
    </workspace>
</service>

FTR the issue is due to the upgrade of django from 5.0.8 to 5.1 in version swh-deposit-20240812.1

https://docs.djangoproject.com/en/5.1/releases/5.1/#dropped-support-for-postgresql-12

staging: Upgrade postgresql server

Designs

Child items ...

Activity