AW: [VOTE] Apache CloudStack 4.14.0.0 RC3

[Ismaili, Liridon (SWISS TXT)]

Hi All
Here is my vote: +1

Environment configuration:

  *   Apache CloudStack: MGMT + DB > CentOS 7
  *   Hosts: VMware ESXi
  *   Primary Storage: VMware VMFS, NFS
  *   Secondary Storage: NFS
  *   Zone Network: Advanced Network

Tests:

  *
Upgrade 4.13.1 to 4.14 (RC1/2/3)
  *
Update VRs
  *
Create new Networks (isolated; shared)
  *
VM lifecycle (starting, stopping, destroy, expunge)
  *   live migration
  *   snapshots
  *   Backups
  *   Created projects
  *   Created VPCs
  *   Check usage data
  *   Check DNS entries (after stopping / expunging)
  *   Check NIC cleanup after expunging VM
  *   Register new Template

Findings:

Since we are using CEST timezone over here we saw that the GUI shows now UTC 
times under Events. Over API I get CEST so I think it's a display issue here. 
DB entries are all in UTC.

Regards
Liridon

Von: Andrija Panic 
Gesendet: Montag, 11. Mai 2020 17:11
An: dev ; users 
Betreff: [VOTE] Apache CloudStack 4.14.0.0 RC3

Hi All,

I've created a 4.14.0.0 release (RC3), with the following artefacts up for
testing and a vote:

Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200511T1503
Commit: 6f96b3b2b391a9b7d085f76bcafa3989d9832b4e

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/

PGP release keys (signed using 3DC01AE8):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 14th May 2020, 17.00 CET (72h).

For sanity in tallying the vote, can PMC members please be sure to indicate
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from
6f96b3b2b391a9b7d085f76bcafa3989d9832b4e and published RC3 repository here:
http://packages.shapeblue.com/testing/41400rc3/  (CentOS 7 and
Debian/generic, both with noredist support)
and here
https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
 (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):

The release notes are still work-in-progress, but for the upgrade
instructions (including the new systemVM templates) you may refer to the
following URL:
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html

4.14.0.0 systemVM templates are available from here:
http://download.cloudstack.org/systemvm/4.14/

NOTES on issues fixed in this RC3 release:

(this one does *NOT* require a full retest if you were testing RC1/RC2
already - just if you were affected this issue):
- https://github.com/apache/cloudstack/pull/4064 - affects hostnames when
attaching a VM to additional networks

Regards,


Andrija Panić

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Ismaili, Liridon (SWISS TXT)]

Hi Andrija & Daan

@Daan I tried that out but without success. However the service seems to be 
recovered and did run successful. The dates inside the DB are in UTC format but 
when I list entries from the usage or cloud DB with CloudMonkey I get CEST 
results.
(the GUI did still show me UTC values in the Events but that's may caused by my 
environment).

@Andrija: I would say that it looks good. I also testet the parameters with 
"Europe/Zurich" but made no difference to me.

Regards
Liridon

-Original Message-
From: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>
Reply-To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
To: us...@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>,
 dev mailto:dev%20%3c...@cloudstack.apache.org%3e>>
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
Date: Tue, 05 May 2020 19:11:14 +0200


Hi Liridon,


do you have any feedback about the usage records timing/time zone and such?


Thanks

Andrija


On Mon, 4 May 2020 at 14:32, Daan Hoogland <

<mailto:daan.hoogl...@gmail.com>

daan.hoogl...@gmail.com

> wrote:


Liridon,

"Not owner of usage job, skipping" means there is a PID in the record for

this job that isn't the current process. If recognise this and have

remedied by setting the process id to null in the record. I'm sure there is

some underlying issue that you hit though. Just a workaround.


On Mon, May 4, 2020 at 12:56 PM Ismaili, Liridon (SWISS TXT) <

<mailto:liridon.isma...@swisstxt.ch>

liridon.isma...@swisstxt.ch

> wrote:


Hi Rohit


I tried so and did configure the usage to run 12:45 so I can monitor the

behavior. I got the following output:

2020-05-04 12:45:00,002 INFO  [cloud.usage.UsageManagerImpl]

(Usage-Job-1:null) (logid:) starting usage job...

2020-05-04 12:45:00,015 DEBUG [cloud.usage.UsageManagerImpl]

(Usage-Job-1:null) (logid:) Not owner of usage job, skipping...

2020-05-04 12:45:00,015 INFO  [cloud.usage.UsageManagerImpl]

(Usage-Job-1:null) (logid:) usage job complete


So the job did not run for some reason... I'm still looking into this. So

currently I can't confirm but will update you later as soon as the usage

job did run.


Regards

Liridon

-Original Message-

From: Rohit Yadav <

<mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com>

rohit%20yadav%20%3crohit.ya...@shapeblue.com

%3e>>

Reply-To:

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

>

To:

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

 <

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

mailto:22...@cloudstack.apache.org>

22...@cloudstack.apache.org

<mailto:%22%20%3c...@cloudstack.apache.org>

%22%20%3c...@cloudstack.apache.org

%3e>>,

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

 <

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

mailto:22andrija.pa...@gmail.com>

22andrija.pa...@gmail.com

<mailto:%22%20%3candrija.pa...@gmail.com>

%22%20%3candrija.pa...@gmail.com

%3e>>,

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

 <

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

mailto:22us...@cloudstack.apache.org>

22us...@cloudstack.apache.org

<mailto:%22%20%3cus...@cloudstack.apache.org>

%22%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Date: Mon, 04 May 2020 10:16:51 +



Thanks for testing and sharing your results Liridon!



Can you also test the case if the usage records have the correct time

according to configured timezone (in global settings) if you're using a

non-UTC timezone?



I'll add the db.usage.url.paramsl as well in the PR.




Regards,



Rohit Yadav



Software Architect, ShapeBlue



<

<https://www.shapeblue.com>

https://www.shapeblue.com

>


<https://www.shapeblue.com>

https://www.shapeblue.com








From: Ismaili, Liridon (SWISS TXT) <


mailto:liridon.isma...@swisstxt.ch>

liridon.isma...@swisstxt.ch

>


<mailto:liridon.isma...@swisstxt.ch>

liridon.isma...@swisstxt.ch





Sent: Monday, May 4, 2020 15:38


To:


mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>


<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org



 <


mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>


<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org



;


mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

>


<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com



 <


mailto:a

Re: [ Proposal ] Managing CloudStack Load Balancer configuration

[Ismaili, Liridon (SWISS TXT)]

Hi Wei,

That's some great improvements to the HAProxy! We couldn't realize some 
projects because of the missing features on the HAProxy therefore we are happy 
to hear that there will be some improvements.
As an addition to the proposal of you we would like to see the possibility to 
separate timeout settings (client/server/connect/...) as these timeout can be 
different.
We would also like to have the timeout settings available under the 
LoadbalancerRule

as a summary:
- Separate options for all timeout parameters (client/server/connect/...)
- Timeouts also per LoadbalancerRule, not only Network

We also thought about some "nice to have" additions:
- check customization: HTTP Check, Check Interval, etc.
- LoadbalancerRule: Custom Server string & Custom Listen string (only Domain 
Admin)
- Network: Custom Defaults (only Domain Admin)

Please let me know what you think about these additions.

Best Regards
Liridon

-Original Message-
From: "Riepl, Gregor (SWISS TXT)" 
mailto:%22Riepl,%20gregor%20%28swiss%20txt%29%22%20%3cgregor.ri...@swisstxt.ch%3e>>
Reply-To: dev@cloudstack.apache.org
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>
Subject: Re: [ Proposal ] Managing CloudStack Load Balancer configuration
Date: Mon, 04 May 2020 10:22:39 +


Hi Wei,


Thank you for this proposal!

We are also very much interested in this feature.


There's a few things we're not quite happy with, though - but we still need to 
discuss this internally a bit.

Liridon or myself will give some feedback soon.


Regards,

Gregor



From: Wei ZHOU <



ustcweiz...@gmail.com

>

Sent: 01 May 2020 08:01

To:



dev@cloudstack.apache.org

 <



dev@cloudstack.apache.org

>

Subject: [ Proposal ] Managing CloudStack Load Balancer configuration


Our improvements to cloudstack load balancer (implemented by HAproxy in the

VRs) allow cloudstack users to manage certain restricted configuration

settings. With this feature, users can


* Change basic configuration of HAproxy (e.g. set the amount of allowed

connections),


* choose if load balancer is transparent,


* enable or disable the support for SSL offloading in isolated networks.


* choose if load balancer supports HTTP/2.


* more settings.




To make this possible to the user, we provide two forms on cloudstack GUI

(old GUI, will add changes on Primate) from which the settings can be

managed and applied in virtual routers.




FS can be found at



https://cwiki.apache.org/confluence/display/CLOUDSTACK/VR+haproxy+customization+in+CloudStack




Any suggestions ?




Kind regards,


*Wei Zhou*


Principal Cloud Engineer


Leaseweb Global B.V.

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Ismaili, Liridon (SWISS TXT)]

Hi Rohit

I tried so and did configure the usage to run 12:45 so I can monitor the 
behavior. I got the following output:
2020-05-04 12:45:00,002 INFO  [cloud.usage.UsageManagerImpl] (Usage-Job-1:null) 
(logid:) starting usage job...
2020-05-04 12:45:00,015 DEBUG [cloud.usage.UsageManagerImpl] (Usage-Job-1:null) 
(logid:) Not owner of usage job, skipping...
2020-05-04 12:45:00,015 INFO  [cloud.usage.UsageManagerImpl] (Usage-Job-1:null) 
(logid:) usage job complete

So the job did not run for some reason... I'm still looking into this. So 
currently I can't confirm but will update you later as soon as the usage job 
did run.

Regards
Liridon
-Original Message-
From: Rohit Yadav 
mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com%3e>>
Reply-To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 andrija.pa...@gmail.com 
mailto:%22andrija.pa...@gmail.com%22%20%3candrija.pa...@gmail.com%3e>>,
 us...@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
Date: Mon, 04 May 2020 10:16:51 +


Thanks for testing and sharing your results Liridon!


Can you also test the case if the usage records have the correct time according 
to configured timezone (in global settings) if you're using a non-UTC timezone?


I'll add the db.usage.url.paramsl as well in the PR.



Regards,


Rohit Yadav


Software Architect, ShapeBlue


<https://www.shapeblue.com>

https://www.shapeblue.com



________

From: Ismaili, Liridon (SWISS TXT) <

<mailto:liridon.isma...@swisstxt.ch>

liridon.isma...@swisstxt.ch

>

Sent: Monday, May 4, 2020 15:38

To:

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

 <

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>;

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

 <

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

>;

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

 <

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1


Hi Rohit


That did the trick! I did remove all the timezone information on my.cnf and 
only added the timezone information on the db.properties file.

So I can confirm it fixes the issue.


If you are using the usage service too you will also need to specify the 
timezone information for the usage DB:

"db.usage.url.params=" in the /etc/cloudstack/management/db.properties file. 
Otherwise the usage service won't be able to start.


This did also fix my issue and all my dates inside the db are now in the 
correct time zone! I'll also update the Github PR so we can track it there.


Many thanks and Regards

Liridon


<mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com



<http://www.shapeblue.com>

www.shapeblue.com


3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK

@shapeblue







-Original Message-

From: "Ismaili, Liridon (SWISS TXT)" <

<mailto:liridon.isma...@swisstxt.ch>

liridon.isma...@swisstxt.ch

<mailto:%22Ismaili,

<mailto:%20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch>

%20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch

%3e>>

Reply-To:

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

>

To:

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

 <

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

mailto:%22...@cloudstack.apache.org>

%22...@cloudstack.apache.org

<mailto:%22%20%3c...@cloudstack.apache.org>

%22%20%3c...@cloudstack.apache.org

%3e>>,

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

 <

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

mailto:%22andrija.pa...@gmail.com>

%22andrija.pa...@gmail.com

<mailto:%22%20%3candrija.pa...@gmail.com>

%22%20%3candrija.pa...@gmail.com

%3e>>,

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

 <

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

mailto:%22us...@cloudstack.apache.org>

%22us...@cloudstack.apache.org

<mailto:%22%20%3cus...@cloudstack.apache.org>

%22%20%3cus...@cloudstack.apache.org

%3e>>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Date: Mon, 04 May 2020 09:53:35 +



Hi Rohit



I'll test that and let you know.



Regards


Liridon



-Original Message-


From: Rohit Yadav <


mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

>

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Ismaili, Liridon (SWISS TXT)]

Hi Rohit

That did the trick! I did remove all the timezone information on my.cnf and 
only added the timezone information on the db.properties file.
So I can confirm it fixes the issue.

If you are using the usage service too you will also need to specify the 
timezone information for the usage DB:
"db.usage.url.params=" in the /etc/cloudstack/management/db.properties file. 
Otherwise the usage service won't be able to start.

This did also fix my issue and all my dates inside the db are now in the 
correct time zone! I'll also update the Github PR so we can track it there.

Many thanks and Regards
Liridon

-Original Message-----
From: "Ismaili, Liridon (SWISS TXT)" 
mailto:%22Ismaili,%20liridon%20%28swiss%20txt%29%22%20%3cliridon.isma...@swisstxt.ch%3e>>
Reply-To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 andrija.pa...@gmail.com 
mailto:%22andrija.pa...@gmail.com%22%20%3candrija.pa...@gmail.com%3e>>,
 us...@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
Date: Mon, 04 May 2020 09:53:35 +


Hi Rohit


I'll test that and let you know.


Regards

Liridon


-Original Message-

From: Rohit Yadav <

<mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com>

rohit%20yadav%20%3crohit.ya...@shapeblue.com

%3e>>

Reply-To:

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

>

To: Andrija Panic <

<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

mailto:andrija%20panic%20%3candrija.pa...@gmail.com>

andrija%20panic%20%3candrija.pa...@gmail.com

%3e>>, users <

<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

mailto:users%20%3cus...@cloudstack.apache.org>

users%20%3cus...@cloudstack.apache.org

%3e>>,

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

 <

<mailto:dev@cloudstack.apache.org>

dev@cloudstack.apache.org

mailto:%22...@cloudstack.apache.org>

%22...@cloudstack.apache.org

<mailto:%22%20%3c...@cloudstack.apache.org>

%22%20%3c...@cloudstack.apache.org

%3e>>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Date: Mon, 04 May 2020 09:50:10 +



Hi Andrija, all,



While adding support for Java 11, the mysql-connector 8.x java dependency was 
introduced from previous 5.7x version.



According to


<

<https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html>

https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html

>


<https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html>

https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html



 it seems we can specify the server time in connection parameters. Can any 
users test this workaround and confirm if it fixes their issue in their 
test/upgrade environments by adding  "&serverTimezone=UTC" to the 
"db.cloud.url.params=" in the /etc/cloudstack/management/db.properties file, 
revert changes for mysql server and restart the management server.



Draft PR proposed:


<

<https://github.com/apache/cloudstack/pull/4055/files>

https://github.com/apache/cloudstack/pull/4055/files

>


<https://github.com/apache/cloudstack/pull/4055/files>

https://github.com/apache/cloudstack/pull/4055/files





We may then either discuss to either include the above PR or document this in 
our release/upgrade notes. Thanks.




Regards,



Rohit Yadav



Software Architect, ShapeBlue



<

<https://www.shapeblue.com>

https://www.shapeblue.com

>


<https://www.shapeblue.com>

https://www.shapeblue.com








From: Andrija Panic <


mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com

>


<mailto:andrija.pa...@gmail.com>

andrija.pa...@gmail.com





Sent: Friday, May 1, 2020 22:38


To: users <


mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org

>


<mailto:us...@cloudstack.apache.org>

us...@cloudstack.apache.org



; Rohit Yadav <


mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

>


<mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com





Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1



@Rohit Yadavmailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

>


<mailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com



can you possibly advice on the time zone issue? I've seen this on another ML 
thr

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Ismaili, Liridon (SWISS TXT)]

Hi Rohit

I'll test that and let you know.

Regards
Liridon

-Original Message-
From: Rohit Yadav 
mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com%3e>>
Reply-To: dev@cloudstack.apache.org
To: Andrija Panic 
mailto:andrija%20panic%20%3candrija.pa...@gmail.com%3e>>,
 users 
mailto:users%20%3cus...@cloudstack.apache.org%3e>>,
 dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1
Date: Mon, 04 May 2020 09:50:10 +


Hi Andrija, all,


While adding support for Java 11, the mysql-connector 8.x java dependency was 
introduced from previous 5.7x version.


According to



https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html

 it seems we can specify the server time in connection parameters. Can any 
users test this workaround and confirm if it fixes their issue in their 
test/upgrade environments by adding  "&serverTimezone=UTC" to the 
"db.cloud.url.params=" in the /etc/cloudstack/management/db.properties file, 
revert changes for mysql server and restart the management server.


Draft PR proposed:



https://github.com/apache/cloudstack/pull/4055/files



We may then either discuss to either include the above PR or document this in 
our release/upgrade notes. Thanks.



Regards,


Rohit Yadav


Software Architect, ShapeBlue




https://www.shapeblue.com





From: Andrija Panic <



andrija.pa...@gmail.com

>

Sent: Friday, May 1, 2020 22:38

To: users <



us...@cloudstack.apache.org

>; Rohit Yadav <



rohit.ya...@shapeblue.com

>

Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1


@Rohit Yadavmailto:rohit.ya...@shapeblue.com>

rohit.ya...@shapeblue.com

> 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. a forbidden NFSv3 or 
similar)? Also, can you please open a GitHub issue and provide the same there? 
So we can track it and collaborate - I've not seen this one before.

What packages did you use for the installation? On the issue you'll raise, 
please also include the relevant output from the /var/log/cloud.log from inside 
the SSVM

Also not sure what is the relation between MySQL and JRE at all - they should 
have nothing in common?


Thanks!


Andrija






rohit.ya...@shapeblue.com





www.shapeblue.com


3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK

@shapeblue






On Fri, 1 May 2020 at 17:49, Robert Ward <



rww...@gmail.com

mailto:rww...@gmail.com>

rww...@gmail.com

>> wrote:

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.


MySQL chokes with timezone error @ cloudstack-setup-management. In my case 
MySQL doesn't like "EDT" as a timezone. Resolved by adding this to etc/my.cnf:


default-time-zone= "-05:00"


On my last point CS has difficulty with mounting secondary storage. I have 
clipped the logs to the point where I think the problem lies:


2020-05-01 10:55:07,871 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] 
(StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) getCommandHostDelegation: 
class com.cloud.agent.api.GetStorageStatsCommand

2020-05-01 10:55:07,871 DEBUG [c.c.h.XenServerGuru] 
(StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) We are returning the default 
host to execute commands because the command is not of Copy type.

2020-05-01 10:55:07,910 DEBUG [c.c.a.t.Request] (AgentManager-Handler-8:null) 
(logid:) Seq 2-4356951164504244991: Processing:  { Ans: , MgmtId: 144345337593, 
via: 2, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
 GetRootDir for nfs://192.168.25.1/export/secondary<



http://192.168.25.1/export/secondary

> failed due to com.cloud.utils.exception.CloudRuntimeException: Unable to 
> mount 192.168.25.1:/export/secondary at 
> /mnt/SecStorage/b7e9e158-ed80-3a62-a5d7-1992c991d829 due to mount.nfs: 
> requested NFS version or transport protocol is not supported\n\tat 
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorag

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

[Ismaili, Liridon (SWISS TXT)]

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 following 
exception:
2020-05-01 11:45:12,116 ERROR [utils.db.Merovingian2] (main:null) Unable to get 
a new db connection
java.sql.SQLNonTransientConnectionException: Could not create connection to 
database server. Attempted reconnect 3 times. Giving up.
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
at 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
at 
com.mysql.cj.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:906)
at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:831)
at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:456)
at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:246)
at 
com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:197)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:228)
at 
org.apache.commons.dbcp2.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:121)
at 
org.apache.commons.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:355)
at 
org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:889)
at 
org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:424)
at 
org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:349)
at 
org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:134)
at 
com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:213)
at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
at 
com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
at 
com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at 
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:203)
at 
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:117)
at 
org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:310)
at 
org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:295)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:879)
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550)
at 
org.apache.cloudstack.spring.module.model.impl.DefaultModul

Re: [VOTE] Apache CloudStack 4.13.0.0 RC2

[Ismaili, Liridon (SWISS TXT)]

Hi Guys,

+1 from our side

Following upgrade was done:
from 4.11.3 to 4.13 RC2
- VMWare 6.5
- Advanced network setup

Post upgrade steps:
- redeployed systemVMs
- redeployed vRouters

Tests done:
- create / started / stopped / destroyed VMs which were created before and 
after the upgrade
- create / restart / cleanup / redundant vRouters
- upload / delete templates and multi disk templates
- create / delete projects / accounts / users

Regards
Liridon

-Original Message-
From: Paul Angus 
mailto:paul%20angus%20%3cpaul.an...@shapeblue.com%3e>>
Reply-To: us...@cloudstack.apache.org
To: dev@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 us...@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: [VOTE] Apache CloudStack 4.13.0.0 RC2
Date: Wed, 28 Aug 2019 22:02:32 +


Hi All,


We had an excellently low number of bugs in RC1, so here's RC2 with just 3 
fixes...


I've created a 4.13.0.0 release (RC2), with the following artefacts up for 
testing and a vote:


Git Branch and Commit SH:



https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535


Commit: 7c7efe76013675b476d8aa14c36a353cd5d429fc


Source release (checksums and signatures are available at the same location):



https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/



PGP release keys (signed using 51EE0BC8):



https://dist.apache.org/repos/dist/release/cloudstack/KEYS



The vote will be open until 31st August.


For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?


[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)


Additional information:


For users' convenience, I've built packages from 
7c7efe76013675b476d8aa14c36a353cd5d429fc and published RC1 repository here:



http://packages.shapeblue.com/testing/41300rc2/



The systemvm templates are unchanged from 4.11.3/4.12.0:



http://download.cloudstack.org/systemvm/4.11/



Fixes in RC2


#3566   server: fix NPE for the case where volume is not attached to a VM

#3567   fix xenserver 7.1.0 os mapping typo

#3571   Unable to deploy VMs via UI in advanced networks with SG and IPv6 cidr







paul.an...@shapeblue.com





www.shapeblue.com


Amadeus House, Floral Street, London  WC2E 9DPUK

@shapeblue