On 25.05.2016 09:58, Stanislav Laznicka wrote:
On 05/20/2016 03:00 PM, Martin Basti wrote:
On 19.05.2016 13:34, Stanislav Laznicka wrote:
Also, I tried to upgrade from 4.2.4 to 4.3.1 and it seems that it
might be necessary to start the service even earlier in the upgrade
logic. Attached i
On 05/20/2016 03:00 PM, Martin Basti wrote:
On 19.05.2016 13:34, Stanislav Laznicka wrote:
Also, I tried to upgrade from 4.2.4 to 4.3.1 and it seems that it
might be necessary to start the service even earlier in the upgrade
logic. Attached is the trace that occurred during the upgrade.
I
On 19.05.2016 13:34, Stanislav Laznicka wrote:
Also, I tried to upgrade from 4.2.4 to 4.3.1 and it seems that it
might be necessary to start the service even earlier in the upgrade
logic. Attached is the trace that occurred during the upgrade.
I sent the whole log earlier accidentally, hop
Also, I tried to upgrade from 4.2.4 to 4.3.1 and it seems that it might
be necessary to start the service even earlier in the upgrade logic.
Attached is the trace that occurred during the upgrade.
I sent the whole log earlier accidentally, hopefully it will not arrive
here as well.
On 05/19/
NACK, see my comments below
+# following upgrade steps require running CA
This is a nitpicky nitpick but could you please change this comment for
# the following ...
Took me a while to understand what you were trying to say here.
+if ca_running and not ca.is_running():
+ca.sto
