Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4

2022-06-03 Thread Vladimir Petrov
+1

I tested many basic operations related to VMs, volumes, templates and haven't 
found any issues.

Vladimir Petrov



Nicolas Vazquez wrote:


Hi all,

I have created a 4.17.0.0 release (RCR) with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
Commit: c56220fcf2348c7809331dcc266775f3d7130fe6

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

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

The vote will be open until 6th June 2022.

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)

Regards,
Nicolas Vazquez





 



Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4

2022-06-03 Thread Daan Hoogland
+1 (binding)
checksums verified
monkeying on a combined kvm/vmware env and no issues encountered as of yet

On Fri, Jun 3, 2022 at 10:39 AM Wei ZHOU  wrote:

> +0 (binding)
>
> tested on rocky8 and vmware70u3 on
>
>1. vm lifecycle
>2. volume lifecycle
>3. different network types
>4. certificates
>
> looks good.
>
> I have confirmed an issue found by Pearl that VPC VR is stuck for 1 minute
> at startup and continues working. It seems like a non-critical issue.
> fix: https://github.com/apache/cloudstack/pull/6435
>
> -Wei
>
> On Tue, 31 May 2022 at 19:40, Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com>
> wrote:
>
> > Hi all,
> >
> > I have created a 4.17.0.0 release (RCR) with the following artefacts up
> > for testing and a vote:
> >
> > Git Branch and Commit SH:
> > https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
> > Commit: c56220fcf2348c7809331dcc266775f3d7130fe6
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.17.0.0/
> >
> > PGP release keys (signed using 239A653975E13A0EEF5122A1656E1BCC8CB54F84):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > The vote will be open until 6th June 2022.
> >
> > 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)
> >
> > Regards,
> > Nicolas Vazquez
> >
> >
> >
> >
> >
>


-- 
Daan


Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4

2022-06-03 Thread Wei ZHOU
+0 (binding)

tested on rocky8 and vmware70u3 on

   1. vm lifecycle
   2. volume lifecycle
   3. different network types
   4. certificates

looks good.

I have confirmed an issue found by Pearl that VPC VR is stuck for 1 minute
at startup and continues working. It seems like a non-critical issue.
fix: https://github.com/apache/cloudstack/pull/6435

-Wei

On Tue, 31 May 2022 at 19:40, Nicolas Vazquez 
wrote:

> Hi all,
>
> I have created a 4.17.0.0 release (RCR) with the following artefacts up
> for testing and a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
> Commit: c56220fcf2348c7809331dcc266775f3d7130fe6
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.17.0.0/
>
> PGP release keys (signed using 239A653975E13A0EEF5122A1656E1BCC8CB54F84):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 6th June 2022.
>
> 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)
>
> Regards,
> Nicolas Vazquez
>
>
>
>
>


Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

2022-06-03 Thread Andrija Panic
What he said ^^^, as the XenServer upgrade effectively does backup of the
old partition data, and installs a brand new OS - with no ACS
plugins/scripts - so you have to initialise the host, to force ACS to copy
again all the binaries.

Best,

On Thu, 2 Jun 2022 at 06:14, Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Hi Vivek,
>
> Please check the CloudStack detected Xenserver version in either UI or
> database.
>
> You may try an option to reinitialize the Xenserver host by clearing the
> tags on the host and try reconnecting from CloudStack UI.
> Run the following command on Xenserver and reconnect the host.
>
> # for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe
> host-param-clear uuid=$host param-name=tags; done;
>
> Hope this helps.
>
> Regards,
> Harikrishna
> 
> From: Suresh Anaparti 
> Sent: Wednesday, June 1, 2022 3:07 PM
> To: users@cloudstack.apache.org 
> Subject: Re: XenServer Agent is not coming up after upgrading from 7.1 to
> 8.2
>
> Hi Vivek,
>
> This discussion thread might provide you some inputs:
> https://lists.apache.org/thread/7q6yybm3qcms21qcd8945kvrygpr1v86
>
> Also, check the docs here:
> http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/hypervisor/xenserver.html#upgrading-xenserver-versions,
> and see if you have missed any upgrade step.
>
>
> Regards,
> Suresh
>
> On 01/06/22, 2:17 PM, "Vivek Kumar" 
> wrote:
>
> Hello Guys,
>
>
> We have recently upgraded our XenServer  from 7.1 to 8.2. We are using
> CloudStack 4.16.1. But after the upgradation my status of host is showing
> alert. I have gone through the logs getting below error. Can someone help
> me out for this.
>
>
>
> —
>
>
>
> rZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw=listSystemVms=json=3=2022-06-01T08%3A43%3A33%2B=x7KQg4LW2XPtTf%2BHHVn0Fm599xA%3D
> 2022-06-01 14:00:51,613 DEBUG [c.c.u.s.SSHCmdHelper]
> (DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Executing cmd: rm -f
> /opt/xensource/sm/hostvmstats.py
> /opt/xensource/bin/copy_vhd_to_secondarystorage.sh
> /opt/xensource/bin/copy_vhd_from_secondarystorage.sh
> /opt/xensource/bin/create_privatetemplate_from_snapshot.sh
> /opt/xensource/bin/vhd-util /opt/cloud/bin/copy_vhd_to_secondarystorage.sh
> /opt/cloud/bin/copy_vhd_from_secondarystorage.sh
> /opt/cloud/bin/create_privatetemplate_from_snapshot.sh
> /opt/cloud/bin/vhd-util
> 2022-06-01 14:00:52,750 DEBUG [c.c.a.ApiServlet]
> (qtp1850777594-19:ctx-5c391d12) (logid:fb2dbf4b) ===START===  172.31.29.44
> -- GET
> listall=True=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw=listVpnConnections=json=3=2022-06-01T08%3A43%3A35%2B=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
> 2022-06-01 14:00:52,756 DEBUG [c.c.a.ApiServer]
> (qtp1850777594-19:ctx-5c391d12 ctx-9cd12123) (logid:fb2dbf4b) CIDRs from
> which account 'Acct[0d808973-19be-11eb-9555-005056961200-admin] -- Account
> {"id": 2, "name": "admin", "uuid": "0d808973-19be-11eb-9555-005056961200"}'
> is allowed to perform API calls: 0.0.0.0/0,::/0
> 2022-06-01 14:00:52,761 DEBUG [c.c.a.ApiServlet]
> (qtp1850777594-19:ctx-5c391d12 ctx-9cd12123 ctx-6326bb8c) (logid:fb2dbf4b)
> ===END===  172.31.29.44 -- GET
> listall=True=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw=listVpnConnections=json=3=2022-06-01T08%3A43%3A35%2B=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
> 2022-06-01 14:00:52,862 INFO  [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Host 172.31.21.5
> OpaqueRef:d1a2d70a-25bd-37b3-c581-2249ccf88fc0: Host 172.31.21.5 is already
> setup.
> 2022-06-01 14:00:52,868 WARN  [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-13:ctx-797e05c2) (logid:3256e16e) callHostPlugin failed for
> cmd: setIptables with args  due to The requested plugin could not be found.
> 2022-06-01 14:00:52,869 WARN
> [c.c.h.x.r.w.x.CitrixSetupCommandWrapper] (DirectAgent-13:ctx-797e05c2)
> (logid:3256e16e) Unable to setup
> com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed
> for cmd: setIptables with args  due to The requested plugin could not be
> found.
> at
> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:367)
> at
> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4706)
> at
> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:63)
> at
> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:45)
> at
> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
> at
> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1758)
>   

