Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osd: clarify REQUIRE_LUMINOUS error message #13363

Merged
merged 1 commit into from Feb 12, 2017

Conversation

Projects
None yet
4 participants
@jdurgin
Copy link
Member

jdurgin commented Feb 10, 2017

This should be visible at the default log level, so users have some
hope of figuring out the problem.

Signed-off-by: Josh Durgin jdurgin@redhat.com

osd: clarify REQUIRE_LUMINOUS error message
This should be visible at the default log level, so users have some
hope of figuring out the problem.

Signed-off-by: Josh Durgin <jdurgin@redhat.com>

@jdurgin jdurgin added the core label Feb 10, 2017

@liewegas
Copy link
Member

liewegas left a comment

1 is logged by default, but a higher error level can't hurt!

@xiexingguo

This comment has been minimized.

Copy link
Member

xiexingguo commented Feb 11, 2017

This should be visible at the default log level, so users have some
hope of figuring out the problem.

+1

@tchaikov tchaikov added the needs-qa label Feb 11, 2017

@liewegas liewegas merged commit cfccde7 into ceph:master Feb 12, 2017

3 checks passed

Signed-off-by all commits in this PR are signed
Details
Unmodifed Submodules submodules for project are unmodified
Details
default Build finished.
Details

shinobu-x added a commit to shinobu-x/ceph that referenced this pull request Feb 12, 2017

Merge pull request ceph#13363 from jdurgin/wip-req-luminous-error
osd: clarify REQUIRE_LUMINOUS error message

Reviewed-by: xie xingguo <xie.xingguo@zte.com.cn>
Reviewed-by: Kefu Chai <kchai@redhat.com>

@jdurgin jdurgin deleted the jdurgin:wip-req-luminous-error branch Feb 14, 2017

@jdurgin

This comment has been minimized.

Copy link
Member Author

jdurgin commented Feb 14, 2017

@liewegas 0 is the default level for the osd subsys - perhaps there are some other warnings that should be made visible

@liewegas

This comment has been minimized.

Copy link
Member

liewegas commented Feb 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.