Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 682323

Summary: if ricci authentication hasn't taken place yet, then state that and exit
Product: Red Hat Enterprise Linux 6 Reporter: Corey Marthaler <cmarthal>
Component: ricciAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: cluster-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ricci-0.16.2-29.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:18:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2011-03-04 20:33:20 UTC
Description of problem:
I'm trying to bump the .conf version number and ricci prompts me continuously for auth passwords. It never stops (even though I continue to enter the correct vaild password) which is super annoying.

The only error can only be found in messages:
Mar  4 14:21:37 hayes-01 saslauthd[1947]: do_auth         : auth failure: [user=ricci] [service=ricci] [realm=] [mech=pam] [reason=PAM auth error]
Mar  4 14:21:42 hayes-01 saslauthd[1948]: do_auth         : auth failure: [user=ricci] [service=ricci] [realm=] [mech=pam] [reason=PAM auth error]

[root@hayes-01 ~]# cman_tool version -r
You have not authenticated to the ricci daemon on hayes-01
Enter the ricci password for hayes-01:
You have not authenticated to the ricci daemon on hayes-03
Enter the ricci password for hayes-03:
You have not authenticated to the ricci daemon on hayes-02
Enter the ricci password for hayes-02:
You have not authenticated to the ricci daemon on hayes-01
Enter the ricci password for hayes-01:
You have not authenticated to the ricci daemon on hayes-03
Enter the ricci password for hayes-03:
You have not authenticated to the ricci daemon on hayes-02
Enter the ricci password for hayes-02:
You have not authenticated to the ricci daemon on hayes-03
Enter the ricci password for hayes-03:
[THIS GOES ON FOREVER]

A ^C doesn't even help. If the cmd fails, then exit already. 

Version-Release number of selected component (if applicable):
ricci-0.16.2-28.el6.x86_64
cman-3.0.12-34.el6.x86_64

Comment 1 Corey Marthaler 2011-03-04 21:04:52 UTC
The above "Enter the ricci password" endless loop should be replaced with a single message stating "hey dummy, run passwd ricci".

Comment 2 Chris Feist 2011-03-04 22:01:09 UTC
If the password entered isn't correct, cman_tool should immediately fail (with a message to that effect).  It shouldn't continue to request a password.  devel_acking this.

Comment 3 Chris Feist 2011-03-08 22:45:53 UTC
Due to the way ccs_sync was written a rewrite of major parts of the code would be necessary to completely fix the broken behavior.

However, now when you type Control-C, it will actually interrupt the program and get you out.

Also, if you enter an incorrect password for a node, ccs_sync may ask your for passwords for other nodes, but it will not ask for the password for a node more than once.

How to test:
On all ricci nodes:
rm -f /var/lib/ricci/certs/clients/client_cert_*
service ricci restart

On node running ccs_sync:
[root@ask-03 ~]# ccs_sync
You have not authenticated to the ricci daemon on ask-03
Password: <enter bad password here>
Incorrect ricci password for ask-03
[root@ask-03 ~]# 

With old ccs_sync it would continually ask for the nodes password instead of failing

Comment 5 Corey Marthaler 2011-04-07 19:28:44 UTC
This now exits after receiving an invalid password, as well as when receiving a ^C. I'd still like to see it exit right away with a "run 'passwd ricci'" message when it knows that authenticated hasn't even taken place yet. I'll file another RFE for that and mark this one verified.

[root@taft-01 ~]# cman_tool version -r
You have not authenticated to the ricci daemon on taft-01
Password:
You have not authenticated to the ricci daemon on taft-04
Password:
You have not authenticated to the ricci daemon on taft-03
Password:
You have not authenticated to the ricci daemon on taft-02
Password:
Incorrect ricci password for taft-01
cman_tool: ccs_sync failed.
If you have distributed the config file yourself, try re-running with -S

[root@taft-01 ~]# cman_tool version -r
You have not authenticated to the ricci daemon on taft-03
Password:
You have not authenticated to the ricci daemon on taft-04
Password: ^C
cman_tool: ccs_sync failed.
If you have distributed the config file yourself, try re-running with -S

Comment 6 errata-xmlrpc 2011-05-19 14:18:03 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0749.html