Sorry for my late response. I have added your issue to our ticket-system. I will let you know if/when it will be fixed.
Thanks for your bug report! Regards, Daniele On Wednesday, August 19, 2015 at 4:01:08 AM UTC+8, [email protected] wrote: > > *bump*. > > > Has anybody been able to confirm this issue? > > > > On Thursday, August 13, 2015 at 1:29:07 PM UTC-7, [email protected] > wrote: >> >> Hey there. >> >> I have been able to confirm this w/ the latest OSS Version of scalr on >> both Chrome and Safari (latest of each, on up to date OSX). >> >> Here's what you need to do in order to reproduce. I have attached >> screenshots below to demonstrate. >> >> >> >> 0) create a farm or edit an existing farm with at least one farm role set >> to use Chef for bootstrapping. >> >> 1) from the "bootstrap with chef" tab, change the chef environment from >> it's current setting to any other setting. In the included screenshots, i >> change an environment from dev to dev14. >> >> 2) the run list for the node (role `graphite`) has been changed to BLANK. >> >> 3) Saving the farm will result in future nodes coming up w/ an empty run >> list with the correct environment. Cloning this farm will result in a new >> farm, with the existing roles. The chef environment will be correct, and >> the run list will be BLANK >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
