Comment 5 for bug 1734148

In Autopkgtest env it fails in 5/5 last runs, but it isn't reproducible in a s390x VM.

autopkgtest [12:09:59]: test command6: debian/tests/run-ocft named
autopkgtest [12:09:59]: test command6: [-----------------------
Making 'named':
    - case 0: check base env
    - case 1: check base env: invalid 'OCF_RESKEY_named'
    - case 2: normal start
    - case 3: normal stop
    - case 4: double start
    - case 5: double stop
    - case 6: running monitor
    - case 7: not running monitor
    - case 8: unimplemented command
    - case 9: non-existent user
Initializing 'named' ...
Starting bind9 (via systemctl): bind9.service.
Stopping bind9 (via systemctl): bind9.service.
Done.

named: check base env - /usr/share/resource-agents/ocft/caselib: line 83: 3227 Terminated setsid $aroot/$agent $cmd > /tmp/.ocft_runlog 2>&1
ERROR: The agent was hanging, killed it, maybe you damaged the agent or system's environment, see details below:
ocf-exit-reason:named didn't answer properly for localhost.
2017/11/22_12:10:12 ERROR: Expected: 127.0.0.1.
2017/11/22_12:10:12 ERROR: Got: ;; connection timed out; no servers could be reached

named: check base env: invalid 'OCF_RESKEY_named' - ERROR: './named monitor' failed, the return code is 1.
named: normal start - ERROR: './named monitor' failed, the return code is 1.
named: normal stop - ERROR: './named monitor' failed, the return code is 1.
named: double start - ERROR: './named monitor' failed, the return code is 1.
named: double stop - ERROR: './named monitor' failed, the return code is 1.
named: running monitor - ERROR: './named monitor' failed, the return code is 1.
named: not running monitor - ERROR: './named monitor' failed, the return code is 1.
named: unimplemented command - ERROR: './named monitor' failed, the return code is 1.
named: non-existent user - ERROR: './named monitor' failed, the return code is 1.

Therefore for this test mask it on s390x.