I'm also unable to reproduce this issue in my 4.1.1 env

Screenshot for added and attached 1 root and 3 data disks
https://www.diigo.com/item/image/3qjce/wnhb

Screenshot that stop and start VMs have been successful
https://www.diigo.com/item/image/3qjce/q4i6

Not adding any longs as nothing was out of the ordinary there..

> -----Original Message-----
> From: Musayev, Ilya [mailto:imusa...@webmd.net]
> Sent: Friday, July 26, 2013 1:04 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE] Apache Cloudstack 4.1.1 (Second Round)
> 
> Nicolas,
> 
> This issue exists in 4.1.0, 4.2.0 and as you can see has not been fixed in 
> 4.1.1
> 
> Since no-one is assigned to work on this ticket and we made no claims that it
> has been fixed in 4.1.1, IMHO posting "-1" is a bit too harsh.
> 
> While I am all for fixing this issue and will also look into this problem (we 
> are
> vpshere shop and I did not know if this problem), we need to raise
> awareness on this bug and not block 4.1.1 release, because this specific issue
> has not yet been addressed. We did address about 20+ bug fixes. If we were
> to follow a methodology of blocking every single release because a specific
> issue exists and has not been addressed, there is a good chance we will
> never release anything.
> 
> As you know, open source projects are ran by volunteers (and while many
> developers are paid by company X), in general we do not make
> commitments of any kind - we can try out best, but if it does not happen, we
> will try on the next release. Therefore ACS community cannot guarantee that
> issue X or feature Y will be added or resolved in the next release.
> 
> With that in mind, let's work on raising awareness for this problem.
> 
> Regards
> ilya
> 
> 
> 
> > -----Original Message-----
> > From: nicolas.lamira...@orange.com
> > [mailto:nicolas.lamira...@orange.com]
> > Sent: Friday, July 26, 2013 3:26 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.1.1 (Second Round)
> >
> > Hi,
> >
> > -1 due to the opened issue :
> >
> > - https://issues.apache.org/jira/browse/CLOUDSTACK-2895
> >
> > Le 26/07/2013 05:42, Marcus Sorensen a écrit :
> > > +1 binding, CentOS 6.4. Used devcloud-kvm advanced zone marvin
> > > +config,
> > > started up a VPC, registered a template, started a VM. Tested NFS,
> > > local, CLVM primary storage.
> > >
> > > One of these days I'll get around to making an Ubuntu devcloud-kvm.
> > >
> > > On Thu, Jul 25, 2013 at 2:54 PM, Simon Weller <swel...@ena.com> wrote:
> > >> +1
> > >>
> > >> Built NONOSS rpms and deployed on RHEL 6.3
> > >>
> > >> Tested vm creation + deletion, network creation + deletion,
> > >> template
> > creation + deletion.
> > >>
> > >> - Si
> > >>
> > >> ----- Original Message -----
> > >>
> > >> From: "Ilya Musayev" <imusa...@webmd.net>
> > >> To: dev@cloudstack.apache.org
> > >> Sent: Thursday, July 25, 2013 1:04:27 PM
> > >> Subject: [VOTE] Apache Cloudstack 4.1.1 (Second Round)
> > >>
> > >> Hi All,
> > >>
> > >> I've created a 4.1.1 release, with the following artifacts up for a vote:
> > >>
> > >> Git Branch and Commit SH:
> > >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog
> > >> ;h
> > >> =refs/heads/4.1
> > >> Commit: d2c646f0a434831bd5aef88b5692c108fe26e718
> > >>
> > >> Release notes:
> > >>
> > >> http://jenkins.cloudstack.org/view/4.1/job/docs-4.1-releasenotes/23
> > >> /
> > >>
> > >>
> > >> Source release (checksums and signatures are available at the same
> > >> location):
> > >> https://dist.apache.org/repos/dist/dev/cloudstack/4.1/
> > >>
> > >> PGP release keys (signed using B7B5E7FD):
> > >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >>
> > >> Vote will be open for 72 hours.
> > >>
> > >> 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)
> > >>
> > >> d2c646f0a434831bd5aef88b5692c108fe26e718
> > >>
> > >
> > >
> >
> >
> > --
> > Nicolas Lamirault
> >
> >
> __________________________________________________________
> >
> __________________________________________________________
> > _____
> >
> > Ce message et ses pieces jointes peuvent contenir des informations
> > confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
> > exploites ou copies sans autorisation. Si vous avez recu ce message
> > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
> > que les pieces jointes. Les messages electroniques etant susceptibles
> > d'alteration, Orange decline toute responsabilite si ce message a ete 
> > altere,
> deforme ou falsifie. Merci.
> >
> > This message and its attachments may contain confidential or
> > privileged information that may be protected by law; they should not
> > be distributed, used or copied without authorisation.
> > If you have received this email in error, please notify the sender and
> > delete this message and its attachments.
> > As emails may be altered, Orange is not liable for messages that have
> > been modified, changed or falsified.
> > Thank you.
> >
> 
> 


Reply via email to