CFP - CloudStack Collaboration Conference

2022-06-21 Thread Jamie Pell 
Hi all,

Just a reminder that the CFP is open for CloudStack Collaboration Conference 
2022.

I would encourage anyone interested in submitting a talk to do so sooner than 
later, to help maximise the chance of being accepted 
-https://docs.google.com/forms/d/e/1FAIpQLSeE2o9IZTVHaPvsBJXQW2gZjZqxjZ7CynUJb9MZ22s7uyzyDA/viewform

If you have any questions, feel free to ask.

Kind regards,

Re: ACS Upgrade Failed :: Xenserver

2022-06-21 Thread Ranjit Jadhav 
Hello,

Thanks for the update, I tried with bionic but got the error below. After
changing to focal it worked, both management and usage services are online.
But the SystemVM version is still 4.16.1. Shall we import the template
again?  What should be the approach now.


root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created

or been moved out of Incoming.
The following information may help to resolve the situation:




*The following packages have unmet dependencies: cloudstack-usage :
Depends: cloudstack-common (= 4.17.0.0~focal) but 4.17.0.0~bionic is to be
installedE: Unable to correct problems, you have held broken
packages.root@cloudstack1:~#*



On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher  wrote:

> Ranjit can you please try the upgrade again?
>
> There was an issue with the mirror for the usage package (4.17.0.0 bionic
> only).
> Should be good now (the mirror might still be syncing, but I bet it is
> already good to go).
>
> Regards,
> Gabriel.
>
> On Mon, Jun 20, 2022 at 6:15 AM Ranjit Jadhav 
> wrote:
>
> > Hello,
> >
> > Thanks for getting back to me. Nothing specific in logs, getting
> following
> > error while we are trying to reinstall the services.
> >
> > =
> > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
> > 4.17.0.0~bionic is to be installed
> > E: Unable to correct problems, you have held broken packages.
> > =
> >
> > Thank you,
> > Ranjit
> >
> > On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala <
> > harikrishna.patn...@shapeblue.com> wrote:
> >
> > > Hi Ranjit,
> > >
> > > CloudStack management and usage have to be on the same version, can you
> > > please check the version of CloudStack usage server and verify if the
> > > upgrade to 4.17 happened properly. If not on 4.17, can you please try
> to
> > > upgrade the usage server?
> > >
> > > Please paste the exact error from the management server or usage server
> > > logs that you are seeing.
> > >
> > > Thanks,
> > > Harikrishna
> > >
> > > 
> > > From: Ranjit Jadhav 
> > > Sent: Saturday, June 18, 2022 5:53 PM
> > > To: us...@cloudstack.apache.org ; dev <
> > > dev@cloudstack.apache.org>
> > > Subject: ACS Upgrade Failed :: Xenserver
> > >
> > > Hello,
> > >
> > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we
> > faced
> > > the following issue. It appears that "cloudstack-management" and
> > > "cloudstack-usage" requires different versions of cloudstack-common.
> > >
> > > With cloudstack-common=4.17 Management, services are working but Usage
> > > services are asking for 4.16.1.0~bionic
> > >
> > > ==
> > > The following packages have unmet dependencies:
> > >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
> > > 4.17.0.0~bionic is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > > ==
> > >
> > > We followed the steps below to upgrade ACS
> > >
> > >
> > >
> >
> https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers
> > >
> > > The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng)
> > >
> > > Any guidance would be appreciated.
> > >
> > > Thank you
> > >
> > >
> > >
> > >
> >
>

Re: ACS Upgrade Failed :: Xenserver

2022-06-21 Thread Ranjit Jadhav 
While trying to switch back to Bionic from Focal, please advice


root@cloudstack1:~# sudo apt-get install
cloudstack-management=4.17.0.0~bionic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cloudstack-management : Depends: cloudstack-common (= 4.17.0.0~bionic) but
4.17.0.0~focal is to be installed
E: Unable to correct problems, you have held broken packages.
root@cloudstack1:~#


On Tue, 21 Jun 2022 at 18:32, Ranjit Jadhav 
wrote:

