creating-an-installation-medium-for-ubuntu-22-04: add ISO image note
I ran into difficulties with mounting the Ubuntu ISO image under /var/lib/foreman since I manage foreman with puppet, and mounting the ISO is more doable with puppet compared with copying the content. This commit just adds a note for other people who might want to try the same thing. This note may help someone avoid this particular pitfall.
Checklists
- [x] I am okay with my commits getting squashed when you merge this PR.
- [x] I am familiar with the contributing guidelines.
Please cherry-pick my commits into:
- [x] Foreman 3.14/Katello 4.16
- [x] Foreman 3.13/Katello 4.15 (EL9 only)
- [x] Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only)
- [ ] Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
- [ ] Foreman 3.10/Katello 4.12
- [ ] Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
- [ ] Foreman 3.8/Katello 4.10
- [ ] Foreman 3.7/Katello 4.9 (Satellite 6.14)
- We do not accept PRs for Foreman older than 3.7.
The PR preview for a6aa5723bf57bcd90521a3fb3d6981b6b0c6cc99 is available at theforeman-foreman-documentation-preview-pr-3847.surge.sh
The following output files are affected by this PR:
The documentation says clearly to mount the image under
/mnt.I would avoid mentioning any other directory as an option altogether. I do not recommend merging this PR.
What is the reason you tried to mount it under
/var/lib/foreman?
The current version of this PR does say to mount it under /mnt.
I had it mounted under /var/lib/foreman because that is the location where Foreman looks to consume the content of the ISO image. As mentioned in the original post, I manage my machines with Puppet. Following the documented procedure of mounting, copying, and removing the ISO image is not really idempotent and puppetizable.
Using a symlink to the mounted ISO, as in the current version of this PR, works perfectly though. Thanks to @evgeni on the Foreman Matrix channel for that idea.
Yes, but that is only temporary. The current procedure has you copy the content, and then unmount it. My contribution suggests a way to do it without having to mount, copy, and unmount.
Added a mention that this is a tip for Puppet management.
No objections from my side. In downstream, we currently suggest using ATIX-provided file repositories that you can sync to your orcharhino Server and optionally orcharhino Proxy Servers to perform offline host provisioning.
I'm declaring this PR mergeable.
I'll merge it tomorrow.
Cherry picked to currently supported and latest releases:
- df3ba87727..db052ffe37 3.16 -> 3.16
- 3f2eb9286c..6d0efd0d38 3.15 -> 3.15
- 53639fa8b4..d779592c5e 3.14 -> 3.14