| [cbi-dev] Is anyone else seeing warning about "[FailedMount] MountVolume.SetUp failed for volume "kube-api-access-7s2lh" : failed to sync configmap cache: timed out waiting for the condition" in Eclipse CI job output? |
From ci.eclipse.org/jakartaee-tck [1], I am seeing [2]. Since we are in the middle of a major development cycle, I have no idea if the test failures that occur after that point are related or not. I also do not know if they are new.
What is the impact of the failed mount for "kube-api-access-"
volumes? Could it be that we need the patches mentioned in [3]?
Scott
[1]
https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1767/consoleText
[2]
[Warning][jakartaee-tck/jakartaee-tck-pod-e6e7e126-1bd1-47db-bcd1-5ac4abcc8265-11-v6kdh][FailedMount]
MountVolume.SetUp failed for volume "kube-api-access-7s2lh" :
failed to sync configmap cache: timed out waiting for the
condition
[Warning][jakartaee-tck/jakartaee-tck-pod-e6e7e126-1bd1-47db-bcd1-5ac4abcc8265-11-j0jcb][FailedMount]
MountVolume.SetUp failed for volume "kube-api-access-kpljv" :
failed to sync configmap cache: timed out waiting for the
condition
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1999325