python-common: drive_selection: fix KeyError when osdspec_affinity is not set#52532
python-common: drive_selection: fix KeyError when osdspec_affinity is not set#52532
Conversation
|
|
jenkins test make check |
1 similar comment
|
jenkins test make check |
|
@ljflores jobs are failing with the following error |
@guits that looks like https://tracker.ceph.com/issues/59142, which was merged to main. Is your branch on the latest commit? |
… not set When osdspec_affinity is not set, the drive selection code will fail. This can happen when a device has multiple LVs where some of are used by Ceph and at least one LV isn't used by Ceph. Fixes: https://tracker.ceph.com/issues/58946 Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
just rebased, thanks 🙂 |
|
@ljflores the fix for https://tracker.ceph.com/issues/59142 was merged 3 months ago, my branch was created only a few days ago so that fix was already present in my branch. That being said, it is still failing |
@guits can you link to the still-failing tests? All I can see are the ones that were scheduled on the non-rebased branch. I see this link https://pulpito.ceph.com/gabrioux-2023-08-10_21:20:10-orch:cephadm-wip-guits-testing-5-2023-08-10-1324-distro-default-smithi/ as well, but I don't see the dashboard test that runs into this failure |
|
I scheduled some fresh runs here: This branch is based on the tip of main. Here's also the same tests run on plain main for comparison: |
|
Okay, I studied the two runs, and they are both exhibiting a new, unrelated bug which I tracked here: https://tracker.ceph.com/issues/62491 Since the failure occurs in both before we can get to the spec file that concerns this bug, it makes it difficult to evaluate this fix. @ceph/dashboard can you help us out here? TL;DR is that @guits has a fix for one of the spec files, but a new bug tracked above fails the test before we can get to the original point of failure. Is there a way we can isolate this spec file locally to verify the fix? |
|
jenkins test dashboard |
|
@guits Do you mind rebasing the PR and push it, so it triggers the dashboard e2e jenkins job ( |
|
jenkins test dashboard cephadm |
@avanthakkar I got it to retrigger with |
@ljflores Those are different set of e2es(which are cephadm based). We also need to make sure if dashboard e2e are passing |
|
jenkins test dashboard cephadm |
|
Rebuilding here on the tip of main, which includes #53141. Running some tests here: http://pulpito.front.sepia.ceph.com/lflores-2023-08-25_16:17:14-rados-wip-lflores-testing-2-2023-08-25-1435-distro-default-smithi/ The tests failed again due to another unrelated dashboard failure, but this time the affected spec file has progressed past host assignment, where it failed previously. With the fix: W/o the fix: |
When osdspec_affinity is not set, the drive selection code will fail. This can happen when a device has multiple LVs where some of are used by Ceph and at least one LV isn't used by Ceph.
Fixes: https://tracker.ceph.com/issues/58946