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

Verify automation process to run macOS tests on PSI #4408

Closed
2 tasks
anandrkskd opened this issue Feb 5, 2021 · 19 comments
Closed
2 tasks

Verify automation process to run macOS tests on PSI #4408

anandrkskd opened this issue Feb 5, 2021 · 19 comments
Assignees
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).

Comments

@anandrkskd
Copy link
Contributor

anandrkskd commented Feb 5, 2021

/kind user-story

User Story

As a QE I want to analyse/research and automate macOS test on PSI.

Acceptance Criteria

  • Mention the steps needed for automation
  • Automate the process of test

Links

/kind user-story

@openshift-ci-robot openshift-ci-robot added the kind/user-story An issue of user-story kind label Feb 5, 2021
@prietyc123 prietyc123 added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Feb 5, 2021
@anandrkskd
Copy link
Contributor Author

anandrkskd commented Feb 10, 2021

Below are some steps needed to be done to move Tests on macOS :
**Automation steps **

  • Divide setup & run script, make changes if required to be mac friendly
  • create 2 prow job configuration
    • unit test
    • e2e test
  • create 2 jenkins job
    • unit test
    • e2e test
  • 2 amqp send queue
    • unit test
    • e2e test
  • Configure each Jenkins job according to send queues
  • Create Nodessh file for mac

@dharmit dharmit added the estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person label Feb 10, 2021
@anandrkskd
Copy link
Contributor Author

Jobs on MacOS are failing while tests are executed using script due to

  • unable to find go
  • unable to resolve github
  • failing to download OC, and more network related issue

Need to check why tests are getting triggered, when it is not involved in the release repo.

@dharmit
Copy link
Member

dharmit commented Apr 14, 2021

  • Unit tests are done (tried this on PSI)
  • e2e & integration tests being tested on Jenkins.
  • macOS unit test need a PR on openshift/release repo.

@anandrkskd
Copy link
Contributor Author

Running e2e & integration tests on Jenkins fails due to n/w bandwidth issue as it is not able to download oc binary within timeout of 210 seconds, As discussed with Tomas we will use a pre-downloaded oc binary for the e2e test.

@anandrkskd
Copy link
Contributor Author

anandrkskd commented May 5, 2021

scope for sprint 201:

  • failure on fix operatorhub tests and e2e tests

@anandrkskd
Copy link
Contributor Author

anandrkskd commented May 21, 2021

@anandrkskd
Copy link
Contributor Author

Scope for sprint 201:

  • Ensure parallel run on mac and windows don't fail due to resource
  • Create PR on release repo to start testing on PRs

@anandrkskd
Copy link
Contributor Author

anandrkskd commented Jul 8, 2021

Scope of the issue:

@dharmit dharmit added estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person and removed estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person labels Jul 8, 2021
@anandrkskd
Copy link
Contributor Author

anandrkskd commented Jul 26, 2021

@dharmit
Copy link
Member

dharmit commented Jul 27, 2021

What I understood in the Triage call was that we will set things up on PSI till IBM Cloud is ready for switchover. Waiting for #4944 & #4800 would mean we have to wait for majority of the Sprint.

@anandrkskd
Copy link
Contributor Author

What I understood in the Triage call was that we will set things up on PSI till IBM Cloud is ready for switchover.

yes, but in terms of scripts or setting up PSI it's already done. we just facing this #3256 issue.

@prietyc123 prietyc123 added milestone/2.4 priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). labels Aug 12, 2021
@anandrkskd
Copy link
Contributor Author

anandrkskd commented Aug 18, 2021

Acceptance criteria

  • create job on prow for mac test
  • Create a file for reference of Ibmcloud varriable
  • update IBMCloud vars on Jenkins

@anandrkskd
Copy link
Contributor Author

anandrkskd commented Sep 20, 2021

while running test on ibm cloud openshift cluster we are facing error FailedMount.
checking pod with

oc describe pods -n cmd-devfile-url-test241zed
Name:           qwbeou-app-9d9b8dc57-vbzmc
Namespace:      cmd-devfile-url-test241zed
Priority:       0
Node:           10.243.0.13/10.243.0.13
Start Time:     Mon, 20 Sep 2021 16:29:07 +0530
Labels:         app=app
                app.kubernetes.io/instance=qwbeou
                app.kubernetes.io/managed-by=odo
                app.kubernetes.io/managed-by-version=v2.3.1
                app.kubernetes.io/name=
                app.kubernetes.io/part-of=app
                component=qwbeou
                pod-template-hash=9d9b8dc57
