Bug 1295806
Summary: | too many warnings coming from ceph-deploy | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Ben England <bengland> |
Component: | Ceph-Installer | Assignee: | Christina Meno <gmeno> |
Status: | CLOSED WONTFIX | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 1.3.1 | CC: | adeza, anharris, aschoen, ceph-eng-bugs, flucifre, kdreyer, nthomas, sankarshan |
Target Milestone: | rc | ||
Target Release: | 1.3.4 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-20 20:50:29 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
Ben England
2016-01-05 14:03:19 UTC
I don't see this as a bug. ceph-deploy reads stderr output from remote nodes and sets them as WARNING and stdout as DEBUG. There is really no good way to determine what would be true error output on remote execution. We could however lower the level, but then again, true warning messages on remote nodes would be misread as INFO and not as a warning. So far it has been very helpful to have high verbosity in ceph-deploy as it is easier for development to understand what and where things are going wrong. I can only suggest to raise the log level to ERROR if the current level is not sufficient. I don't think stderr output can be interpreted as level WARNING. The only way to know whether subprocess messages are reporting errors is to look at the process exit status. If it is zero, then it wasn't an error. If it was non-zero, then at least some of the output on either stderr or stdout was reporting an error. You can redirect the output from a subprocess to a file and decide what to do with it later. Just my opinion. Since ceph-deploy does "real time" logging, there is no way we can know about the error condition. I don't have a good solution here although I understand how cumbersome it is to look at the (probably long) output generated. |