Hi Marc, Now that Amazon has pushed the new longer Id format, would it be possible for Scalr to publish a small update in order to support them in the community version? Right now, if I start a new instance, I would be unable to use the auto-snapshot feature, which is something I really depend on.
Thank you Le mardi 6 décembre 2016 15:59:12 UTC-5, Marc O'Brien a écrit : > > Hi Bernard, > > Very glad to hear you have this issue isolated. The longer format > resource ID is supported in the current version of Enterprise Scalr and > will be rolled in to the next release of Open Source Scalr at a later > date. Apologies for the confusion. By the way, welcome to the Scalr Open > Source community! We're excited to have you join us. Please feel free to > post any issues or questions you have moving forward and we will do our > best to lend a hand here. > > P.S. You had previously mentioned migration from Open Source to Hosted > Scalr. It turns out that migration from Open Source to Hosted is not > possible. If you do move to Hosted you would need to start with a new > account from scratch. > > Many thanks, > Wm. Marc O'Brien > Scalr Technical Support > > On Tuesday, December 6, 2016 at 1:52:06 PM UTC-7, Bernard Lefebvre wrote: >> >> Hi Marc, >> >> I have found the issue. It is related to the new Ressource ID length now >> in used by default by Amazon. I have disabled the new length, created a >> volume and I was able to activate the auto-snapshot feature. I am sorry if >> this has been addressed already, but I have searched this forum and the web >> and couldn't find anything related to this issue. >> >> Here is a copy of the EBSManager.log: >> >> EBSManagerProcess@31116 - WARN - Cannot create snapshot for volume >> vol-0127033d34a18538. AWS Error. Request DescribeVolumes failed. Value >> (vol-0127033d34a18538) for parameter volumes is invalid. Expected: >> 'vol-...'. >> >> Thank you >> >> >> Le lundi 5 décembre 2016 14:27:30 UTC-5, Marc O'Brien a écrit : >>> >>> Hi Bernard, >>> >>> I have not been able to replicate this behavior in my test environment. >>> To clarify, this is working fine in other Environments within your same >>> Scalr installation? You noted there is a difference in deployment region >>> in those successful tests. Is there any change to behavior if you >>> replicate the same steps and region that are successful in your other >>> environments? If the problem persists, can you open the Chrome Developer >>> Tools in your browser and verify if any errors thrown in the Console when >>> you attempt to enable automatic snapshots? >>> >>> Many thanks, >>> Wm. Marc O'Brien >>> Scalr Technical Support >>> >>> >>> On Monday, December 5, 2016 at 9:01:00 AM UTC-7, Bernard Lefebvre wrote: >>>> >>>> Hi Marc, >>>> >>>> Any update on this issue? >>>> >>>> This feature is really important for me. >>>> >>>> Thank you >>>> >>>> Le lundi 28 novembre 2016 23:13:26 UTC-5, Bernard Lefebvre a écrit : >>>>> >>>>> Hi, >>>>> >>>>> I have setup a new environment, added the EC2 credentials and tried to >>>>> enable auto-snapshot for a volume, but it just won't enable the option. >>>>> I >>>>> receive the message that the operation was successful and I do not >>>>> receive >>>>> any error message. I can create a snapshot manually and I can access all >>>>> parts of AWS. I have also tried with another IAM user which has full >>>>> access to everything, so I do not think it is a permission issue. >>>>> >>>>> Any idea of what can cause this behaviour? >>>>> >>>>> I am running 5.11.22 (Community Edition) >>>>> >>>>> Thank you >>>>> >>>>> Bernard >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to scalr-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
