Documentation #55855
closedBackport pacific release notes to pacific branch
0%
Description
This is more complicated than it sounds. ceph_confval is present in the main branch and the quincy branch, but not in the pacific branch or the octopus branch.
Because ceph_confval is not present in the pacific branch (and because it cannot under the present circumstances be included in the pacific branch), it is necessary to work around all confval statements in all documents that releases/pacific.rst links to.
This is, in short, a game of whack-a-mole. A very dull game of whack-a-mole.
Updated by Zac Dover almost 2 years ago
Updated by Zac Dover almost 2 years ago
https://github.com/ceph/ceph/pull/46484 - this is an attempt to backport the pacific release notes into the pacific branch.
Updated by Zac Dover almost 2 years ago
This is the state of the console output as of now:
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:988: WARNING: undefined label: cve-2021-3509
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:990: WARNING: undefined label: cve-2021-3531
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:991: WARNING: undefined label: cve-2021-3524
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1110: WARNING: undefined label: cve-2021-20288
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1160: WARNING: undefined label: mgr ceph api
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1208: WARNING: undefined label: bluestore-rocksdb-sharding
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1251: WARNING: undefined label: s3-select-feature-table
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1282: WARNING: undefined label: cephfs-top
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1286: WARNING: undefined label: snap-schedule
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1307: WARNING: undefined label: ceph-dokan
Updated by Zac Dover almost 2 years ago
checking consistency... /home/jenkins-build/build/workspace/ceph-pr-docs/doc/security/index.rst: WARNING: document isn't included in any toctree
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1160: WARNING: undefined label: mgr ceph api
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1251: WARNING: undefined label: s3-select-feature-table
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1282: WARNING: undefined label: cephfs-top
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1286: WARNING: undefined label: snap-schedule
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1307: WARNING: undefined label: ceph-dokan
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/security/index.rst:39: WARNING: undefined label: active-releases
Updated by Zac Dover almost 2 years ago
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1160: WARNING: undefined label: mgr ceph api
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1251: WARNING: undefined label: s3-select-feature-table
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1282: WARNING: undefined label: cephfs-top
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1286: WARNING: undefined label: snap-schedule
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/releases/pacific.rst:1307: WARNING: undefined label: ceph-dokan
/home/jenkins-build/build/workspace/ceph-pr-docs/doc/security/index.rst:39: WARNING: undefined label: active-releases
Updated by Zac Dover almost 2 years ago
"Throttling" in bluestore-config-ref will have to be filled later.
Updated by Zac Dover almost 2 years ago
I had to add ":orphan:" to the top of security/index.rst in order to get the document to suppress a failure due to security/index not being in any toctree. This is absurd, because security/index is in doc/index's toctree. I don't know what's going on here, but whatever it is, it's occult and too obscure to base a documentation workflow on.
Updated by Zac Dover almost 2 years ago
- Status changed from New to Resolved
- Pull request ID set to 46484