You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of problem:
Create a VM with "Create and edit" and a SSH key, then modify the network to "Direct attachment", then run the VM and wait until the VM boot completely. After that, log in the guest, and check the .ssh/authorized_keys, no public key found
Version-Release number of selected components (if applicable):
cockpit-300.1-1.el8_9.x86_64
cockpit-machines-301.1.2.gb0140b7-1.fc38.noarch
libvirt-dbus-1.3.0-2.module+el8.9.0+18724+20190c23.x86_64
How reproducible:
100%
Steps to Reproduce:
1 Create a VM with "Create and edit" and a SSH key
2 Modify the network to "Direct attachment"
3 Run the VM and wait until the VM boot completely
4 Log in the guest, and checck the .ssh/authorized_keys
Actual results:
1 No public found in .ssh/authorized_keys after step 4
Expected results:
1 The SSH key should be put in .ssh/authorized_keys
Additional info:
If without the step which is "Modify the network to "Direct attachment"", the SSH key will still not be in the .ssh/authorized_keys
The text was updated successfully, but these errors were encountered:
Description of problem:
Create a VM with "Create and edit" and a SSH key, then modify the network to "Direct attachment", then run the VM and wait until the VM boot completely. After that, log in the guest, and check the .ssh/authorized_keys, no public key found
Version-Release number of selected components (if applicable):
cockpit-300.1-1.el8_9.x86_64
cockpit-machines-301.1.2.gb0140b7-1.fc38.noarch
libvirt-dbus-1.3.0-2.module+el8.9.0+18724+20190c23.x86_64
How reproducible:
100%
Steps to Reproduce:
1 Create a VM with "Create and edit" and a SSH key
2 Modify the network to "Direct attachment"
3 Run the VM and wait until the VM boot completely
4 Log in the guest, and checck the .ssh/authorized_keys
Actual results:
1 No public found in .ssh/authorized_keys after step 4
Expected results:
1 The SSH key should be put in .ssh/authorized_keys
Additional info:
If without the step which is "Modify the network to "Direct attachment"", the SSH key will still not be in the .ssh/authorized_keys
The text was updated successfully, but these errors were encountered: