cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alena Prokharchyk <>
Subject Re: [ACS41] Blockers for tomorrow's release
Date Thu, 21 Mar 2013 22:03:12 GMT
Just FYI, is not a blocker bug
(double checked with QA, it doesn't block the regression test), and it's
been in the CS since 2.x version of the code.

I'll try to resolve it in a time manner though as its a real issue.


On 3/21/13 2:27 PM, "Sudha Ponnaganti" <> wrote:

>Below are the issues that are blocking tomorrow┬╣s release. Pl  take a
>look at these. I have included Developers in the TO list, I have removed
>bare metal related issues from this list.
>Koushik Das                        CLOUDSTACK-1740          Failed to
>view console
>Min Chen                            CLOUDSTACK-1764
>ListTemplateCommand failed with java.lang.NumberFormatException and
>failed to create default template
>Pradeep Soundararajan                                CLOUDSTACK-1694
>    Issues to start/access Management Server after upgrade from 4.0 to 4.1
>Prasanna Santhanam                     CLOUDSTACK-1736          Ubuntu
>12.04 cloud-setup-management Failed to configure CloudStack Management
>Alena Prokharchyk                          CLOUDSTACK-1771          IPv6
>- Network restart for a dual network , results in the ipv4 address of the
>router to be changed. After netwpork restart , name resolution of the Vms
>Hugo Trippaers                 CLOUDSTACK-216            Templates'
>Source Location Information present on "template_host_ref" and
>"vm_template" tables should refer to Apache System Template Locations
>Hugo Trippaers                 CLOUDSTACK-1252          Failed to
>download default template in VMware
>Kelven Yang                       CLOUDSTACK-1729          Ensure adapter
>execution order in runtime
>Marcus Sorensen                             CLOUDSTACK-354
>Display of storage statistics is wrong.
>Murali Reddy                     CLOUDSTACK-1673          AWS Regions -
>Events - User disable event does not include the UUID of the user that
>was disabled.

View raw message