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

Installed features on standalone's child do not persist patch process

XMLWordPrintable

    • % %
    • Hide

      1. bin/start, bin/client
      2. features:install admin
      3. admin:create test
      4. admin:start test
      5. patch:add file:<path-to-R4-patch>
      6. patch:install <R4-patch-name>
      7. list -> root is on correct version
      8. admin:connect -u karaf -p karaf test
      9. patch:install <R4-patch-name>
      10. patch is being installed, you are disconnected from test container
      11. admin:start test
      12. admin:connect -u karaf -p karaf test
      13. list -t 0 -> child is upgraded
      14. try to use patch command -> not found

      I have also noticed if you rollback test container you will see on the root (patch:list) that patch is still installed on test container.

      Show
      1. bin/start, bin/client 2. features:install admin 3. admin:create test 4. admin:start test 5. patch:add file:<path-to-R4-patch> 6. patch:install <R4-patch-name> 7. list -> root is on correct version 8. admin:connect -u karaf -p karaf test 9. patch:install <R4-patch-name> 10. patch is being installed, you are disconnected from test container 11. admin:start test 12. admin:connect -u karaf -p karaf test 13. list -t 0 -> child is upgraded 14. try to use patch command -> not found I have also noticed if you rollback test container you will see on the root (patch:list) that patch is still installed on test container.

      Features installed on karaf child (admin:create) is removed by patch installation.

            ggrzybek Grzegorz Grzybek
            ecervena@redhat.com Emil Cervenan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: