Tried PDM for the first time (version 1.1) - had issues

[stuartbh]

Proxmox team, users, developers, et alia:

I installed PDM 1.1 and had some several issues as I attempted to get it functioning.

1) In succession to an installation that instantiated zero errors or that, the only button I could see was "REBOOT", no shutdown button. I wanted to shutdown the VM first so I could do a pre-first-bootup snapshot of it. I had to click reboot and then try to catch powering off the VM before it started its real boot process. Please add a shutdown button!!

2) Once I got the VM booted up I could not login. I carefully typed the username (root) and the password I set, but it kept telling me it was invalid. I reverted to the "pre-install" snapshot and reinstalled, thereafter I was able to login.

3) After logging in I added my Proxmox Backup Server to the PDM server, it worked flawlessly. I then went to add my cluster, however, one of the cluster members is having a hardware issue and is down. It got stuck trying to add the cluster and all I could do was cancel out. WOW! no way to just say, please ignore the missing cluster member as 5 out of 6 cluster members are up and healthy? What a brick wall!!!

4) It would be worthy of notation that I did not see any way to get in process help (a "?" to hover over) that would tell me what a "remote id" is? Had to stop and conduct a google search on that. Why not just give an easy to find answer to that?

Thanks!

Stuart

 

[dcsapak]

hi,

1) In succession to an installation that instantiated zero errors or that, the only button I could see was "REBOOT", no shutdown button. I wanted to shutdown the VM first so I could do a pre-first-bootup snapshot of it. I had to click reboot and then try to catch powering off the VM before it started its real boot process. Please add a shutdown button!!

AFAIK there is no special setup done on the first boot, so just let it boot and shutdown should have the same effect as directly shutting down. adding a shutdown button
at the end of the installation is IMO a rather niche use case.

3) After logging in I added my Proxmox Backup Server to the PDM server, it worked flawlessly. I then went to add my cluster, however, one of the cluster members is having a hardware issue and is down. It got stuck trying to add the cluster and all I could do was cancel out. WOW! no way to just say, please ignore the missing cluster member as 5 out of 6 cluster members are up and healthy? What a brick wall!!!

you should be able to remove the node from in the PVE remote wizard, so it does not try to connect there, did that not work for you? If not what error did you get?
Generally the idea of a cluster is still that all nodes are healthy during normal operations, but i agree you should be able to add a remote even if some nodes are offline (if the majority is online of course, otherwise it's not possible to generate a token for example)

4) It would be worthy of notation that I did not see any way to get in process help (a "?" to hover over) that would tell me what a "remote id" is? Had to stop and conduct a google search on that. Why not just give an easy to find answer to that?

this is the same for most of our concepts in pve/pbs, everything you configure has to have a unique id, such as: a storage, remote, node, metric server, realm, etc...
but yeah some kind of emptytext/tooltip could be nice