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 1688262 - Destroying nonexistent fs should fail
Summary: Destroying nonexistent fs should fail
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: stratis-cli
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Stratis Team
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-13 12:19 UTC by Jakub Krysl
Modified: 2021-09-06 15:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-18 13:04:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jakub Krysl 2019-03-13 12:19:01 UTC
Description of problem:
There is no difference when destroying stratis fs that exists or does not from user point of view. Both of these succeed so there is no feedback (except small time delay) to user if the fs got actually destroyed or (for example) he made a typo.

# stratis pool create test_pool /dev/sda
# time stratis fs create test_pool test_fs
# time stratis fs destroy test_pool test_fs
real    0m0.273s
user    0m0.116s
sys     0m0.006s
# time stratis fs destroy test_pool test_fs
real    0m0.161s
user    0m0.111s
sys     0m0.013s
# time stratis fs destroy test_pool anything
real    0m0.145s
user    0m0.106s
sys     0m0.016s

Version-Release number of selected component (if applicable):
stratisd-1.0.3-1.el8.x86_64
stratis-cli-1.0.2-1.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. stratis pool create test_pool /dev/sda
2. stratis fs destroy test_pool anything_at_all

Actual results:
same output as actually destroying existing fs

Expected results:
different from actually destroying existing fs

Additional info:

Comment 1 mulhern 2019-03-18 13:04:34 UTC
This behavior was chosen for idempotency.


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