Yes, this does do the trick. One thing I would like to mention for future readers, you will need to go back to any farm using the changed flavors and reassign them to your desired flavor. Otherwise Scalr will try to use the old instance ID which no longer exists. I don't believe this to be the fault of Scalr, but the fault of OpenStack for changing the Unique ID when simply editing.
Thanks Marc for the quick reply and the on spot help. On Tuesday, July 19, 2016 at 4:04:56 PM UTC-6, Marc O'Brien wrote: > > Hi Dewey, > > Scalr caches instance types for 24 hours. To clean up this cache, please > execute the following commands: > > > 1. cd /opt/scalr-server/embedded/scalr/app/tools > 2. /opt/scalr-server/embedded/bin/php warmup-cache.php > > > Let us know if this does the trick. > > > Many thanks, > Wm. Marc O'Brien > Scalr Technical Support > > > On Tuesday, July 19, 2016 at 4:00:47 PM UTC-6, Dewey wrote: >> >> I was working on something and realized I wanted to adjust a value in the >> OpenStack Flavors. However OpenStack Flavors will change their ID every >> time there is an edit. This throws Scalr off and I can no longer deploy >> with the edited OpenStack Flavors. While I can see that changing the >> flavors in general is undesired, it may still need to be done. Is there a >> way to get Scalr to rescan OpenStack and update the Flavors with the >> correct ID? >> > -- 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.
