Staging Koji should be synced with production. The last sync was done 4 months ago (Wed, 31 Oct 2018). Besides the usual problems (most importantly, builds garbage-collected from production volume), f31 tags are missing.
I remind that any configuration which is specific to staging Koji (i.e. that is not in production Koji) and which should be preserved during the sync must be in ansible.git. If not, it will be lost during the sync.
I can do the sync. Proposed date and time: Fri, 08 Mar 2019 05:00 AM UTC. If anyone has any objections to this date/time or to the sync in general, please comment here.
+1 - bodhi in staging always gets weirder and weirder the longer they get out of sync ☺
+1 from me. The more often the better. ;)
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Update: I've been working on the sync on Friday, but the sync failed, leaving staging Koji in non-working state. I didn't have enough time reserved to resolve the issues and complete the sync on Friday, but I am planning to continue the work tomorrow morning.
This is done I think? At least the hub is up and responding fine...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
The sync is mostly done, but I kept this issue open because there was a problem with NFS on s390x builder.
Ah, well, I don't think we ever had nfs on the s390x staging host. As long as we don't do runroot or newrepos on it, that should be fine.
if we do need to do those things, it likely will need a RHIT ticket to open nfs ports.
Login to comment on this ticket.