Ubuntu guide and snippet edit

Author: sus-admin

_includes/cloud-init_network.txt

@@ -46,6 +46,8 @@
             - $dns
                     #end for
                 #end if
+            #else
+        dhcp4: true
             #end if
         #else
         dhcp4: true

_posts/2024-12-11-Cobbler-v3.3.7-Ubuntu-Deployment-Guide.md

@@ -60,7 +60,9 @@ Create the new Cobbler template and snippets necessary to generate the `cloud-in
 {% for line in lines %}{{ line | prepend: "      " }}
 {% endfor %}
 
-> This section should resemble the standard [netplan](https://netplan.readthedocs.io/en/latest/netplan-yaml/) YAML configuration file for Ubuntu once generated.
+> This section assumes that, for automated Cobbler System deployments (not Profiles...), each system interface defined should have the corresponding MAC address defined, a standard requirement in Cobbler. Less intuitively, this solution only adds DNS servers to static interfaces with an IP address defined, since DNS servers are set per-interface in Ubuntu cloud-init/netplan, but per-system in Cobbler.
+>
+> Also, the above section should resemble the standard [netplan](https://netplan.readthedocs.io/en/latest/netplan-yaml/) YAML configuration file for Ubuntu once generated. 
 
 Create 2 Cobbler sync-triggers to correct the GRUB and PXELINUX boot configurations to support Ubuntu `cloud-init` installations, which will run each time the `cobbler sync` action is performed:
 
@@ -87,9 +89,7 @@ chmod u+x /var/lib/cobbler/triggers/sync/post/fix-ubuntu-profiles-GRUB_PXE.sh
 chmod u+x /var/lib/cobbler/triggers/sync/post/fix-ubuntu-systems-GRUB_PXE.sh
 ```
 
-> Cobbler is normally a dynamic and responsive app that implements many options, parameters, and configurations on-demand through `edit|add|remove|etc...` actions, not requiring a `cobbler sync` to commit most changes. However, it is recommended to run `cobbler sync` after any changes to a *(Ubuntu)* Cobbler Distro/Profile/System when using Cobbler sync-triggers in this manner, unless you're absolutely certain otherwise.
->
-> **TIP:** Cobbler recommends writing triggers as Python modules and has a lot of good info in their [docs](https://cobbler.readthedocs.io/en/latest/user-guide/extending-cobbler.html#about), but I have only written bash scripts that slowly but surely accomplish my needs.
+> More info on Cobbler triggers in the **Tips & Troubleshooting** section below
 
 Download the latest 3 releases of Ubuntu Server LTS
 
@@ -243,6 +243,12 @@ cobbler sync
 
 1. The [Cobbler 3.3.6 Beginner's Guide](/blog/2024/Cobbler-v3.3.6-Beginners-Guide/) **Tips & Troubleshooting** section contains some basic recommendations and limitations of Cobbler which will not be repeated here.
 
+1. **Cobbler Triggers**
+
+    - Cobbler is normally a dynamic and responsive app that implements many options, parameters, and configurations on-demand through `edit|add|remove|etc...` actions, not requiring a `cobbler sync` to commit most changes. However, it is recommended to run `cobbler sync` after any changes to a Cobbler Distro/Profile/System when using Cobbler sync-triggers in this manner *(editing DHCP configs, boot options, etc...)*, unless you're absolutely certain otherwise.
+
+    - Cobbler recommends writing triggers as Python modules and has a lot of good info in their [docs](https://cobbler.readthedocs.io/en/latest/user-guide/extending-cobbler.html#about), but I have only written bash scripts that slowly but surely accomplish my needs.
+
 1. Troubleshooting the installation
 
     - The Ubuntu installer will reboot the system automatically upon completing a `cloud-init` auto-install. To prevent this, append the following line to the end of the autoinstall template (`cloud-init_user-data`) as the final command in the `late-commands:` section *(be sure the spacing/indentation aligns with the rest of the `late-command` entries)*: