gbmc-release-23.18.x: nvmesensor: hack to avoid huge amount of VF

This patch only include one line code change. `index++;` -> `break;`

nvmesensor created too much VF(secondary) controllers DBus objects
even when most of those VF controllers are offline state.  The
creation of those DBus objects will make xyz.openbmc_project.ObjectMapper
slow or even timeout when response to other component of BMC.

This is a release branch only patch to meet the urgent timeline.
In master branch, we will solve this issue more gracefully by
moderate code change.

Tested:
Power cycle and check host bootnum passed 20 loops:
https://paste.googleplex.com/4562061991346176?raw

OOB test without VF controllers:
https://fusion2.corp.google.com/ci/guitar/workflows/%2F%2Fplatforms%2Fgbmc%2Fmtest%2Fintegration_test:izumi_ironfist_nightly_regression/activity/f88f8744-6e28-300b-88bb-c5ad3b607fb7:0/phases
(The failure tests already failed on `23.18.48.0`)

Google-Bug-Id: 301462811
Google-Bug-Id: 298022427
Change-Id: I46fe34c703ca739c0dac668ccf70ec0b372a0664
Signed-off-by: Jinliang Wang <jinliangw@google.com>
2 files changed
tree: cf2fb0a2e7b667ab1ae560457f4b86b0db8814b7
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-devtools/
  7. recipes-extended/
  8. recipes-google/
  9. recipes-kernel/
  10. recipes-phosphor/
  11. LICENSE
  12. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.