Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-678

Operator failing smoke tests (6.2.0 / release-0.2)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • MTA 6.2.0
    • MTA 6.2.0
    • Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • No

      On a fresh new install in OCP v4.12 , operator fails to reconcile with :

       

       

      --------------------------- Ansible Task StdOut -------------------------------
       TASK [Collect database coordinates] ******************************** 
      fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: list object has no element 0\n\nThe error appears to be in '/opt/ansible/roles/tackle/tasks/main.yml': line 246, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n    - name: \"Collect database coordinates\"\n      ^ here\n"}
      

       

      Description of problem:

      It seems like some req var is not getting set in the collect database coordinates task

       

      [fbladilo@fdev:/tmp]$ oc describe tackle
      Name:         mta
      Namespace:    openshift-mta
      Labels:       <none>
      Annotations:  <none>
      API Version:  tackle.konveyor.io/v1alpha1
      Kind:         Tackle
      Metadata:
        Creation Timestamp:  2023-05-30T15:15:17Z
        Generation:          1
        Managed Fields:
          API Version:  tackle.konveyor.io/v1alpha1
          Fields Type:  FieldsV1
          fieldsV1:
            f:metadata:
              f:annotations:
                .:
                f:kubectl.kubernetes.io/last-applied-configuration:
            f:spec:
              .:
              f:cache_storage_class:
              f:keycloak_sso_req_passwd_update:
              f:rwx_supported:
          Manager:      kubectl-client-side-apply
          Operation:    Update
          Time:         2023-05-30T15:15:17Z
          API Version:  tackle.konveyor.io/v1alpha1
          Fields Type:  FieldsV1
          fieldsV1:
            f:status:
              .:
              f:conditions:
          Manager:         ansible-operator
          Operation:       Update
          Subresource:     status
          Time:            2023-05-30T15:28:30Z
        Resource Version:  308345226
        UID:               08dc9b28-5573-4f0f-9400-b579c166e13e
      Spec:
        cache_storage_class:             nfs
        keycloak_sso_req_passwd_update:  false
        rwx_supported:                   true
      Status:
        Conditions:
          Last Transition Time:  2023-05-30T15:15:47Z
          Message:               
          Reason:                
          Status:                False
          Type:                  Successful
          Last Transition Time:  2023-05-30T15:28:03Z
          Message:               Running reconciliation
          Reason:                Running
          Status:                False
          Type:                  Running
          Ansible Result:
            Changed:             0
            Completion:          2023-05-30T15:28:30.446556
            Failures:            1
            Ok:                  8
            Skipped:             28
          Last Transition Time:  2023-05-30T15:28:30Z
          Message:               The task includes an option with an undefined variable. The error was: list object has no element 0
      The error appears to be in '/opt/ansible/roles/tackle/tasks/main.yml': line 246, column 7, but may
      be elsewhere in the file depending on the exact syntax problem.
      The offending line appears to be:
          - name: "Collect database coordinates"
            ^ here
          Reason:  Failed
          Status:  True
          Type:    Failure
      Events:      <none>
      

       

      Version-Release number of selected component (if applicable):

       MTA 6.2.0 operator synced with release-0.2 branch

      How reproducible:

       Always

      Steps to Reproduce:
      1. Attempt to deploy a fresh new install with Tackle CR : feature_auth_required true and feature_auth_type set to keycloak (rwx_supported is also set true but I don't think it is affecting this issue)

      Actual results:

       Failure

      Expected results:

       Reconcile succesfully

      Additional info:

            rhn-engineering-jmontleo Jason Montleon
            fbladilo@redhat.com Franco Bladilo
            Igor Braginsky Igor Braginsky
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: