The complete docs tree at https://docs.stg.fedoraproject.org/en-US/docs/ ^^^ is no longer being built. They are usually rebuilt every hour. Last happened on 2025-06-26 09:50:14 UTC
The same was true for the docs main public tree at https://docs.fedoraproject.org/en-US/docs/
It works again since yesterday (2025.09.02) about 18:00 UTC
Well, as soon as possible. :-) It blocks working on Fedora Docs for some projects which use staging to discuss and preview new / updated articles.
I assume staging is related to DC move. At least the date seems close.
But the production seems a different issue.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, high-gain, medium-trouble, ops
Yeah, prod was almost certainly a separate problem.
Metadata Update from @kevin: - Issue assigned to kevin
The problem was the docsbuilding project never did a build of the image it uses, so the crons were hitting imagepullbackoff.
I started a build of the image and now the cron builds, but hits:
[17:16:49.959] FATAL (antora): ReadableStream is not defined
The built image used a nodejs version that was too old for antora. I updated the image to use a newer version (and bumped the image to f42 in the process), and now the build is working fine.
Yeah, I saw it was ancient...
Last build doesn't seem to have updated tho. ;( Or it hasn't synced out yet?
The PVC on OpenShift side was incorrect and was mapped to the wrong volume (solr-storage-stg instead of docs-volume). The docs were building properly but just not to the right place.
solr-storage-stg
docs-volume
I fixed the volume, and now everything seems to be up to date on the website. I didn't fix the solr-storage-stg volume, though, so it's currently not used by any project. It's possible that some other applications are not using the right volumes.
It builds now, occasionally correct, occasionally not. You get different results, see #12782
Should be all in sync now. Feel free to reopen if you still see any issues.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)