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

yggdrasil-0.4.6 changes cause yggdrasil to not connect to configured broker unless protocol is configure explicitly

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • rhel-10.1
    • rhel-10.1
    • yggdrasil
    • None
    • yggdrasil-0.4.8-1.el10
    • Yes
    • Important
    • subs-client-tools
    • 5
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      Continue using yggdrasil-0.4.6 with the same configuration file that we used to use with 0.4.5

      What is the impact of this issue to you?

      Pull mode for remote execution in Satellite will stop working

      Please provide the package NVR for which the bug is seen:

      yggdrasil-0.4.6

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1) Have yggdrasil < 0.4.6
      2) Configure it to connect to a mqtt broker without explicitly setting `protocol` option to `mqtt`
      3) Update yggdrasil to 0.4.6

      Expected results

      Yggdrasil continues to connect to the broker

      Actual results

      Yggdrasil does not connect to the broker, because the default value for protocol option changed to `none` in 0.4.6.

              rh-ee-jlocash Joshua Locash
              aruzicka@redhat.com Adam Ruzicka
              Adam Ruzicka, Jason Jerome, Jiri Hnidek, Peter Ondrejka
              Joshua Locash Joshua Locash
              Archana Pandey Archana Pandey
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: