From ebe7a5809ab5afe63da26db7596b0c1fe6f6b4d4 Mon Sep 17 00:00:00 2001 From: Minae Lee Date: Mon, 2 Feb 2026 09:47:41 -0700 Subject: [PATCH 1/3] doc: linkcheck ignore sourceforge.io Ignore sourceforge.io links in linkcheck due to rate limiting causing failures. Signed-off-by: Minae Lee (cherry picked from commit ddbc819cf6f9ac07d4b5b71a0448ccaca7b14b6e) --- doc/custom_conf.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/custom_conf.py b/doc/custom_conf.py index 3b43a9244..8d6307bf2 100644 --- a/doc/custom_conf.py +++ b/doc/custom_conf.py @@ -165,7 +165,7 @@ # These links may fail from time to time 'https://ceph.io', # Cloudflare protection on SourceForge domains often block linkcheck - r"https://.*\.sourceforge\.net/.*", + r"https://.*\.sourceforge\.(net|io)/.*", ] # Pages on which to ignore anchors From 9c74a1f41ac05e377f99a67467e2be13bd58067c Mon Sep 17 00:00:00 2001 From: Minae Lee Date: Mon, 2 Feb 2026 10:31:52 -0700 Subject: [PATCH 2/3] doc: set GOTOOLCHAIN=auto for RTD Go builds Update .readthedocs.yaml to set GOTOOLCHAIN=auto when building the lxd integration and make doc-html-rtd. This fixes RTD build issues by allowing Go to auto-fetch the required Go patch version when the local toolchain is outdated. Signed-off-by: Minae Lee (cherry picked from commit 7d87d3089d965bfc351f4cfb9ab7f690612a1872) --- doc/.readthedocs.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/.readthedocs.yaml b/doc/.readthedocs.yaml index 4e8f7690f..3df760f20 100644 --- a/doc/.readthedocs.yaml +++ b/doc/.readthedocs.yaml @@ -13,14 +13,14 @@ build: python: "3.12" commands: - git fetch --unshallow || true - - cd doc && make integrate - - cd doc/integration/lxd/ && go build -ldflags "-s -w" -o trimpath -o lxc.bin ./lxc + - cd doc && make GOTOOLCHAIN=auto integrate + - cd doc/integration/lxd/ && GOTOOLCHAIN=auto go build -ldflags "-s -w" -o trimpath -o lxc.bin ./lxc # Pretend that woke is installed - we don't need it for building # (workaround until https://github.com/canonical/microovn/pull/168 is merged # and https://github.com/canonical/microceph/pull/400 is restored) - ln -s /bin/true doc/integration/microovn/docs/woke - ln -s /bin/true doc/integration/microceph/docs/woke - - make doc-html-rtd PATH=$PATH:. + - make GOTOOLCHAIN=auto doc-html-rtd PATH=$PATH:. # Build documentation in the docs/ directory with Sphinx sphinx: From 4f0b3473d88fae02a760b1afe0cba0ff11d6918c Mon Sep 17 00:00:00 2001 From: Minae Lee Date: Mon, 2 Feb 2026 14:58:29 -0700 Subject: [PATCH 3/3] doc: fix broken ubuntu server link Signed-off-by: Minae Lee (cherry picked from commit cc0d61322152ec6f9c6fe19a16df4fcf9dc6c207) --- doc/tutorial/multi-member.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tutorial/multi-member.md b/doc/tutorial/multi-member.md index 4e95da16c..9a7442703 100644 --- a/doc/tutorial/multi-member.md +++ b/doc/tutorial/multi-member.md @@ -4,7 +4,7 @@ This tutorial guides you through installing and initializing MicroCloud in a confined environment, including storage and networking. You'll then start some instances to see what you can do with MicroCloud. This tutorial uses LXD virtual machines (VMs) for the MicroCloud cluster members, so you don't need any extra hardware to follow it. ```{tip} - Only use physical machines in a production environment. Use VMs as cluster members only in testing or development environments, such as this tutorial. For this, nested virtualization must be enabled on your host machine. See the [Ubuntu Server documentation on how to check if nested virtualization is enabled](https://documentation.ubuntu.com/server/how-to/virtualisation/enable-nested-virtualisation/#check-if-nested-virtualisation-is-enabled). + Only use physical machines in a production environment. Use VMs as cluster members only in testing or development environments, such as this tutorial. For this, nested virtualization must be enabled on your host machine. See the [Ubuntu Server documentation on how to check if nested virtualization is enabled](https://documentation.ubuntu.com/server/how-to/virtualisation/enable-nested-virtualisation). We also limit each machine in this tutorial to 2 GiB of RAM, which is less than the recommended hardware requirements. In the context of this tutorial, this amount of RAM is sufficient. However, in a production environment, make sure to use machines that fulfill the {ref}`reference-requirements-hardware`. ```