Annotations:    openshift.io/scc: restricted
Status:         Pending
IP:             
IPs:            <none>
Controlled By:  ReplicaSet/qwbeou-app-9d9b8dc57
Init Containers:
  copy-supervisord:
    Container ID:  
    Image:         registry.access.redhat.com/ocp-tools-4/odo-init-container-rhel8:1.1.10
    Image ID:      
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/cp
    Args:
      -r
      /opt/odo-init/.
      /opt/odo/
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /opt/odo/ from odo-supervisord-shared-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-sl5hz (ro)
Containers:
  tools:
    Container ID:  
    Image:         quay.io/eclipse/che-java11-maven:next
    Image ID:      
    Port:          9090/TCP
    Host Port:     0/TCP
    Command:
      tail
    Args:
      -f
      /dev/null
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      memory:  768Mi
    Requests:
      memory:  768Mi
    Environment:
      PROJECTS_ROOT:   /projects
      PROJECT_SOURCE:  /projects
    Mounts:
      /data/cache/.m2 from springbootpvc-qwbeou-app-vol (rw)
      /projects from odo-projects (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-sl5hz (ro)
  runtime:
    Container ID:  
    Image:         quay.io/eclipse/che-java11-maven:next
    Image ID:      
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      /opt/odo/bin/supervisord
    Args:
      -c
      /opt/odo/conf/devfile-supervisor.conf
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Limits:
      memory:  768Mi
    Requests:
      memory:  768Mi
    Environment:
      PROJECTS_ROOT:                /projects
      PROJECT_SOURCE:               /projects
      ODO_COMMAND_RUN:              mvn -Dmaven.repo.local=/data/cache/.m2/repository spring-boot:run
      ODO_COMMAND_RUN_WORKING_DIR:  /projects
    Mounts:
      /data/cache/.m2 from springbootpvc-qwbeou-app-vol (rw)
      /opt/odo/ from odo-supervisord-shared-data (rw)
      /projects from odo-projects (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-sl5hz (ro)
Conditions:
  Type              Status
  Initialized       False 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  springbootpvc-qwbeou-app-vol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  springbootpvc-qwbeou-app
    ReadOnly:   false
  odo-projects:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  odo-supervisord-shared-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  default-token-sl5hz:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-sl5hz
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason              Age                  From                     Message
  ----     ------              ----                 ----                     -------
  Warning  FailedScheduling    63m                  default-scheduler        0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling    63m                  default-scheduler        0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
  Normal   Scheduled           62m                  default-scheduler        Successfully assigned cmd-devfile-url-test241zed/qwbeou-app-9d9b8dc57-vbzmc to 10.243.0.13
  Warning  FailedAttachVolume  50m (x6 over 60m)    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-62cbf6e1-c5fb-4e6d-bd50-2c8fcb35b34c" : attachdetachment timeout for volume r010-3fe2b73f-fd07-40dc-9039-524b2c36a05a
  Warning  FailedMount         46m (x3 over 60m)    kubelet                  Unable to attach or mount volumes: unmounted volumes=[springbootpvc-qwbeou-app-vol], unattached volumes=[default-token-sl5hz odo-projects springbootpvc-qwbeou-app-vol odo-supervisord-shared-data]: timed out waiting for the condition
  Warning  FailedAttachVolume  37m (x8 over 49m)    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-62cbf6e1-c5fb-4e6d-bd50-2c8fcb35b34c" : rpc error: code = Internal desc = {RequestID: 2c9c7378-84ef-48e1-902a-858fce1e2355 , Code: InternalError, Description: Internal error occurred, BackendError: {Code:VolumeAttachFailed, Type:AttachFailed, Description:The volume ID 'r010-3fe2b73f-fd07-40dc-9039-524b2c36a05a' could not be attached to the instance ID 'kube-c3teebof0t4eae9po0ag-devtools14v-devtool-00000247'., BackendError:P4053: The 'vpc-gen2' infrastructure operation failed with the message: Internal server error, RC:500}, Action: Please check 'BackendError' tag for more details}

need help in debugging this problem

@anandrkskd
Copy link
Contributor Author

I think we can close this issue as we are moving to IBM cloud pipelines

@anandrkskd
Copy link
Contributor Author

/close

@openshift-ci
Copy link

openshift-ci bot commented Nov 8, 2021

@anandrkskd: Closing this issue.

In response to this:

/close

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/test-infra repository.

@openshift-ci openshift-ci bot closed this as completed Nov 8, 2021
@kadel
Copy link
Member

kadel commented Nov 9, 2021

I think we can close this issue as we are moving to IBM cloud pipelines

where are we going to run MacOS tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants