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

[Patch] Consistent problem applying patch when using bin/start

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.2
    • jboss-fuse-6.1
    • Patching
    • None
    • % %
    • Hide 
      sed -i 's/#admin/admin/' ${FUSE_INSTALL_PATH}jboss-fuse-6.1.0.redhat-379/etc/users.properties

${FUSE_INSTALL_PATH}jboss-fuse-6.1.0.redhat-379/bin/start

## wait for instance to be available
${FUSE_INSTALL_PATH}jboss-fuse-6.1.0.redhat-379/bin/client

      within karaf

      fabric:create --clean --wait-for-provisioning --profile fabric

version-create
patch-apply --version 1.1  --username admin --password admin  file:///data/installers/jboss-fuse-6.1.0.redhat-379-r1.zip
container-upgrade 1.1 root
      Show
      sed -i 's/#admin/admin/' ${FUSE_INSTALL_PATH}jboss-fuse-6.1.0.redhat-379/etc/users.properties ${FUSE_INSTALL_PATH}jboss-fuse-6.1.0.redhat-379/bin/start ## wait for instance to be available ${FUSE_INSTALL_PATH}jboss-fuse-6.1.0.redhat-379/bin/client within karaf fabric:create --clean --wait- for -provisioning --profile fabric version-create patch-apply --version 1.1 --username admin --password admin file: ///data/installers/jboss-fuse-6.1.0.redhat-379-r1.zip container-upgrade 1.1 root

      Hi rhn-support-jsherman I have identified a recurring problem while patching that I'd like your opinion about.

      Basically if I patch a 6.1 Fabric, that I have started with bin/start and that I was connected to with client script, the patching procedure always fail.

      In particular I see I got kicked out my session, which might be normal, but than I'm no longer able to connect to neither with client nor with ssh

      The same whole workflow, succeeds if I perform same steps to an instance started with bin/fuse

        1. karaf.log
          938 kB
          Paolo Antinori

            gertv_jira Gert Vanthienen (Inactive)
            pantinor@redhat.com Paolo Antinori
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: