-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.3
-
None
-
No
-
Low
-
rhel-ha
-
3
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
We should unify some of the resource-agents attribute names to be the same across all the different resource-agents.
For example, in some resource-agents that have an attribute (or option) called password, passwd, or some other attribute name that is for password.
# pcs resource describe "ocf:heartbeat:slapd" 2>&1 | grep -v 'Description' | grep -v -ie 'check_passwd' | grep -ie '^ .*password' -ie '^ .*passwd'; password # pcs resource describe "ocf:heartbeat:sybaseASE" 2>&1 | grep -v 'Description' | grep -v -ie 'check_passwd' | grep -ie '^ .*password' -ie '^ .*passwd'; db_passwd # pcs resource describe "ocf:pacemaker:Dummy" 2>&1 | grep -v 'Description' | grep -v -ie 'check_passwd' | grep -ie '^ .*password' -ie '^ .*passwd'; passwd
Another example is when monitoring username and password attribute exists for the the resource-agent.
# pcs resource describe "ocf:heartbeat:oracle" 2>&1 | grep -v 'Description' | grep -ie '^ .*mon.*pass.*' -ie '^ .*mon.*user.*'; monuser monpassword root@rhel9-1 [13:45:15]:~ # pcs resource describe "ocf:heartbeat:pgsql" 2>&1 | grep -v 'Description' | grep -ie '^ .*mon.*pass.*' -ie '^ .*mon.*user.*'; monitor_user monitor_password
This is not an exhaustive list of resource-agent attributes that we could unify, but a few examples.
What is the impact of this issue to you?
From customer and support stand point if we unified some of these attributes/options then it would make using and supports these resource-agents easier.
Please provide the package NVR for which the bug is seen:
Latest version of resource-agents on RHEL 10.
How reproducible is this bug?:
Every time.
Steps to reproduce
- N/A
Expected results
The resource-agents should have unified attribute names when it is appropriate.
Actual results
The resource-agents do not have unified attribute names when it is appropriate as demonstrated in the examples above.