> Hello,
>
> Thanks for the update, I tried with bionic but got the error below. After
> changing to focal it worked, both management and usage services are online.
> But the SystemVM version is still 4.16.1. Shall we import the template
> again?  What should be the approach now.
>
> 
> root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
>
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
>
>
>
> *The following packages have unmet dependencies: cloudstack-usage :
> Depends: cloudstack-common (= 4.17.0.0~focal) but 4.17.0.0~bionic is to be
> installedE: Unable to correct problems, you have held broken
> packages.root@cloudstack1:~#*
> 
>
>
> On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher 
> wrote:
>
>> Ranjit can you please try the upgrade again?
>>
>> There was an issue with the mirror for the usage package (4.17.0.0 bionic
>> only).
>> Should be good now (the mirror might still be syncing, but I bet it is
>> already good to go).
>>
>> Regards,
>> Gabriel.
>>
>> On Mon, Jun 20, 2022 at 6:15 AM Ranjit Jadhav 
>> wrote:
>>
>> > Hello,
>> >
>> > Thanks for getting back to me. Nothing specific in logs, getting
>> following
>> > error while we are trying to reinstall the services.
>> >
>> > =
>> > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage
>> > Reading package lists... Done
>> > Building dependency tree
>> > Reading state information... Done
>> > Some packages could not be installed. This may mean that you have
>> > requested an impossible situation or if you are using the unstable
>> > distribution that some required packages have not yet been created
>> > or been moved out of Incoming.
>> > The following information may help to resolve the situation:
>> >
>> > The following packages have unmet dependencies:
>> >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
>> > 4.17.0.0~bionic is to be installed
>> > E: Unable to correct problems, you have held broken packages.
>> > =
>> >
>> > Thank you,
>> > Ranjit
>> >
>> > On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala <
>> > harikrishna.patn...@shapeblue.com> wrote:
>> >
>> > > Hi Ranjit,
>> > >
>> > > CloudStack management and usage have to be on the same version, can
>> you
>> > > please check the version of CloudStack usage server and verify if the
>> > > upgrade to 4.17 happened properly. If not on 4.17, can you please try
>> to
>> > > upgrade the usage server?
>> > >
>> > > Please paste the exact error from the management server or usage
>> server
>> > > logs that you are seeing.
>> > >
>> > > Thanks,
>> > > Harikrishna
>> > >
>> > > 
>> > > From: Ranjit Jadhav 
>> > > Sent: Saturday, June 18, 2022 5:53 PM
>> > > To: us...@cloudstack.apache.org ; dev <
>> > > dev@cloudstack.apache.org>
>> > > Subject: ACS Upgrade Failed :: Xenserver
>> > >
>> > > Hello,
>> > >
>> > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we
>> > faced
>> > > the following issue. It appears that "cloudstack-management" and
>> > > "cloudstack-usage" requires different versions of cloudstack-common.
>> > >
>> > > With cloudstack-common=4.17 Management, services are working but Usage
>> > > services are asking for 4.16.1.0~bionic
>> > >
>> > > ==
>> > > The following packages have unmet dependencies:
>> > >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
>> > > 4.17.0.0~bionic is to be installed
>> > > E: Unable to correct problems, you have held broken packages.
>> > > ==
>> > >
>> > > We followed the steps below to upgrade ACS
>> > >
>> > >
>>

[GitHub] [cloudstack-terraform-provider] Damans227 commented on a diff in pull request #38: Adding new data sources to cloudstack-terraform-proivder

2022-06-21 Thread GitBox 


Damans227 commented on code in PR #38:
URL: 
https://github.com/apache/cloudstack-terraform-provider/pull/38#discussion_r903147546


##
cloudstack/data_source_cloudstack_network_offering_test.go:
##
@@ -0,0 +1,65 @@
+//
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+//
+
+package cloudstack
+
+import (
+   "testing"
+
+   "github.com/hashicorp/terraform/helper/resource"
+)
+
+func TestAccNetworkOfferingDataSource_basic(t *testing.T) {
+   resourceName := "cloudstack_network_offering.net-off-resource"
+   datasourceName := "data.cloudstack_network_offering.net-off-data-source"
+
+   resource.Test(t, resource.TestCase{
+   PreCheck:  func() { testAccPreCheck(t) },
+   Providers: testAccProviders,
+   Steps: []resource.TestStep{
+   {
+   Config: 
testNetworkOfferingDataSourceConfig_basic,
+   Check: resource.ComposeTestCheckFunc(
+   
resource.TestCheckResourceAttrPair(datasourceName, "name", resourceName, 
"name"),
+   ),
+   ExpectNonEmptyPlan: true,
+   },
+   },
+   })
+}
+

Review Comment:
   ```
   
❯ TF_ACC=1 go test -run TestAccNetworkOfferingDataSource_basic -v
   === RUN   TestAccNetworkOfferingDataSource_basic
   --- PASS: TestAccNetworkOfferingDataSource_basic (0.26s)
   PASS
   ok
   
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org