Hi all,
We are seeing a strange behavior and are still troubleshooting... but what
seems to be happening is when we shutdown a VM, and then power it on, on a
different host, the VM’s operating systems sees a new NIC and the old NIC is
gone. We aren’t 100% sure this is the scenario yet to repro
Announcing Apache CloudStack LTS Maintenance Release 4.13.1.0
The Apache CloudStack project is pleased to announce the release of
CloudStack 4.13.1.0 as part of its LTS 4.13.x releases. The CloudStack
4.13.1.0 release contains c. 80 fixes on top of the CloudStack 4.13.0.0
release. CloudStack LTS b
Hi Liridon,
I think CS has the wrong timezone because the default project is set to
GMT/UTC. I believe you can change that in the global settings. I have the same
situation but my management logs have the correct timestamp.
Thanks,
Robert
On 2020/05/01 17:52:46, "Ismaili, Liridon (SWISS TXT)
np!
Thanks
On Fri, 1 May 2020 at 20:27, Robert Ward wrote:
> Hi Andrija,
>
> On the JRE/MySQL/Timezone issues these are more observations than anything
> (comparing to my experience with fresh installs of 4.13). These may be
> more an install documentation note than anything.
>
> As for NFS is
Hi Andrija,
On the JRE/MySQL/Timezone issues these are more observations than anything
(comparing to my experience with fresh installs of 4.13). These may be more an
install documentation note than anything.
As for NFS issue: This install follows my tried and true practices for 4.13
installs
@Robert I did add the default-time-zone parameter to the my.cnf file but the
dates inside CloudStack are still in UTC format. select now() however gives me
the correct output:
mysql> select now();
+-+
| now() |
+-+
| 2020-05-01 19:48:38 |
+---
@Rohit Yadav can you possibly advice on the
time zone issue? I've seen this on another ML thread as well. We are mostly
in UTC (test envs) so this might be the reason we didn't see this...could
be just a documentation update that is needed.
@Robert is there any specifics to your NFS server (i.e.
Hi all,
I too have run into an issues while performing a clean install:
Centos 7, MySQL 5.6, JRE 11
JRE 11 and MySQL 5.6 don't see to play well on two points:
Installing JRE before MySQL causes MYSQL to "lockup" on startup. I have found
that if I install JRE after MySQL that issue is resolved.
Hi Andrija
First of thank you and Gabriel for pre-building the packages!
I did upgrade our test environment to CS 4.14.0.0 but had some issues on the
first upgrade try. As Java JRE 11 is required under CS 4.14.0.0 I did install
it on the cs-mgmt server. After that I made the Upgrade and saw the
