Bug 1341598 – Crush rule ids are not set as specified in the request instead takes the auto incremented one

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1341598 - Crush rule ids are not set as specified in the request instead takes the auto incremented one [NEEDINFO]

Summary:	Crush rule ids are not set as specified in the request instead takes the auto...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Ceph Storage
Classification:	Red Hat
Component:	Calamari (Show other bugs)
Sub Component:
Version:	2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	2.0
Assigned To:	Gregory Meno
QA Contact:	Nishanth Thomas
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1339529 1343229
	Show dependency tree / graph

Reported:	2016-06-01 06:32 EDT by Nishanth Thomas
Modified:	2016-08-23 15:40 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	calamari-server-1.4.1-1.el7cp
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-08-23 15:40:20 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	gmeno: needinfo? (nthomas)

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1755	normal	SHIPPED_LIVE	Red Hat Ceph Storage 2.0 bug fix and enhancement update	2016-08-23 19:23:52 EDT

Groups: None (edit)

Description Nishanth Thomas 2016-06-01 06:32:55 EDT

Description of problem:
Crush rule ids are not set as specified in the request instead takes the auto incremented one. The issue here is that the crush rule created becomes unusable

Expected results:
Make it auto incremented by default. User need not specify crush rule id in the crush rule creation request

Comment 2 Gregory Meno 2016-06-02 11:36:14 EDT

the workaround is hard, USM has to guess what ceph will assign the ruleset id
one possibility is to relax the validation so that ruleset is not required on create

Comment 3 Nishanth Thomas 2016-06-04 06:40:16 EDT

I think that would be sufficient. Let the ruleset is autogenerated, which will solve the problem for us. The only thing to make sure is that, calamari gets the right ruleset and stores it.

Comment 4 Gregory Meno 2016-06-08 18:57:31 EDT

I'm a little confused here:
ruleset has not been required in create or update since 5/18/16.


Nishanth is it that you want them to not be allowed during create or update since we don't honor them?

Comment 7 Harish NV Rao 2016-07-12 06:31:30 EDT

Moving this to verified state as Nishanth confirmed that the issue is fixed.

Comment 9 errata-xmlrpc 2016-08-23 15:40:20 EDT

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.

https://rhn.redhat.com/errata/RHBA-2016-1755.html

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