First a big sorry for my incredible delay. Unfortunately I had to deal with some family issues, some work related crisis interventions, and nevertheless keep up the work of the server WG.
Am 02.02.2022 um 18:03 schrieb Katerina Koukiou kkoukiou@redhat.com:
My cockpit installation did not have the "Virtual Machines" menu option nor did I have the option to install cockpit modules. I could initially only remove installed modules. Coming back to this days later, I now see all cockpit modules, with the ability to install those I don't have. Is this a known issue or have I done this wrong?
I am suspecting you are facing this issue https://github.com/cockpit-project/cockpit/issues/16128
I saw that issue earlier at various times but couldn't reliable reproduce. Now, with my F35 test machines running cockpit-machines 260, I have not encountered this problem, despite multiple attempts.
The issue is not closed. Is it worthwhile to mention in a side note that, as a result of a bug, the list is sometimes not displayed and you should try again?
The _images/virtualization-vm-install-fedoraserver-cockpit-020.png image does not match the form I get on F35. I have a "Connection" option which gives me the choice between "System" and "Session". This is not reflected in the image.
There are cases where 'Session' connection is not available, for example when logged in to cockpit as root.
Indeed, I was logged in as root when I made the screenshot.
I wanted to find out what the session option exactly does and tried to find a documentation of the cockpit-machines module, without success. Did I overlooked it on the Cockpit project site or is there currently no documentation?
(And I’m in the process to add documentation to install cloud images and looking for documentation how the module deals with cloud-init, with ignition, and with plain VMs. Or is the only way so far to reconstruct it by trial and error?)
The documentation later states "After a test of the installation media the well known installation process begins. You may select Expand at the right top to increase readability". In my case, I HAD to click on 'Expand' for the VNC console to register my keystrokes.
There is an open issue about this, https://github.com/cockpit-project/cockpit-machines/issues/29
I’m unsure how to handle that in the documentation here. What would be a better and more adequate wording?
Hope this helps, Katerina
thanks, helped me a lot. Documentation is sometimes harder (at least for me) as writing my scientific research reports. :-)
In the "Optional post-installation tasks" section, the first task is titled "Get rid of nano as default editor". I feel "Making vim the default editor" better reflects the contents of this section. I would also recommend replacing the command by "dnf install --allowerasing vim-default-editor" which simplifies the task.
Regards, Emmanuel
Yes, very much agreed!
I already pushed the modification to stg. Should be visible in about an hour at the latest.
Best Peter