NuGet packages missing from TeamCity NuGet feed

Hello,

I recently upgraded from TeamCity 2017.2.3 to 2018.1 (build 58245). Since the upgrade, we've noticed that some packages built by 2018.1 are not visible in the internal TeamCity NuGet feed, while others are - even within the same build. We did not observe this behavior on 2017.2.3.

My observations:

1. One package affected by this problem is called "JDICM". "JDICM" revision 26333 was built by 2017.2.3 and is visible in the NuGet feed and in the TeamCity UI. "JDICM" revision 26388 was built by 2018.1 and is NOT visible in the NuGet feed but IS visible in the TeamCity UI.
2. One package unaffected by this problem is called "JDICheckPrint". "JDICheckPrint" revision 26333 was built by 2017.2.3 and is visible in the NuGet feed and in the TeamCity UI. "JDICheckPrint" revision 26388 was built by 2018.1 and IS visible in the NuGet feed and is visible in the TeamCity UI.
3. Please note that 26388 is not the only problematic revision. TeamCity will not list any "JDICM" package AFTER revision 26333.
4. My NuGet feed is configured as v2

Here's what I tried - no affect on the problem:

1. Restarting TeamCity
2. I tried resetting the "buildsMetadata" cache. I also looked at teamcity-nuget.log and did NOT see "JDICM" rev 26388 getting indexed.
3. I tried querying the TeamCity NuGet feed directly using a web browser (taking everything but TeamCity out of the equation) and observed the same behavior.

Attachments:

1. "Figure_1.png" illustrates what revision 26388 looks like in TeamCity 2018.1
2. "Figure_2.png" shows an excerpt of TeamCity's response to the following request: /httpAuth/app/nuget/feed/_Root/default/v2/FindPackagesById()?id='JDICheckPrint'. Notice that "JDICheckPrint" rev 26388 is present. This is the behavior I would expect. I executed the same HTTP request, changing "JDICheckPrint" to "JDICM" and did NOT see an JDICMrev 26388 in the XML document that TeamCity responded with. I tried to upload the actual XML file, but I am only permitted to attach images.
3. "Figure_3.png" shows that the permissions of rev 26333 and 26388 are identical.