Bug 2182233 - VM cannot be scheduled due to the secret name exceeds 63 characters
Summary: VM cannot be scheduled due to the secret name exceeds 63 characters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.14.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-28 01:43 UTC by Guohua Ouyang
Modified: 2023-11-08 14:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:05:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
error about VM is not started (201.43 KB, image/png)
2023-03-28 01:43 UTC, Guohua Ouyang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 1219 0 None open Bug 2182233: Enforcing ssh secret name to be 51 chars or less 2023-03-30 10:41:10 UTC
Red Hat Issue Tracker CNV-27498 0 None None None 2023-03-28 01:47:59 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:05:19 UTC

Description Guohua Ouyang 2023-03-28 01:43:00 UTC 
Created attachment 1954055 [details]
error about VM is not started

Description of problem:
Clone a VM and then add a secret to the VM, VM is not able to be scheduled due to the secret name exceeds 63 characters

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create a vm from centos-stream8, wait for it up
2. clone a VM from it
3. add a secret to it and then restart the VM

Actual results:
VM is not started

Expected results:
VM is started

Additional info:
Comment 1 Matan Schatzman 2023-03-30 10:37:19 UTC 
The right number for the secret is 51 chars, as BE creates volume and adds more chars, so our bug fix will limit the name of the secret to 51 chars.
Comment 2 Guohua Ouyang 2023-03-31 01:03:38 UTC 
verified with v4.14.0-755
Comment 3 Guohua Ouyang 2023-03-31 05:29:05 UTC 
(In reply to Guohua Ouyang from comment #2)
> verified with v4.14.0-755

Added it by mistake, the issue is still there.
Comment 4 Matan Schatzman 2023-04-03 09:19:03 UTC 
As discussed, you have tested against the 4.12 cluster. The bug is caused by a very long VM name, the fix is applied for 4.13, 4.14. not backported to 4.12
Comment 5 Guohua Ouyang 2023-04-03 10:38:01 UTC 
verified it with v4.13.0-2383
Comment 8 errata-xmlrpc 2023-11-08 14:05:06 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.