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

Director should not create volume record if storage daemon fails to label the volume #1804

Open
arogge opened this issue May 8, 2024 · 0 comments
Labels
bug This addresses a bug

Comments

@arogge
Copy link
Member

arogge commented May 8, 2024

Bareos component version

current / 23.0.2 and probably every older version

Steps to reproduce

  1. set up an SD with File backend pointing to a non-existent directory
  2. autolabel a volume on that SD

Expected results

Getting an error message from the Storage and no Volume record in the media table.

Actual results

Error message from the Storage is there, but the Director already created a volume record in the catalog for a volume that could not be labeled.

Environment

No response

Relevant log output

No response

Relevant traces output

No response

Anything else?

https://bugs.bareos.org/view.php?id=1598

@arogge arogge added the bug This addresses a bug label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This addresses a bug
Projects
None yet
Development

No branches or pull requests

1 participant