Add automated test case for OCP-24688#68
Conversation
fbladilo
left a comment
There was a problem hiding this comment.
Can we change these ansible module calls for k8s_facts, k8s_info is not available on ansible-2.8.x (RHEL7.x)
|
@hu-weihua Also could you briefly describe the test logic on the PR, I don't seem to have access to the reference... |
|
@fbladilo Thank you for all you comments.
If you have any other question or comment, feel free to let me know, Thanks again. |
| @@ -0,0 +1,16 @@ | |||
| - name: get all storageclasses infornamtion of migration target cluster | |||
| @@ -0,0 +1,88 @@ | |||
| - name: get all storageclasses infornamtion of migration target cluster | |||
There was a problem hiding this comment.
small typo also in information
| state: absent | ||
| when: source_cluster_sc_name_list_tmp_file is defined | ||
|
|
||
| - name: sleep a while to wait configuration working |
There was a problem hiding this comment.
We could use the pause module with seconds 60 on this instead of calling the shell module, ideally we would check for the condition expected in a loop with retries perhaps until it is satisfied....
|
@hu-weihua Thanks for the revision, I added some other minor comments since last review. I tested the PR on a 3.11 source and 4.2 target (using CAM v1.0.1) , the first run was successful on both source and destination. The second time, it failed retrying on the destination cluster , see below : Something is probably not cleaned up correctly on the target deploy/validation, it exhibits the issue when it is run the second consecutive time, you should be able to reproduce just by running twice on the destination/target cluster : ansible-playbook e2e_mig_samples.yml -t ocp-24688-storageclasses -e with_deploy=false |
|
@hu-weihua Let me know how to proceed with this one, I made another revision back in Feb with some comments/experience with it. |
|
@fbladilo Thanks a lot for your valuable comments and sorry to reply later. I have updated the typos and replaced But I did not hit your problem pasted above. I rerun the test in same test environment many times without below error. My test result in target cluster |
This pull request is used to automate test case OCP-24688