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

Standby Fuse container in active/standby configuration does not expose an SSH service since 6.2

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.2
    • Fix Version/s: jboss-fuse-6.3
    • Component/s: Karaf
    • Labels:
    • Environment:

      JBoss Fuse 6.2

    • Sprint:
      6.3 Sprint 1 (4-Jan->29-Jan)
    • Steps to Reproduce:
      Hide

      1. Install Fuse 6.2 GA
      2. bin/fuse
      3. In a different console, bin/fuse
      4. Check the open ports in the second instance – no SSH port is exposed

      Show
      1. Install Fuse 6.2 GA 2. bin/fuse 3. In a different console, bin/fuse 4. Check the open ports in the second instance – no SSH port is exposed

      Description

      In Fuse 6.1, when Fuse was used in an active/standby configuration so that only one instance would be active at a given time, the standby instance initialized its SSH service and could be interrogated via SSH or using the bin/client script.

      As of 6.2 this behaviour has changed, presumably because the start-level of the sshd bundles have changed from 30 to 80. Customers that relied on SSH access to monitor their production systems can no longer do so.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  sonicaaaa Paolo Antinori
                  Reporter:
                  kboone Kevin Boone
                  Tester:
                  Josef Ludvicek
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: