Created attachment 1957957 [details] [video] no secret found while attaching secret to template Description of problem: Clone a template and try to attach existing secret to the template, it does not found any secret even there are existed secrets in current namespace Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. add some secrets to current namespace 2. clone a template 3. add existing secret to the template Actual results: no secret found Expected results: secret from current namespace should be found in the list Additional info:
@gouyang i can see from other clusters that the auto-test-secret resource has an empty key named 'key'. This secret selector filter all the secrets that do not contain a public key using a regular expression.
(In reply to Ugo Palatucci from comment #1) > @gouyang i can see from other clusters that the auto-test-secret > resource has an empty key named 'key'. > > This secret selector filter all the secrets that do not contain a public key > using a regular expression. You can try to create a secret on your own and try again, all secrets are not found never matter whether does it has valid data or not, the problem only happens to template but not VM.
verified on kubevirt-console-plugin-rhel9-container-v4.14.0-1047
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6817