AFTER:
======

[root@virt-058 ~]# rpm -q pcs
pcs-0.10.8-1.el8.x86_64


## New 'resource create' wizard

- Open the web ui, for this case: https://virt-058.cluster-qe.lab.eng.brq.redhat.com:2224/ui/
- Log in
- Add existing cluster via specifying one of the cluster nodes
- Click on the cluster name in the dashboard
- Click on 'Resources' in the cluster menu
- Click on 'Create Resource'
- 4-step Wizard appears:
New resource
Create new resource wizard


1. Name and type
- Resource name ('r1' for this test case)
- Resource type - all resource types are listed. It is possible to use search (ocf:heartbeat:IPaddr2 for this test case)
- Both fields are required, the wizard shall not let you pass, if you omit any:
Please provide the new resource name
Please select resource agent
- Click 'Next'


2. Instance attributes:
- Here you specify all required resource attributes and optionally some other
- Required attributes are shown by default, you can additionally add to filter 'Optional' and 'Advanced' attributes
- There is also a search field, that dynamically shows you desired attributes as you typing
- All attributes have description, e.g. ip:
IPv4 or IPv6 address
The IPv4 (dotted quad notation) or IPv6 address (colon hexadecimal notation) example IPv4 "192.168.1.1". example IPv6 "2001:db8:DC28:0:0:FC57:D4C8:1FFF".

- For this test case, Setting up ip attribute (required):
ip: 192.168.1.58

- There is info, if you choose a resource type, that doesn't have any required attributes (e.g. ocf:heartbeat:Dummy):
Info alert:No instance attribute is required. Other available attributes can be added.


3. Settings
- Specify these setting to specific resource:
Multiple instances
Group
Start automatically

- With Multiple instances, 'Clone' can be ticked, if it is, another option will be shown: 'Promotable'
- With Group, 'Use group' can be ticked, it can't be ticked if the resource is 'Clone'. Then you can select, if the resource will be part of existing group from the list of cluster groups, or if you create new group, where you define its name.
- With Start automatically, 'Disabled' can be ticked

> All of the options above and its combinations were tried for this test case, only 'Disabled' option works at this moment. New bz was created for this issue: bz1927384


4. Review new resource configuration
- review of the entered settings for the new resource, e.g.:
Resource name
    r1
Resource type
    ocf:heartbeat:IPaddr2
Instance attributes
    ip
        192.168.1.58
Clone
    no
Group
    no
Disabled
    no

- Click 'Finish'
(in every step of the creation, you can jump between other steps depending on fulfillment of required fields, or you can Cancel the wizard)

- If everything is ok:
Resource "r1" created successfully

- If resource can't be created (for example unique required value is not unique across resources), the message from backend will be shown and you are offered alternative options:
Create resource "r1" failed
Create resource failed in the backend (see messages below). You can return back, correct values and try to create resource again. The messages will be kept in the wizard.
Button: Back to first step
Button: Cancel
Messages:
Danger alert:Value '192.168.1.58' of option 'ip' is not unique across 'ocf:heartbeat:IPaddr2' resources. Following resources are configured with the same value of the instance attribute: 'r5'


Result:
=======
There is an issue with the following cases:
1. Resource is not cloned if 'Clone' option was ticked 
2. Resource is nor promotable or clone, if 'Promotable' option was ticked
3. Resource is not in already existing group, if 'Use group' with 'Select existing group' is selected
4. Resource is not in newly created group, if 'Use group' with 'Create new group' is selected


Marking as VERIFIED for pcs-0.10.8-1.el8 with new bz created, solving the issues described above: bz1927384

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (pcs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1737