Bug 986747
Summary: | ssm: ssm -f doesn't work when creating or adding | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jimmy Pan <jipan> |
Component: | system-storage-manager | Assignee: | Lukáš Czerner <lczerner> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Beňas <pbenas> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | ccui, kzhang, pbenas, pstehlik |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | system-storage-manager-0.4-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-13 09:46:08 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
Jimmy Pan
2013-07-22 02:41:33 UTC
This was fixed upstream with ea0d52abdfaa90b727f31bb81770951738281439. -Lukas Correction, the trace was fixed by that commit. However you'll be still prompted even though -f has been provided. Problem with making 'force' to work for everything is that we're actually using stack of tools and in this case you usually want to 'force' only the removal. However what if you're creating a file system, do you want to force it as well ? There is actually no way to tell. No sure how to resolve this right now... -Lukas Fixed upstream with https://sourceforge.net/p/storagemanager/code/ci/bb76641a30ff428021df6f99b0f3e32211e1e9a6/ -Lukas Building in system-storage-manager-0.4-1.el7 Reproduced in system-storage-manager-0.3-1.el7.noarch and verified in system-storage-manager-0.4-1.el7.noarch. This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |