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

NSFS | NC | Change Debug Level of a Message HTTP Not Enabled #7691

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

shirady
Copy link
Contributor

@shirady shirady commented Jan 3, 2024

Explain the changes

  1. Change the debug level of a message HTTP not enabled from log0 to warn.

Issues: Fixed #xxx / Gap #xxx

  1. none

Testing Instructions:

  1. none
  • Doc added/updated
  • Tests added

@shirady shirady self-assigned this Jan 3, 2024
from log0 to warn

Signed-off-by: shirady <57721533+shirady@users.noreply.github.com>
@shirady
Copy link
Contributor Author

shirady commented Jan 3, 2024

While I tried to fix the Ceph tests on NC NSFS I had this message at first but didn’t notice it:

[nsfs/14] [L0] core.endpoint.endpoint:: HTTP is not allowed for NC NSFS.
nsfs/14] [L0] core.endpoint.endpoint:: Starting S3 HTTPS 443
[nsfs/14] [L0] core.endpoint.endpoint:: Started S3 HTTPS successfully

When it works fine (HTTP enable) the logs are:

[Endpoint/145] [L0] core.endpoint.endpoint:: Starting S3 HTTP 80
[Endpoint/145] [L0] core.endpoint.endpoint:: Started S3 HTTP successfully
[Endpoint/145] [L0] core.endpoint.endpoint:: Starting S3 HTTPS 443
[Endpoint/145] [L0] core.endpoint.endpoint:: Started S3 HTTPS successfully

@shirady shirady merged commit 06515f2 into noobaa:master Jan 3, 2024
9 checks passed
@shirady shirady deleted the change-dbg-level branch January 3, 2024 09:24
@shirady shirady changed the title NC | NSFS | Change Debug Level of a Message HTTP Not Enabled NSFS | NC | Change Debug Level of a Message HTTP Not Enabled Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants