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

Deprecation warning for /usr/sbin/bdii-update #53

Closed
marianne013 opened this issue May 16, 2024 · 9 comments · Fixed by #58
Closed

Deprecation warning for /usr/sbin/bdii-update #53

marianne013 opened this issue May 16, 2024 · 9 comments · Fixed by #58

Comments

@marianne013
Copy link
Contributor

Short Description of the issue

This is on a Rocky Linux release 9.4 (Blue Onyx) site bdii installed from epel. The bdii-update.log is filled with depreciation warnings, making it hard to see any real errors. The actual running of the bdii is unaffected.

[root@bdii02 ~]# tail /var/log/bdii/bdii-update.log
/usr/sbin/bdii-update:552: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
  log.warn(line.strip())

Summary of proposed changes

The fix (replace 'warn' by 'warning') is straight forward and gets rid of this spurious error message.

@brucellino
Copy link
Member

Does this affect only that one os or can it be applied across the board?

@marianne013
Copy link
Contributor Author

I believe this is a python issue. 'warn' has been deprecated since 3.3 and 'warning' seems to exist even in 3.0, I think it's save to assume no-one is running python2 any longer.

@brucellino brucellino changed the title Depreciaton warning for /usr/sbin/bdii-update Deprecaton warning for /usr/sbin/bdii-update May 17, 2024
@brucellino
Copy link
Member

Awesome, thanks. Would you like to work on a PR for this? If not, we can do it.

@gwarf gwarf changed the title Deprecaton warning for /usr/sbin/bdii-update Deprecation warning for /usr/sbin/bdii-update May 17, 2024
@marianne013
Copy link
Contributor Author

I'll have a go

@brucellino
Copy link
Member

Thanks @marianne013 -- could you put the PR in draft at first, since I would like to add a test case for this to ensure that we actually do eliminate the warning. I will put it on the same PR you work on so we can merge together.

@marianne013
Copy link
Contributor Author

Why would you need a draft (instead of a standard) pull request for testing ? I mean I can make a draft, but I can't quite see the difference.

@marianne013
Copy link
Contributor Author

Here's the draft:
#58

@brucellino
Copy link
Member

Why would you need a draft (instead of a standard) pull request for testing ? I mean I can make a draft, but I can't quite see the difference.

Just to avoid automerging if tests pass.

Thanks for the PR! Will be in touch soon.

@gwarf gwarf closed this as completed in #58 Jun 10, 2024
gwarf pushed a commit that referenced this issue Jun 10, 2024
# Summary

Replaces log.warn with the python standard log.warning

---

**Related issue :**

fixes #53
@gwarf
Copy link
Member

gwarf commented Jun 17, 2024

Dear @marianne013, a new version for AlmaLinux 9 got released, would be great if you could give it a test and report: https://github.com/EGI-Federation/bdii/releases/tag/v6.0.2
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants