Search results

I'm opening this issue here to actually document the solution. Upgrading from jessie to stretch, or actually from older to newer may result a non-working https repo which fail the certificate verification. The problem occurs when there was either no way to perform a dist-upgrade first, or...

While I see your point in this case Proxmox deletes a container with active HA state, and HA subsystem is unable to handle this (cannot delete it). The problem is not [only] that there is no consistency check when deleting something still in HA but that along with this missing check there is a...

Use CephFS.

It seems to be easily fixed by manually cutting the respective entries from /etc/pve/ha/resources.cfg, with no visible side effects. Still, not ideal.

set CT to "ignore" in the HA web GUI delete CT At that point you have an entry in ha config without a node, which cannot be removed, and keeps logging errors.

I would really appreciate a thread where there would be a continuous, complete status report about LXC online migration; I mean: what have you done to make it work; why it doesn't work now; who and what should be done to make it work; is there any timeframe for that; i$ there any way to $peed...

Fixed in recent releases.

It seems the other way around: the documentation have been updated to v5 but the doc doesn't contain that it's been changed from v4.x. My bad.

In proxmox5 cpu setting have diverged from all the documentation. It seems that cores setting is gone, as well as cpusets, and right now only cpulimit prevailed. First, documentation thinks otherwise. Very probably should be updated. Second, this may be a problem if the programs in the...

btw see gnutls_handshake() failed: A TLS packet with unexpected length was received.

So, this bug may be related to the various versions of [DOWNGRADE] libcurl3-gnutls:amd64 7.52.1-5 -> 7.38.0-4+deb8u7 [DOWNGRADE] python-pycurl:amd64 7.43.0-2 -> 7.19.5-3 and possibly the related to [REMOVE, NOT USED] libidn2-0:amd64 [REMOVE, NOT USED] libnghttp2-14:amd64 [REMOVE, NOT USED]...

Right now there is no convenient way to add a CT/VM to the HA: you go to the HA view, and have to type the id number, which you should either memorize or scroll back and forth the list; the point is: I hardly ever care WHAT the ctid is, so I don't [intend to] memorize it. HA view only show the...

Don't get me wrong: I am aware how an open source project works, and I am also aware that it's a really uncomfortable position to lead a project and realise that one decision in the past have turned out to be wrong, and results lots of really unwanted tasks waiting to be done. I could, at least...

1) Almost. First, you have to go to and from the host tab. Second, you have to wait until the error gets cleared by the ha-manager, then can you add it again. Do it too fast and it won't clear. This may require you to go there and back again, again. :-) 2) This requires at least four, most...

https://forum.proxmox.com/threads/annoying-no-scroll-menu-in-the-new-gui.29808/ This is the same you have said on Oct 19, 2016. Okay, I'll open a bug. You see, from the end-user point of view there is no "sencha", only Proxmox. We are not in any relation with "sencha", and we have neither...

It would be neat to have a HA function on the gui to actually clear the error status of the given CT/VM. HA have the bad tendency to put stuff in error when it had timeout, or generally holding some grudge against me. It'd do no harm: if it's still bad, it'll go into error again anyway...

It is a known bug for at least half a year now (possibly more), some external javascript you use to display any menu on the second from the left (like server view>>host) cannot mouse-scroll under firefox but works under chrome. You said you have reported it and wait for the fix, but it's been...

Didn't help.

When the ct/vm list is long and scrolling, and something is selected, then the list jumps there after a few seconds no matter where I have scrolled it. Unspeakably annoying. :-) [By the way the firefox mouse scrolling of the menu is still not working. It's been, what, half a year now?] This is...

Okay, thanks, and let's hope others find this thread to have it fixed. :rolleyes: