Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4786

Clustering integration tests fails once -Dnode0 and -Dnode1 are used

    XMLWordPrintable

Details

    • Hide

      ./integration-tests.sh clean install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -Dmcast=$MCAST_ADDR -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.*.* -Djboss.dist=$JBOSS_DIST -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

      Show
      ./integration-tests.sh clean install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -Dmcast=$MCAST_ADDR -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.*.* -Djboss.dist=$JBOSS_DIST -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

    Description

      Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties.

      See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-clustering/

      • build 5 binds to localhost (no -Dnode*)
      • build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

      Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015

      Attachments

        1. testsuite.clustering.logs.zip
          444 kB
        2. results.zip
          195 kB
        3. maven.logs
          2.60 MB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-322 Clustering integration tests fails once -Dnode0 and -Dnode1 are used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5021 XSiteSimpleTestCase fails with -Dnode{0,1}

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5519 Some clustering tests fail with security manager

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: