Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7423

Unusual Behavior After Upgrading From Fuse 6.2.1 GA to R8 and Rolling Back

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • jboss-fuse-6.2.1
    • Patching
    • % %
    • Hide
      • Build out a fabric environment from the 6.2.1 GA (621084) release
      • Create a new version and add some profiles (1.1)
      • Upgrade containers to new version
      • Create a new version and upgrade patch-management (2.0)
      • Upgrade containers to new version
      • Create new version and apply rollup (2.1)
      • Upgrade containers to patched version
      • Roll containers back to unpatched version (1.1)
      • After completing rollback, upgrade containers to patched version (2.1)

      The non-patched libraries are restored upon rollback and upon upgrading a second time, the user is not reliably prompted to reaccomplish the manual library removal and containers may be reported in a success state when they should require restarting. I also noted that the non-patched git version (1.1) was checked out when the container was reported as being on the patched version (2.1)

      Show
      Build out a fabric environment from the 6.2.1 GA (621084) release Create a new version and add some profiles (1.1) Upgrade containers to new version Create a new version and upgrade patch-management (2.0) Upgrade containers to new version Create new version and apply rollup (2.1) Upgrade containers to patched version Roll containers back to unpatched version (1.1) After completing rollback, upgrade containers to patched version (2.1) The non-patched libraries are restored upon rollback and upon upgrading a second time, the user is not reliably prompted to reaccomplish the manual library removal and containers may be reported in a success state when they should require restarting. I also noted that the non-patched git version (1.1) was checked out when the container was reported as being on the patched version (2.1)

      Strange behavior was observed after upgrading a medium-sized (3 ensemble servers, 5 total root containers, around 7 child containers per root container) from Fuse 6.2.1 GA/084 to Fuse 6.2.1 R8/211. The behavior seems to have manifested after initially upgrading, rolling back, then re-upgrading to the rollup. Observed symptoms include containers reported in fabric as being on the patched (later version), but containers have the earlier (unpatched) git repo version checked out with committed and uncommitted changes, causing provisioning errors across the cluster.

      We noted that rolling containers back undoes the manual lib replacements needed for application of rollup. Possibly this has something to do with the behavior, but no error or warning about lib removal for org.apache.karaf.exception lib was reported during the second upgrade.

              ggrzybek Grzegorz Grzybek
              rhn-support-dhawkins Duane Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: