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

The BootLoggingPatchingStateTestCase fails if the message assertion is flipped

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.1.0.CR1
    • None
    • Patching, Test Suite
    • None

      The BootLoggingPatchingStateTestCase tests two patches which use a different version and product id for the patch. The tests currently pass because of the order of the Collection.containsAll(). However if this is flipped the tests fail.

      It appears that the messages logged always contain the "WildFly" product id. Also the UUID for the failing examples seems to not be logged either.

      Example of logged messages for the "lp1" patch in the test:

      WildFly cumulative patch ID is: 936c95a3-f08e-4fc0-9917-f7feead4ef25, one-off patches include: 00699c2c-84a5-4bdb-b469-8c2fd66afe2a, c6df609e-1620-4369-af48-8041d4be093f
WildFly cumulative patch ID is: 936c95a3-f08e-4fc0-9917-f7feead4ef25, one-off patches include: 00699c2c-84a5-4bdb-b469-8c2fd66afe2a, c6df609e-1620-4369-af48-8041d4be093f

      It looks like the same message is logged twice. However the following is what's expected:

      lp1 cumulative patch ID is: base, one-off patches include: 50a820e4-3659-437d-86f2-fa1d64728adb
WildFly cumulative patch ID is: 936c95a3-f08e-4fc0-9917-f7feead4ef25, one-off patches include: 00699c2c-84a5-4bdb-b469-8c2fd66afe2a, c6df609e-1620-4369-af48-8041d4be093f

      I'm not sure if this is just an issue with the test or if there is a bug in patching.

              olubyans@redhat.com Alexey Loubyansky
              jperkins-rhn James Perkins
              Jan Martiska Jan Martiska
              Jan Martiska Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: