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

dispatcher_track_dns_changes failure on s390x

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • None
    • None
    • 1
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT SST - Future releases
    • Hide

      Given a RHEL machine with Nmstate running

      When running the `dispatcher_track_dns_changes` Nmstate CI tests

      Then, the test should pass successfully

      Definition of Done

      • The implementation meets the acceptance criteria
      • The code is part of a build attached to an errata
      Show
      Given a RHEL machine with Nmstate running When running the `dispatcher_track_dns_changes` Nmstate CI tests Then, the test should pass successfully Definition of Done The implementation meets the acceptance criteria The code is part of a build attached to an errata
    • None
    • None
    • s390x
    • None

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

      I've tried to run the NMCI dispatcher_track_dns_changes test, which ran successfully, but threw an exception in the test cleanup, trying to execute echo XY | nmstatectl apply -

      I've added the full test run to the attachments.

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

      nmstate-1.4.5-2.el8.s390x

      How reproducible:

      always

      Steps to reproduce

      1.  clone NMCI
      2.  ./test_run.sh dispatcher_track_dns_changes
      3.  

      Expected results:

      test passes

      Actual results:

      nmstate throws exception during cleanup

        1. test_run.log
          4 kB

              rh-ee-sfaye Stanislas Faye
              mberezny@redhat.com Matej Berezny (Inactive)
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: