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 797292

Summary:	ccs --createcluster should verify that a cluster.conf doesn't exist before creating one
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Feist <cfeist>
Component:	ricci	Assignee:	Chris Feist <cfeist>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	cluster-maint, djansa, rrati, rsteiger
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ricci-0.16.2-53.el6	Doc Type:	Bug Fix
Doc Text:	No documentation needed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 14:14:19 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 Chris Feist 2012-02-24 19:45:22 UTC

ccs --createcluster should verify that a cluster.conf doesn't exist before creating one.

To Test:
Using a host without a cluster.conf with ricci running.

ccs -h host --createcluster test
ccs -h host --createcluster test2

The second time the command is run an error should be printed stating that a cluster has already been created.

Comment 1 Chris Feist 2012-02-29 22:45:37 UTC

Fix here:

https://github.com/feist/ccs/commit/fb5ccddf8e67ac3c32b1d9c08017f8c4c2746318

Comment 2 Chris Feist 2012-03-01 00:29:14 UTC

With ricci-0.16.2-53.el6:


[root@ask-04 ~]# ccs -h localhost --createcluster testcluster[root@ask-04 ~]# ccs -h localhost --createcluster testcluster
cluster.conf already exists, use '-i' to override.
[root@ask-04 ~]# ccs -h localhost --createcluster testcluster2
cluster.conf already exists, use '-i' to override.
[root@ask-04 ~]# ccs -i -h localhost --createcluster testcluster2
[root@ask-04 ~]# ccs -h localhost --getconf
<cluster config_version="1" name="testcluster2">  
  <fence_daemon/>  
  <clusternodes/>  
  <cman/>  
  <fencedevices/>  
  <rm>    
    <failoverdomains/>    
    <resources/>    
  </rm>  
</cluster>

Comment 4 Chris Feist 2012-03-15 20:03:57 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 6 errata-xmlrpc 2012-06-20 14:14:19 UTC

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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2012-0898.html