-
Notifications
You must be signed in to change notification settings - Fork 164
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: wait until scp is applied (re-created PR) #504
fix: wait until scp is applied (re-created PR) #504
Conversation
SCP import is failing with HTTP and HTTPS share when job_wait=true. Checked on iDRAC8 and iDRAC9 Task output: fatal: [idrac]: FAILED! => { PLAY RECAP ******************************************************************************************************************************** |
Hi @rajshekarp87
Would you kindly check if the scp file is a valid one since the message says "Unable to parse json"? |
Hi @satoshi-tokyo, |
@rajshekarp87 Thanks for checking. We use only NFS but added handling of http.
|
2a83a8b
to
7d33082
Compare
fix: add idrac_redfish_job_tracking for http share
7d33082
to
2e50239
Compare
The UT's are failing because of some changes in devl. Will be merging this and we will take care of this to checkout stable branches in the next PR releases. |
Description
Use idrac_redfish_job_tracking in
module_utils/utils.py
to track job progress so that ansible playbook completes after iDRAC SCP import job is actually completed when "job_wait: True".GitHub Issues
List the GitHub issues impacted by this PR:
ISSUE TYPE
COMPONENT NAME
idrac_server_config_profile.py
OUTPUT
ADDITIONAL INFORMATION
Tested on PowerEdge R650, iDRAC firmware version: 6.10.30.00
Please note that this was based on a fork from v7.4.0.
I checked diff on the below files which are related to my change, between v7.4.0 and my branch, and confirmed that there is no other possible changes.
Checklist: