Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-729 DataMover: exec restore hooks are failing
  3. OADP-910

[IBM QE-Z] Verify Bug OADP-729 - DataMover: exec restore hooks are failing

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

      Description of problem: exec restore hooks are failing. Restore is completed successfully although `onError: Fail`` is set, but the expected behavior in which it will execute the command `mysql -u root -e source /var/lib/mysql/world.sql` and then a schema called world should exist is not satisfied.

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

      How reproducible: 100%

      Steps to Reproduce:
      https://polarion.engineering.redhat.com/polarion/redirect/project/OADP/workitem?id=OADP-196

       

      Actual results:

      https://reportportal-migration-qe.apps.ocp-c1.prod.psi.redhat.com/ui/#oadp/launches/all/2010/52191/log?item0Params=filter.eq.hasStats%3Dtrue%26filter.eq.hasChildren%3Dfalse%26filter.in.issueType%3Dti001

       oc -n mysql-persistent rsh $(oc get pods -n mysql-persistent -o name) mysql -uroot world -e "show tables;" returns `ERROR 1049 (42000): Unknown database 'world'`

      Expected results:

      database world should appear and the command should not return an error

       

      Additional info:

              mayaanilson Maya Anilson (Inactive)
              mperetz@redhat.com Maya Peretz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: