Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-9066

Successfully configured Slave node with no server configured is not shown in the list of hosts

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 9.3.0.Alpha1
    • Component/s: Console
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Consider two hosts (VMs) master and slave with Infinispan unzipped/installed/patched at a given location.

      1. Add a management user with username slave using the $ISPN_HOME/bin/add-user.sh script on the host master, with no group association and at the last stage, choose yes when prompted Is this new user going to be used for one AS process to connect to another AS process?
      2. Start the domain controller on the host master and bind (-b) the domain controller and its management port (-bmanagement) to the public IP address of the VM
      3. On the slave host, update the host.xml with
        1. the name="slave" added to the <host> element
        2. the secret XML tag obtained from step #1 (see host-slave.xml for reference)
        3. with no <server> elements under <servers> and
        4. start the host controller with domain.sh bound (-b) to the VM's public IP address and with --master-address=<master-ip> and --master-port=9999
      4. Now using CLI ($ISPN_HOME/bin/cli.sh --connect --controller=master-ip:9999) on the master VM, check the path `/host=` and try to hit tab. If you see two options master and slave, the slave successfuly registered.
      5. Now using the Management Console server by the master node, navigate to Clutsers → Cluster and click on Add Node and verify if you see two nodes master and slave. If you see only master you ran into the bug.
      Show
      Consider two hosts (VMs) master and slave with Infinispan unzipped/installed/patched at a given location. Add a management user with username slave using the $ISPN_HOME/bin/add-user.sh script on the host master , with no group association and at the last stage, choose yes when prompted Is this new user going to be used for one AS process to connect to another AS process? Start the domain controller on the host master and bind (-b) the domain controller and its management port (-bmanagement) to the public IP address of the VM On the slave host, update the host.xml with the name="slave" added to the <host> element the secret XML tag obtained from step #1 (see host-slave.xml for reference) with no <server> elements under <servers> and start the host controller with domain.sh bound (-b) to the VM's public IP address and with --master-address=<master-ip> and --master-port=9999 Now using CLI ($ISPN_HOME/bin/cli.sh --connect --controller=master-ip:9999) on the master VM, check the path `/host=` and try to hit tab. If you see two options master and slave , the slave successfuly registered. Now using the Management Console server by the master node, navigate to Clutsers → Cluster and click on Add Node and verify if you see two nodes master and slave . If you see only master you ran into the bug.

      Description

      Considering two host setup (master and slave), where the master host is running the domain controller and host controller whereas slave host is only running the slave controller. If the slave's host.xml does not have any servers initially configured, despite successful registration with the domain controller running on master, the slave host does appear for the drop-down of the Add Node feature on the page Clusters → Cluster.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                vblagojevic Vladimir Blagojevic
                Reporter:
                vblagojevic Vladimir Blagojevic
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: