Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-15037

fix: check that logging_max_message_size is set, not rsyslog_max_message_size

    • rhel-system-roles-1.23.0-2.1.el9
    • sst_system_roles
    • 11
    • 22
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • Enhancement
    • Hide
      .Use the `logging_max_message_size` parameter instead of `rsyslog_max_message_size` in the `logging` system role

      Previously, even though the `rsyslog_max_message_size` parameter was not supported, the `logging` RHEL System Role was using `rsyslog_max_message_size` instead of using the `logging_max_message_size` parameter.
      This enhancement ensures that `logging_max_message_size` is used and not `rsyslog_max_message_size` to set the maximum size for the log messages.
      Show
      .Use the `logging_max_message_size` parameter instead of `rsyslog_max_message_size` in the `logging` system role Previously, even though the `rsyslog_max_message_size` parameter was not supported, the `logging` RHEL System Role was using `rsyslog_max_message_size` instead of using the `logging_max_message_size` parameter. This enhancement ensures that `logging_max_message_size` is used and not `rsyslog_max_message_size` to set the maximum size for the log messages.
    • Done

      Enhancement: Check that `logging_max_message_size` is set, not `rsyslog_max_message_size`

      Reason: The play does not check if the correct variable is defined

      Result: Changed so that the test and action use the same variable name

            rmeggins@redhat.com Richard Megginson
            rmeggins@redhat.com Richard Megginson
            Richard Megginson Richard Megginson
            Jakub Haruda Jakub Haruda
            Apurva Bhide Apurva Bhide
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: