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

Fix ansible deprecation warnings #1491

Open
lentzi90 opened this issue Jan 15, 2025 · 5 comments · May be fixed by #1492
Open

Fix ansible deprecation warnings #1491

lentzi90 opened this issue Jan 15, 2025 · 5 comments · May be fixed by #1492
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@lentzi90
Copy link
Member

We have some warnings from ansible in our periodic jobs:

 [DEPRECATION WARNING]: Use 'ansible.utils.nthhost' module instead. This feature
  will be removed from ansible.netcommon in a release after 2024-01-01. 
 Deprecation warnings can be disabled by setting deprecation_warnings=False in 
 ansible.cfg.
 [DEPRECATION WARNING]: Use 'ansible.utils.ipaddr' module instead. This feature 
 will be removed from ansible.netcommon in a release after 2024-01-01. 
 Deprecation warnings can be disabled by setting deprecation_warnings=False in 
 ansible.cfg.
 [WARNING]: The value '' is not a valid IP address or network, passing this
 value to ipaddr filter might result in breaking change in future.
 [DEPRECATION WARNING]: Use 'ansible.utils.ipv4' module instead. This feature 
 will be removed from ansible.netcommon in a release after 2024-01-01. 
 Deprecation warnings can be disabled by setting deprecation_warnings=False in 
 ansible.cfg.

It would be nice to fix these before they break the tests.
The logs above are from https://jenkins.nordix.org/view/Metal3%20Periodic/job/metal3-periodic-dev-env-integration-test-ubuntu-main/

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jan 15, 2025
@Rozzii
Copy link
Member

Rozzii commented Jan 15, 2025

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jan 15, 2025
@Rozzii
Copy link
Member

Rozzii commented Jan 15, 2025

/kind bug
/help

@metal3-io-bot
Copy link
Collaborator

@Rozzii:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/kind bug
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@metal3-io-bot metal3-io-bot added kind/bug Categorizes issue or PR as related to a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 15, 2025
@elfosardo elfosardo linked a pull request Jan 15, 2025 that will close this issue
@elfosardo
Copy link
Member

/assign

@tuminoid
Copy link
Member

Also ipmath and ipwrap are netcommon deprecated.

00:23:36.174  [DEPRECATION WARNING]: Use 'ansible.utils.ipmath' module instead. This feature 
00:23:36.174  will be removed from ansible.netcommon in a release after 2024-01-01. 
00:23:58.451  [DEPRECATION WARNING]: Use 'ansible.utils.ipwrap' module instead. This feature 
00:23:58.451  will be removed from ansible.netcommon in a release after 2024-01-01. 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants