nvazquez commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-3057086700
Hi @weizhouapache @Pearl1594 is there any update regarding the first issue?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
rohityadavcloud commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-2792551229
Can we at least look at the first issue (Allow automatic migration of log4j
xml when upgrading from 4.19 or older versions to 4.20 or later versions;
during upgrade keep
weizhouapache commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-2792376355
> I upgraded from 4.19.0 to 4.20.0 - and I didn't encounter the 3rd issue
mentioned as well.
the folder `/var/log/cloudstack/management/null/` does exist in my old
Pearl1594 commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-2783845282
I upgraded from 4.19.0 to 4.20.0 - and I didn't encounter the 3rd issue
mentioned as well.
--
This is an automated message from the Apache Git Service.
To respond to the me
JoaoJandre commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-2783365436
@rohityadavcloud @weizhouapache, I have not been able to confirm issue 3 in
4.20. Thus this must have been introduced in another PR (not related to the
log4j2 upgrade).
DaanHoogland commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-2783105437
As @weizhouapache remarked, the logging issue itself is addressed in #10567
That leaves the question if we should save the old logging configuration or
consider this res
weizhouapache commented on issue #10665:
URL: https://github.com/apache/cloudstack/issues/10665#issuecomment-2782547322
the issue 2 is same as #10565
```
apilog.log file is empty now, any UI/API activities don't add new lines to
it anymore
```
confirmed issue 3
--
This i
