[LU-16909] rolling-upgrade/downgrade interop: sanity test_805: DoM not working

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.15.3
• Labels: ZFS
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for sarah <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/ea1fe5ee-03b6-4d33-9cab-ceba8caaac1a

test_805 failed with the following error:

DoM not working

Test session details:
clients: https://build.whamcloud.com/job/lustre-b2_12/164 - 3.10.0-1160.49.1.el7.x86_64
servers: https://build.whamcloud.com/job/lustre-b2_15/64 - 4.18.0-425.3.1.el8_lustre.x86_64

CMD: trevis-64vm4 zfs get -H quota lustre-mdt1/mdt1
CMD: trevis-64vm4 lctl get_param -n osd-zfs.lustre-MDT0000..kbytesfree
CMD: trevis-64vm4 lctl get_param -n osd-zfs.lustre-MDT0000..kbytestotal
CMD: trevis-64vm4 zfs set quota=102637568 lustre-mdt1/mdt1
lfs setstripe: cannot set default composite layout for '/mnt/lustre/d805.sanity': File too large
 sanity test_805: @@@@@@ FAIL: DoM not working 

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_805 - DoM not working

Comments

[Andreas Dilger]

I checked back 6 months and this is only failing with rolling-upgrade-mds-zfs and rolling-downgrade-client1-zfs (old 2.12 client, new ZFS MDS) though I haven't looked at why that is the case. The first failure was 2023-03-24, but this was the first time that rolling upgrade was run, so I think the problem predates this time and is not related to a bad patch landing at that time. The failure is not hit with 2.14.0-2.15.x rolling-upgrade-mds-zfs testing, so it looks like the issue was introduced sometime in the 2.13 or 2.14 development cycle.