Bug 2100442

Summary:	[RFE] allow enabling and disabling SSH service while VM is shut down
Product:	Container Native Virtualization (CNV)	Reporter:	Yaacov Zamir <yzamir>
Component:	User Experience	Assignee:	Ugo Palatucci <upalatuc>
Status:	CLOSED ERRATA	QA Contact:	Guohua Ouyang <gouyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.12.0	CC:	danken, gouyang, rsdeor, upalatuc
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2145030 (view as bug list)		Environment:
Last Closed:	2023-01-24 13:36:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2145030

Description Yaacov Zamir 2022-06-23 11:37:36 UTC

Description of problem:
[RFE] allow enabling and disabling SSH service while VM is shut down
a VM can own a service even if the VMI is shut down

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


How reproducible:


Steps to Reproduce:
1. create a VM
2. shut the VM down
3. try to get the ssh command
4. try to start an ssh service

Actual results:
when vm is shut down, ssh comman is hidden, and ssh service is not editable

Expected results:
ssh command is visiable even if vm is shut down, ssh service can be created and deleted.

EDIT: this bug is about starting and stopping the service, the ssh command can be hidden if no VM is running.

Additional info:

Comment 1 Dan Kenigsberg 2022-06-23 11:49:19 UTC

Thanks for filing this. GUI should let users request things that would be eventually available, even if they are not immediately so.

I'm not sure why this is specified as an RFE, though. I would guess that it is just a "if VM is running" conditional that should be dropped.

Comment 2 Ugo Palatucci 2022-07-11 15:24:09 UTC

@yzamir @rsdeor 

What if the user changes credentials in the scripts tab? Should we show in the command the new credentials or the old ones?

Comment 3 Ugo Palatucci 2022-07-11 15:27:02 UTC

Sorry, I have to add something. The question alone does not make a lot of sense.

The user changes credentials *with a VMI running*. 
New credentials will be applied only after restart

Comment 4 Yaacov Zamir 2022-07-12 06:09:43 UTC

AFAIU
- the command a user can copy to access the VMI should work, so it requires the credentials that work now in the VMI
- so the command should always use the valid data from the VMI, [ when editing credentials the changes are only done to the VM, it should not affect the VMI ]
- In cases the VMI is not working, you can show the command to access the VMI using the VM, ( but you can also omit it )
- In cases the VMI is not working, you ** can ** create/delete and edit the service,

Comment 5 Ronen 2022-07-19 12:37:36 UTC

I see it more as a bug than an RFE. I think we should do it

Comment 6 Ugo Palatucci 2022-07-19 13:19:11 UTC

We're working on that. PR in review :-)

Comment 7 Guohua Ouyang 2022-07-27 04:36:30 UTC

verified on v4.12.0-88

Comment 11 errata-xmlrpc 2023-01-24 13:36:39 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.12.0 Images security 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:0408