Re: Ubuntu 22.04 Release

2022-06-03 Thread Andrija Panic
You can find updated packages on our ShapeBlue repo here:
http://packages.shapeblue.com/cloudstack/upstream/debian/4.16/ (same for
EL7 and EL8) - the patch for VNC password (and io_uring) is there. (the
packages are the latest one, with -shapeblue1 extension)

Cheers,

On Thu, 2 Jun 2022 at 14:59, Jorge Luiz Correa
 wrote:

> Hi! I've set up some servers with Ubuntu 22.04 LTS: 2 management servers, 2
> databases, 2 secondary storage and 4 processor nodes.
>
> In my tests I've used the repository from focal:
>
> http://download.cloudstack.org/ubuntu focal 4.16
>
> As cloudstack packages do not require a lot of dependencies, the
> installation was well finished. After all configuration, the cloud is up.
>
> But, I have a main problem, already reported and fixed.
>
> https://github.com/apache/cloudstack/pull/6244
>
> Until now, no System VMs can be deployed. Although the issue was fixed, I'm
> waiting until the repository package gets updated. Or, a new one specific
> to jammy be created. I've seen that the last updates to cloudstack packages
> were done on April 4 (in my servers). The issue was fixed a little bit
> later in April.
>
> MTC
>
> tks!
>
> Em qua., 1 de jun. de 2022 às 04:14, Loth 
> escreveu:
>
> > Hello Users,
> >
> > Has any work been done regarding testing Cloudstack with Ubuntu 22.04,
> > and if so, which versions?
> >
> > Thanks for any news.
> >
>
> --
> __
> Aviso de confidencialidade
>
> Esta mensagem da
> Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), empresa publica
> federal  regida pelo disposto  na Lei Federal no. 5.851,  de 7 de dezembro
> de 1972,  e  enviada exclusivamente  a seu destinatario e pode conter
> informacoes  confidenciais, protegidas  por sigilo profissional.  Sua
> utilizacao desautorizada  e ilegal e  sujeita o infrator as penas da lei.
> Se voce  a recebeu indevidamente, queira, por gentileza, reenvia-la ao
> emitente, esclarecendo o equivoco.
>
> Confidentiality note
>
> This message from
> Empresa  Brasileira de Pesquisa  Agropecuaria (Embrapa), a government
> company  established under  Brazilian law (5.851/72), is directed
> exclusively to  its addressee  and may contain confidential data,
> protected under  professional secrecy  rules. Its unauthorized  use is
> illegal and  may subject the transgressor to the law's penalties. If you
> are not the addressee, please send it back, elucidating the failure.
>


-- 

Andrija Panić


Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4

2022-06-03 Thread Boris Stoyanov
+1 (binding)

Did some simple lifecycle operations around Users, VMs, Networks, Volumes, 
Infra and Offerings. Did not had any issues. LGTM

Bobby.

From: Nicolas Vazquez 
Date: Tuesday, 31 May 2022, 20:40
To: d...@cloudstack.apache.org , users 

Subject: [VOTE] Apache Cloudstack 4.17.0.0 RC4
Hi all,

I have created a 4.17.0.0 release (RCR) with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
Commit: c56220fcf2348c7809331dcc266775f3d7130fe6

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

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

The vote will be open until 6th June 2022.

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)

Regards,
Nicolas Vazquez