Bug 1521138 - [RFE] Section organization should be reordered to better reflect workflow
Summary: [RFE] Section organization should be reordered to better reflect workflow
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhhi-1.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: RHHI-V 1.5
Assignee: Laura Bailey
QA Contact: SATHEESARAN
Chandrakanth Pai
URL:
Whiteboard:
Depends On:
Blocks: 1724792 1531908
TreeView+ depends on / blocked
 
Reported: 2017-12-05 20:52 UTC by Adam Scerra
Modified: 2025-06-16 08:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-15 10:07:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Scerra 2017-12-05 20:52:05 UTC
Description of problem:
link to Document: https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure/1.0/html/deploying_red_hat_hyperconverged_infrastructure/configure-gluster-rhv-manager#add_remaining_virtualization_hosts_to_the_hosted_engine

Section 9.3 is organized in a way that makes it difficult to follow. At sections 9.3.5,9.3.6 the documentation reads

 5. Click Deploy
 6. Attach the gluster network to the host
      i.Click the Hosts tab and select the host.
      ii.Click the Network Interfaces subtab and then click Setup Host Networks.
      iii.Drag and drop the newly created network to the correct interface.
      iv.Ensure that the Verify connectivity checkbox is checked.
      v.Ensure that the Save network configuration checkbox is checked.
      vi.Click OK to save.

Step 5 is run inside of a pop window and the user is never told to click OK and exit the pop up window, then step 6 has the user start a new task. Step 6 is more of a new header then a continued step.



Version-Release number of selected component (if applicable):


How reproducible:
always

Actual results:

9.3. Add remaining virtualization hosts to the hosted engine

Follow these steps in Red Hat Virtualization Manager for each of the other hosts.

    1. Click the Hosts tab and then click New to open the New Host dialog.
    
    2. Provide a Name, Address, and Password for the new host.
    
    3. Uncheck the Automatically configure host firewall checkbox, as firewall
       rules are already configured by gdeploy.
    
    4. In the Hosted Engine tab of the New Host dialog, set the value of Choose
       hosted engine deployment action to deploy.
    
    5. Click Deploy.

    6. Attach the gluster network to the host
        i. Click the Hosts tab and select the host.
        ii. Click the Network Interfaces subtab and then click Setup Host
            Networks.
        iii. Drag and drop the newly created network to the correct interface.
        iv. Ensure that the Verify connectivity checkbox is checked.
        v. Ensure that the Save network configuration checkbox is checked.
        vi. Click OK to save. 

    7. In the General subtab for this host, verify that the value of 
       Hosted Engine HA is Active, with a positive integer as a score.
      [the Important Note]

    8. Verify the health of the network
       Click the Hosts tab and select the host. Click the Networks subtab and
       check the state of the host’s network. 

Expected results:

Section should be organized into less steps that are more specific for the tasks needed to be done.

1. Adding hosts to the hosts tab/inventory
  i. Click the Hosts tab and then click New to open the New Host dialog.
  ii. Provide a Name, Address, and Password for the new host.
  iii. Uncheck the Automatically configure host firewall checkbox, as firewall
       rules are already configured by gdeploy.
  iv. In the Hosted Engine tab of the New Host dialog, set the value of Choose
      hosted engine deployment action to deploy.
  v. Click Deploy. <-- [change to 'Select Deploy' refer to bug #]
  vi. [Click OK] <-- same bug referenced above

2. Attach the gluster network to the host
  i. Click the Hosts tab and select the host.
  ii. Click the Network Interfaces subtab and then click Setup Host Networks.
  iii. Drag and drop the newly created network to the correct interface.
  iv. Ensure that the Verify connectivity checkbox is checked.
  v. Ensure that the Save network configuration checkbox is checked.
  vi. Click OK to save.

3. In the General subtab for this host, verify that the value of Hosted Engine
   HA is Active, with a positive integer as a score.
   IMPORTANT [the important note]


4. Verify the health of the network
   Click the Hosts tab and select the host. Click the Networks subtab and check
   the state of the host’s network.
   IMPORTANT [the important note]

Additional info:

Comment 2 Laura Bailey 2018-01-08 00:38:46 UTC
Good feedback, thanks Adam.

Comment 6 Laura Bailey 2018-01-31 04:49:49 UTC
I think this was partially corrected in an update for RHHI 1.1, but I've altered the structure of this process as suggested, i.e.

1. Add virtualization hosts to the host inventory
  a. Click the **Hosts** tab and then click **New** to open the _New Host_ dialog.
  b. Provide a **Name**, **Address**, and **Password** for the new host.
  c. Under **Advanced Parameters**, uncheck the **Automatically configure host firewall** checkbox, as firewall rules are already configured by gdeploy.
  d. In the **Hosted Engine** tab of the _New Host_ dialog, set the value of **Choose hosted engine deployment action** to **deploy**.
  e. Click **OK**.

2. Attach the gluster network to the new host

[...]



Thanks for submitting this, Adam!

Comment 12 John 2025-06-16 08:49:06 UTC
 is described as being within a pop-up window, but the documentation fails to instruct the user to "Click OK" or exit this pop-up window before proceeding.   https://www.mybkexperience.it.com


Note You need to log in before you can comment on or make changes to this bug.