+++ This bug was initially created as a clone of Bug #2100442 +++

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:

— Additional comment from Dan Kenigsberg on 2022-06-23 19:49:19 CST —

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.

— Additional comment from Ugo Palatucci on 2022-07-11 23:24:09 CST —

@yzamir@redhat.com @rsdeor@redhat.com

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

— Additional comment from Ugo Palatucci on 2022-07-11 23:27:02 CST —

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

— Additional comment from Yaacov Zamir on 2022-07-12 14:09:43 CST —

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,

— Additional comment from Ronen on 2022-07-19 20:37:36 CST —

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

— Additional comment from Ugo Palatucci on 2022-07-19 21:19:11 CST —

We're working on that. PR in review

— Additional comment from Guohua Ouyang on 2022-07-27 12:36:30 CST —

verified on v4.12.0-88

— Additional comment from errata-xmlrpc on 2022-07-27 13:58:19 CST —

This bug has been added to advisory RHEA-2022:95482 by CPaaS, owned by Greg Allen (contra-dev/pipeline@REDHAT.COM)