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

When connection fails the event file is not getting renamed with failure status #8648

Open
ramya-c3 opened this issue Jan 6, 2025 · 0 comments
Labels

Comments

@ramya-c3
Copy link

ramya-c3 commented Jan 6, 2025

Environment info

  • NooBaa Version: 4.18
  • Platform: standalone

Actual behavior

1.If the connection file is not reachable then the event file is not getting renamed. It appears in logs

·   Jan  6 11:27:19 test node[1123933]: 2025-01-06 11:27:19.159734 [PID-1123933/TID-1123933] [L1] FS::FSWorker::Begin: Rename _old_path=/mnt/cesSharedRoot/ces/s3-config/notifications_log/test-22_notification_logging.failure.log _new_path=/mnt/cesSharedRoot/ces/s3-config/notifications_log/test-22_notification_logging.failure.1736159239159.log

Expected behavior

  1. it should rename the file as specified in case of failure

Steps to reproduce

More information - Screenshots / Logs / Other output

@ramya-c3 ramya-c3 added the NS-FS label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant