+1 for an easy way to enable a node's maintenance mode. On the node's top line in the right pane (besides the "Shutdown" and "Reboot" buttons) would be a nice place. Or in the node's context menu (right click).
And as previously stated: this...
Your "+1" is probably better placed over there: https://bugzilla.proxmox.com/show_bug.cgi?id=6144, already mentioned in #47.
You'll also find a patch already mentioned in the last comment.
Thanks for the reply. Still having issues. Logs show nothing except for errors related to error 429. The system will revert my valid certs to expired LetsEncrypt ones after some period of time. I don't have any cron jobs and the only...
I know I'm reviving a rather old post, but since I had a similar issue and found a solution by myself, I'll add my .20 so others can learn from it too, I was also stuck on "Welcome to GRUB!" upon updating from 8 to 9.2, I booted from a USB as...
Hey @Logicman ,
We understand your requirement. Many volunteers on this forum work in similar environments and face comparable constraints. However, the audience overlap for your specific question is relatively small: business PVE users...
I had the same when I first turned on the balancer, and occasionally when replacing a failed OSD. It never caused VMs problems other than sometimes a read would take a long time to return data. Normally the balancer makes just one or a few...
Welcome to the world of having a boss.
Depending on your role, your job is to INFORM the decision makers or MAKE decisions. if you're in the former, voice your concern in writing and then do what is decided (and dont bitch! once the decision is...
this is likely the same issue also affecting pve-subscription, since both use the same underlying HTTP client: https://bugzilla.proxmox.com/show_bug.cgi?id=6791
I was able to trick it into working by putting in a dummy record in host file for shop.proxmox.com does not need to be the actual IP just something for it to get an Ipv4 address it appears. subscription check succeed afterwards.
Based on the solution in this thread: Subscription check behind proxy broken in PVE9, I was able to add shop.proxmox.com to the hosts file on each PVE node and successfully push out keys and activate all my nodes.
How it's just the issue of...
The company I work for want ServiceNow to have access to everything and, myself, as a rule I would not allow anything to have ssh access to an hypervisor unless specifically approved by the make of the hypervisor; but I'm being force to comply...
Any access can cause denial of service. Even read-only might allow too many network requests that cripple the system eventually. You'll have to do your own attack surface and thread vector analysis. That said: you do kind of trust the co-workers...
AFAIK that's all right. Which OSD you talk to for each chunk of data is supposed to kinda look random, so you spread the load out around the cluster. The more disks you have the more simultaneous reads you can do with only some small percentage...