Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-3985

sanity-hsm test_111b failure: 'request on 0x200000401:0x209:0x0 is not FAILED'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • Lustre 2.6.0, Lustre 2.5.1
    • Lustre 2.5.0, Lustre 2.6.0, Lustre 2.5.1
    • OpenSFS cluster with combined MGS/MDS, single OSS with two OSTs, four clients; one agent (c07), one with robinhood/db running (c08) and just running as Lustre clients (c09, c10)
    • 3
    • 10621

      Test results are at https://maloo.whamcloud.com/test_sets/28e49004-2171-11e3-b1f0-52540035b04c

      From the client test_log:

      == sanity-hsm test 111b: No retry policy (release case), restore will error == 10:55:34 (1379526934)
      pdsh@c10: c07: ssh exited with exit code 1
      Purging archive on c07
      Starting copytool agt1 on c07
      mdt.scratch-MDT0000.hsm.policy=+nra
      Remove from backend: 0x200000401:0x209:0x0 = 
      Changed after 0s: from '' to 'SUCCEED'
      Waiting 100 secs for update
      Waiting 90 secs for update
      Waiting 80 secs for update
      Waiting 70 secs for update
      Waiting 60 secs for update
      Waiting 50 secs for update
      Changed after 60s: from 'SUCCEED' to ''
      Waiting 40 secs for update
      Waiting 30 secs for update
      Waiting 20 secs for update
      Waiting 10 secs for update
      Update not seen after 100s: wanted 'FAILED' got ''
       sanity-hsm test_111b: @@@@@@ FAIL: request on 0x200000401:0x209:0x0 is not FAILED 
      

            jamesanunez James Nunez (Inactive)
            jamesanunez James Nunez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: