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

Backport/2.7/51898 #52100

Merged
merged 4 commits into from
Mar 19, 2019
Merged

Backport/2.7/51898 #52100

merged 4 commits into from
Mar 19, 2019

Conversation

billdodd
Copy link
Contributor

SUMMARY

The commands GetManagerAttributes and SetManagerAttributes reply on an Attributes property in the Manager resource. But this is not a standard property in the Redfish spec; it is a vendor-specific Oem property. Accordingly, these 2 non-standard commands are being removed with this PR. These commands can be added by a vendor in an appropriate Oem extension module if needed.

Fixes #47590

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

redfish_utils.py
redfish_facts.py
redfish_config.py

ADDITIONAL INFORMATION

See issue #47590 for the original behavior. After this PR, the subject commands (GetManagerAttributes and SetManagerAttributes) will no longer be available in the standard modules.

@ansibot
Copy link
Contributor

ansibot commented Feb 12, 2019

@ansibot ansibot added affects_2.7 This issue/PR affects Ansible v2.7 backport This PR does not target the devel branch. bug This issue/PR relates to a bug. community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. remote_management Working Group: https://docs.ansible.com/ansible/latest/community/communication.html support:community This issue/PR relates to code supported by the Ansible community. labels Feb 12, 2019
@abadger
Copy link
Contributor

abadger commented Feb 12, 2019

I do not believe this is eligible for backporting as it is removing module parameters which would break existing playbooks.

to solve the initial bug on the stable release you could make this code conditional such that if the remote does not support the non-standard features we give the user a nice error that says that these parameters cannot be used with this host.

It would also be nice for the users if you added a deprecation warning when they specify the parameters which are going away. That way they can start preparing to change their playbooks in the next release. (via module.deprecate(msg)).

@ansibot ansibot removed the needs_triage Needs a first human triage before being processed. label Feb 12, 2019
@billdodd
Copy link
Contributor Author

Thanks, @abadger

I will work on a new PR that emits the suggested deprecation warning and a nice error in the case that the non-standard feature is not available.

Is the best/standard practice in this type of scenario to (1) keep this PR open and update it or (2) close this one and open a new one?

@abadger
Copy link
Contributor

abadger commented Feb 12, 2019

I think updating the existing PR is probably best. Thanks :-)

@billdodd
Copy link
Contributor Author

Sounds good. Thanks for the feedback.

@ansibot ansibot added the stale_ci This PR has been tested by CI more than one week ago. Close and re-open this PR to get it retested. label Feb 20, 2019
@abadger
Copy link
Contributor

abadger commented Mar 18, 2019

@billdodd Hey, just a note that Ansible-2.8.0 will be out in a little over a month. Once that happens, we will only be backporting critical bugfixes to Ansible-2.7.x. So if you want to get this into a 2.7.x release it needs to be done soon.

@billdodd
Copy link
Contributor Author

@abadger - thanks for the heads-up. I will try to get this in for 2.7.x soon.

@ansibot ansibot removed the stale_ci This PR has been tested by CI more than one week ago. Close and re-open this PR to get it retested. label Mar 19, 2019
@abadger abadger merged commit 1d55f4a into ansible:stable-2.7 Mar 19, 2019
@abadger
Copy link
Contributor

abadger commented Mar 19, 2019

Merged for the 2.7.10 release. Thanks!

@billdodd
Copy link
Contributor Author

Thanks, @abadger!

@ansible ansible locked and limited conversation to collaborators Jul 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.7 This issue/PR affects Ansible v2.7 backport This PR does not target the devel branch. bug This issue/PR relates to a bug. community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. remote_management Working Group: https://docs.ansible.com/ansible/latest/community/communication.html support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants