The pkgs01.stg system has been used for a lot of little projects in the past year which has made it diverge from production in multiple ways. Normally, we would regularly reinstall pkgs01.stg and then import source code from the production system. This would mean all work on pkgs01.stg would be lost but the systems in staging are not meant for long term differences so it would not be a problem. However because we do not have a true development environment for teams in modularity or similar to work on I think this might cause some team problems.
I have opened https://pagure.io/fedora-infrastructure/issue/8503 and would like any team which will be affected to let me know. If I don't hear anything I will go ahead with the repave next week.
On Tue, Jan 07, 2020 at 09:02:31AM -0500, Stephen John Smoogen wrote:
The pkgs01.stg system has been used for a lot of little projects in the past year which has made it diverge from production in multiple ways. Normally, we would regularly reinstall pkgs01.stg and then import source code from the production system. This would mean all work on pkgs01.stg would be lost but the systems in staging are not meant for long term differences so it would not be a problem. However because we do not have a true development environment for teams in modularity or similar to work on I think this might cause some team problems.
I have opened https://pagure.io/fedora-infrastructure/issue/8503 and would like any team which will be affected to let me know. If I don't hear anything I will go ahead with the repave next week.
While this is likely going to impact the stg outage some more, it may be a good idea to couple this with a koji db sync from prod to stg.
Pierre
infrastructure@lists.fedoraproject.org