RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1664057 - [GUI] Issues in 'create new cluster' form
Summary: [GUI] Issues in 'create new cluster' form
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.0
Assignee: Ivan Devat
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-07 15:42 UTC by Tomas Jelinek
Modified: 2019-06-14 00:57 UTC (History)
7 users (show)

Fixed In Version: pcs-0.10.1-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 00:57:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed fix (10.96 KB, patch)
2019-01-08 13:08 UTC, Tomas Jelinek
no flags Details | Diff

Description Tomas Jelinek 2019-01-07 15:42:51 UTC
Description of problem:
Several issues were found in the 'create new cluster' form in pcs web ui.


Version-Release number of selected component (if applicable):
pcs-0.10.1-2.el8


How reproducible:
always, easily


Issue 1:
* login to pcs web ui
* click 'Create New', the 'create cluster' form will be displayed
* enter cluster name and node names
* click 'Go to advanced settings'
* authenticate the nodes if necessary
* in Transport, Addresses click Add link
* click Back to get to the previous step of the form
* change node names
* click 'Go to advanced settings'
* the link(s) list old node names instead of the new ones

workaround: remove all the links and add them again


Issue 2:
* follow issue 1 to get to advanced settings
* add a link and set some link options, do not set addresses
* submit the form
* An error message says an empty address is unresolvable. Instead, an address should be filled in in the backend by default. If nodes do not have same number of addresses specified, it should be reported.

workaround: specify node addresses


Issue 3:
* follow issue 1 to get to advanced settings
* enter a not valid value, i.e. put a string where a number is expected
* submit the form
* an error is displayed
* correct the value and submit the form again
* a dialog is displayed saying the cluster was created
* the error is still displayed in the dialog, however, which is a bug

workaround: ignore the error message

Comment 2 Tomas Jelinek 2019-01-08 13:08:34 UTC
Created attachment 1519181 [details]
proposed fix

Comment 4 Ivan Devat 2019-01-14 14:07:12 UTC
After Fix:

[ant8 ~] $ rpm -q pcs
pcs-0.10.1-3.el8.x86_64

> Issue 1:
* login to pcs web ui
* click 'Create New', the 'create cluster' form will be displayed
* enter cluster name and node names
* click 'Go to advanced settings'
* authenticate the nodes if necessary
* in Transport, Addresses click Add link
  * fill addresses for nodes
* click Back to get to the previous step of the form
* change node names
  * keep some of previous names
* click 'Go to advanced settings'
* node names are updated in address section of link
  * addresses that was filled for kept nodes are still filled

> Issue 2.a:
* follow issue 1 to get to advanced settings
* add a link and set some link options, do not set addresses
* submit the form
* no error

> Issue 2.b:
* follow issue 1 to get to advanced settings
* add two links
  * set addresses but omit one in second link
  * so one node has only one address specified and the rest nodes has two adresses specified
* submit the form
* An error message says all nodes must have the same number of addresses

> Issue 3:
* follow issue 1 to get to advanced settings
* enter a not valid value, i.e. put a string where a number is expected
* submit the form
* an error is displayed
* correct the value and submit the form again
* a dialog is displayed saying the cluster was created and no error is displayed here


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