Hi Mike,

For 1 - it's possibly a UI bug, have you tried the legacy UI or just the 
default/new UI? Or were you using APIs to deploy your zone? Please raise a bug 
explaining how to reproduce the issue: 
https://github.com/apache/cloudstack/issues

For 2- For your secondary storage, did you setup NFS exports correctly. I would 
look at file and mod permissions of /var/lib/cloudstack/ folders where the 
systemvm folder is mounted to copy the systemvm.iso file. What's the output of 
"id cloud"? For this issue, was the test done on a new environment or was an 
upgrade attempted, furthermore what was your management server distribution?

Regards.

________________________________
From: Andrija Panic <andrija.pa...@gmail.com>
Sent: Friday, June 18, 2021 02:45
To: users <us...@cloudstack.apache.org>; Corey, Mike <mike.co...@sap.com>
Cc: dev@cloudstack.apache.org <dev@cloudstack.apache.org>
Subject: Re: Issues Found Apache CloudStack 4.15.1.0 (RC2)

@Corey, Mike <mike.co...@sap.com>

can you please raise a GH issue with the same description, and also vote -1
on the RC2 release, with the link to that GH issue?

THanks,
Andrija

On Thu, 17 Jun 2021 at 18:09, Corey, Mike <mike.co...@sap.com.invalid>
wrote:

> Hi,
>
> Thanks for pushing this out.  I'm looking forward to trying the
> template/instance deployment in my VMware PILOT.
>
> A couple items I noticed off the "new" build are:
>
> 1 - During zone creation with VMware and setting up the physical networks
> - adding the traffic label to use a VDS does NOT keep/take/apply.  Once the
> zone is created and you go into the physical networks, the VDS traffic
> label is blank when it should be in this format
> "vSwtichName,VLAN,typeofswitch".  The only physical network traffic label
> that saved during zone setup wizard was for the Management stack; my
> storage and guest physical network traffic labels did not save from the
> wizard.
>
> 2 - Initial SystemVM deployment, the secondary storage permission do not
> allow the copy of the systemvm.iso to the secondary/systemvm/ folder.  I
> had to first create a /mnt/secondary/systemvm/ folder and chmod -R for this
> copy to function.
>
> More to come...
>
> Mike
>
> -----Original Message-----
> From: Rohit Yadav <ro...@apache.org>
> Sent: Wednesday, June 16, 2021 12:28 PM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: [VOTE] Apache CloudStack 4.15.1.0 (RC2)
>
> Hi All,
>
> I've created a 4.15.1.0 release, with the following artifacts up for a
> vote:
>
> Git Branch:
> https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210616T2128
> Commit SHA:
> 3afd37022b9dac52cd146dccada6012e47a80232
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open for the next week until 22 June 2021.
>
> 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)
>
> For users convenience, the packages from this release candidate and 4.15.1
> systemvmtemplates are available here:
> https://download.cloudstack.org/testing/4.15.1.0-RC2/
> https://download.cloudstack.org/systemvm/4.15/
>
> Documentation is not published yet, but the following may be referenced for
> upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
> registered prior to upgrade)
>
> https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade
>
> Regards.
>


--

Andrija Panić

 

Reply via email to