Add details for latest RU and code fixes for errors faced #79
Conversation
…ays the latest RU is installed
…le from GCS to BMS host if an older file with the same patch number (p6880880_<>.zip) exists in bms host
Thanks for the review - the thought of creating multiple PRs crossed my mind, but I have changed these 4 files in a single branch during my testing in cloudVM (control node) and would need to cherry pick them into new branches (as PR is only possible on an entire branch and not commits within that branch). I will take this lesson forward into the future for sizeable PRs. |
…link 3)comments in gcscopy.yml
…th file changes tested successfully
roles/patch/tasks/patch_vars.yml
Outdated
| # limitations under the License. | ||
|
|
||
| --- | ||
| - name: Patch | include defaults |
There was a problem hiding this comment.
roles/patch/meta/main.yml includes a dependency on common
dependencies:
- { role: common }
So this step should be unnecessary
roles/patch/tasks/patch_vars.yml
Outdated
| include_vars: | ||
| file: roles/common/defaults/main.yml | ||
|
|
||
| - name: Patch | Get the highest version number from gi_patches array |
There was a problem hiding this comment.
nit: patch should be lowercase
patch.yml
Outdated
| - include_role: | ||
| name: patch | ||
| tasks_from: patch_vars.yml | ||
| tags: populate_variables |
There was a problem hiding this comment.
Call it patch_vars for consistency maybe? I'll have a related comment inside patch_vars.yml
Adding code fixes and JAN/APR 2021 RU details.
Will add in-line comments (in each file changed) next week for each of the files submitted for review with detailed error message that necessitated that particular code change and the successful testing of the fix.