Keyword search on collection set not working for specific sub-collections

Question

I am having the following problem:
When I do a search (Text->Keyword->Contains All-> for a keyword (in my
case "Fave"), it does not work if I select the collection set that contains the
collection that contains the images with that keyword.
It DOES work if I select the folder, parent folder, or just the
collection that contains the image. Just not the collection set.
The details of how this came about are below - and are probably a
little unusual, but not outside the realm of what should be allowed.
Is there a way to reset/reindex keywords in a collection?
Specifically:
images lives in collection C1 which is part of collection set
CS1. It lives in F1 (on disk and in LR) which is in parent folder
PF1. A keyword search works when I select F1 or PF1 or C1, but NOT
when I select CS1
This happens on a set of folders that went through the following
(totally allowable?) sequence:
I am running on a Windows 7 64 bit machine with 64 bit LR3.3
I have an internal disk where I keep my catalog and images. Windows
mounts this as P:. I also mount it on my Desktop as the folder
"Lightroom" (this allows me to change to a larger external disk
by mounting it in the same place without changing the locations of
all the files).
I mistakenly imported pics into P:/PF1 rather than
C:/.../Desktop/Lightroom/PF1 as I normally do.
Added keywords made a collection C1 put the images in it, and added
C1 to collection set CS1
Having realized my import mistake (P: rather than
C:/.../Desktop/Lightroom), I went in the Folders->P: section and did
an Update Folder Location on F1 to C:/.../Desktop/Lightroom/F1
This seemed to be all fine, but this weird Keyword search problem
resulted.
I have tried the following things:
o Deleting and re-adding Keywords in the Collection
o Deleting and re-adding the Keywords in the Folder
o Renaming and relocating the Folder
o Create new collection C2 and move pics from F1 into C2

Answer 1

See my simplified recipe for reproducing this bug (which turns out not to be related to the drive mounting I described):
http://forums.adobe.com/thread/764538