Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16663

[QE](7.2.z) WFLY-11510 - EarOpenTracingWithWeldProbeTestCase fails with node0/1 set

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.2.CR1, 7.2.2.GA
    • 7.2.1.CR1
    • Test Suite
    • None
    • Hide

      cd testsuite/integration/basic
      mvn clean test -Dtest=EarOpenTracingWithWeldProbeTestCase -Dnode0=<my IP> -Dnode1=<my IP>

      Show
      cd testsuite/integration/basic mvn clean test -Dtest=EarOpenTracingWithWeldProbeTestCase -Dnode0=<my IP> -Dnode1=<my IP>

    Description

      org.jboss.as.test.integration.microprofile.opentracing.EarOpenTracingWithWeldProbeTestCase fails with node0 and node1 set:

      WARN  [org.jboss.weld.probe.Probe] (default task-1) PROBE-000017: Access to /ServiceOne/service-endpoint/app denied for <my IP>
WARN  [org.jboss.weld.probe.Probe] (default task-1) PROBE-000017: Access to /ServiceOne/service-endpoint/app denied for <my IP>
...

java.lang.AssertionError: expected:<200> but was:<403>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:645)
	at org.junit.Assert.assertEquals(Assert.java:631)
	at org.jboss.as.test.integration.microprofile.opentracing.AbstractEarOpenTracingTestCase.testHttpInvokation(AbstractEarOpenTracingTestCase.java:67)
	at org.jboss.as.test.integration.microprofile.opentracing.AbstractEarOpenTracingTestCase.testEarServicesUseDifferentTracersAfterReload(AbstractEarOpenTracingTestCase.java:59)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

      Maybe access from remote IP addresses is blocked in development mode.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11510 EarOpenTracingWithWeldProbeTestCase fails with node0/1 set

          • 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

              pmackay@redhat.com Peter Mackay
              pmackay@redhat.com Peter Mackay
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: