From 3a3b92048f5f10760457a8283d86e106f7b4707b Mon Sep 17 00:00:00 2001 From: Sebastian Heid <8442432+s4heid@users.noreply.github.com> Date: Thu, 25 Sep 2025 16:17:34 +0000 Subject: [PATCH] Fix cloud-init logging format The typo leads to problems when cloud-init attempts to load the logging configuration. This is evident in the logs, as shown by the following stack trace: > cloud-init[515]: 2025-09-24 12:07:29,260 - util.py[WARNING]: Failed > loading yaml blob. Invalid format at line 10 column 1: "expected ? '', but found '' > cloud-init[515]: in "", line 10, column 1: > cloud-init[515]: _log: > cloud-init[515]: ^" --- .../system_azure_init/assets/etc/cloud-init/05-logging.cfg | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/stemcell_builder/stages/system_azure_init/assets/etc/cloud-init/05-logging.cfg b/stemcell_builder/stages/system_azure_init/assets/etc/cloud-init/05-logging.cfg index b6d39ad6fc..b5a95e8078 100644 --- a/stemcell_builder/stages/system_azure_init/assets/etc/cloud-init/05-logging.cfg +++ b/stemcell_builder/stages/system_azure_init/assets/etc/cloud-init/05-logging.cfg @@ -1,7 +1,7 @@ -=## This yaml formated config file handles setting +## This yaml formatted config file handles setting ## logger information. The values that are necessary to be set ## are seen at the bottom. The top '_log' are only used to remove -## redundency in a syslog and fallback-to-file case. +## redundancy in a syslog and fallback-to-file case. ## ## The 'log_cfgs' entry defines a list of logger configs ## Each entry in the list is tried, and the first one that @@ -68,5 +68,4 @@ log_cfgs: # This tells cloud-init to redirect its stdout and stderr to # 'tee -a /var/log/cloud-init-output.log' so the user can see output # there without needing to look on the console. -output: {all: '| tee -a /var/log/cloud-init-output.log'} - +output: {all: '| tee -a /var/log/cloud-init-output.log'} \ No newline at end of file