Bug 1458715
Summary: | rbd feature disable command crashes if no feature specified in command. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Ramakrishnan Periyasamy <rperiyas> |
Component: | RBD | Assignee: | Jason Dillaman <jdillama> |
Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.3 | CC: | ceph-eng-bugs, dzafman, hnallurv, icolle, kchai, tserlin |
Target Milestone: | rc | ||
Target Release: | 2.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.7-25.el7cp Ubuntu: ceph_10.2.7-27redhat1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 13:33:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ramakrishnan Periyasamy
2017-06-05 10:01:59 UTC
Trivial fix -- note that "rbd feature enable <image-spec>" does not crash, only when the image is specified using the optional. Upstream PR: https://github.com/ceph/ceph/pull/15492 Moving this bug to verified state. Command not crashing, output is below. [root@host1 ~]# rbd feature disable --image rbd-img1 rbd: at least one feature name must be specified [root@host1 ~]# rbd feature disable --image rbd: the required argument for option '--image' is missing [root@host1 ~]# rbd feature disable --image rbd-img1 rbd: at least one feature name must be specified [root@host1 ~]# rbd feature disable rbd-img1 rbd: at least one feature name must be specified [root@host1 ~]# rbd feature disable rbd: image name was not specified [root@host1 ~]# rbd feature disable pool1-img1 rbd: at least one feature name must be specified 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://access.redhat.com/errata/RHBA-2017:1497 |