Warning messages on active indexes

[iam432]

What steps did you take and what happened:
Recently upgraded velero to version 6.0.0 and observing warning messages in pod logs and it looks awkward.

What did you expect to happen:
No warning messages

time="2024-03-07T13:50:21Z" level=warning msg="active indexes [xn0_0cd4c40b76073ec11866705b279b9de7-scb1d1eb207f53930987-g3 xn0_15460a29072c4117a265f4ef4719988f-s24646034027c3c89987-g3 xn0_1b700b5b851ce798d0e4b9e0c4e8c189-s27f5d0358aede486987-g3 xn0_1dd957f6068a4e29c26d4c80d77d4b1c-s6906a0697cd97015987-g3 xn0_337c75de1430e8f71f2f93a53c656a90-s4821d8aba9f2248a987-g3 xn0_38e4a32a2c06b61b7a3b576ded95d92e-se7895e12b9227c90987-g3 xn0_522e40140ef7237abd6a1b7e79064de8-s2bcdbde61df9d12a987-g3 xn0_5b81ed4567faa19a8339e3e2c4537d3c-s1d9b73a301ae1853987-g3 xn0_6cd2b802075d2617d28cb52650e7ae79-sfaa21336a1121247987-g3 xn0_6e0a2706aca4bd22007183a5a0bee79d-s8c6925eaf186829f987-g3 xn0_7035533450862ecc9412b6fe17f2f281-se77e7e86952cfe09987-g3 xn0_921d7ac6ac22e950f9c3abc00fb7db37-sb1ceda728d3014f4987-g3 xn0_95868d12969279093139404dfa2c59c7-se0d8af9eb3edf87d987-g3 xn0_9ac4e7fe01eebdc4f944453f3facfb58-sf3b35c0512222d8c987-g3 xn0_aaeb311c4d659366aa48e896ce1918ff-sb9a7cb79957e2878987-g3 xn0_b82ee44cf18e8ca6f7b33cf1eba41b85-sca40745f17318ffd987-g3 xn0_bb40bfb298e75403b7727aee5dd4168b-scca3f59f2ffb5fdc987-g3 xn0_c69a8f20343654e650d71c7c951f7433-s94346bde4d7c9214987-g3 xn0_d2d3f7dd26dce0d97f8bc845e539222a-s05a51bcf2cae76e9987-g3 xn0_d4e9a59f5ea8ad748da2f4e836c23661-s9d32ef39275f09a6987-g3 xn0_f4dbc56b002c9c770903e904aa747190-sfddd24221a56e840987-g3 xn1_0e652104f2fb6afe404c21de543353ed-s31e4a0390ea3d2b9987-g3 xn1_13e7bbd595b20cbd94cf3e20ec3e7ee9-sdf18a50cde7bd4bd987-g3 xn1_20b908795a227f3cb896b0593d95e05d-s6fbec2a06986e671987-g3 xn1_22509b4dd3e4243035b6eebb1a47a0a2-s1ca250892702db89987-g3 xn1_62d7676e891888f47de3b19eabc326fd-se2c932aa871c853d987-g3 xn1_6795beb71e8387a2aafc9772c2126de1-s0b04effef5a7cebf987-g3 xn1_96f08063d8c20783f77eece4320e5068-sa869a395e7c5e426987-g3 xn1_a320a513078e57a23309150150e71a55-s9400b6614669f18a987-g3 xn1_cd6ba0fe64b878b830103ec8c8dc588d-se97e6d30a3d723ec987-g3 xn1_d58b90a7ce7516fbd07e7ee54f33fb21-se416896cee4cb54a987-g3 xn1_df96f736a10f96ef10fd610090b5ca91-s25d98efa5e1a48f1987-g3 xn1_ef2b1f5dc6afb681a310b6c6dc461b8f-s213c155e27489a04987-g3] deletion watermark 2024-03-06 08:26:18 +0000 UTC" backup=velero/daily-backup-20240307130637 controller=podvolumebackup logModule=kopia/kopia/format logSource="pkg/kopia/kopia_log.go:101" logger name="[index-blob-manager]" podvolumebackup=velero/daily-backup-20240307130637-abcfd sublevel=error

Anything else you would like to add:
No

Environment:

• helm version (use helm version): v3.13.1
• helm chart version and app version (use helm list -n <YOUR NAMESPACE>): velero-1.0.0
• Kubernetes version (use kubectl version): v4.5.7
• Kubernetes installer & version: 1.26.12
• Cloud provider or hardware configuration: Azure
• OS (e.g. from /etc/os-release):Ubuntu-2204gen2containerd

[jenting]

Please help file this issue to velero repo, this repo is dedicated for helm chart, thanks.