Hi Ben,
This is expected. Only a handful of changes are applied to running
instances
<https://scalr-wiki.atlassian.net/wiki/display/docs/Editing+a+Running+Farm>,
while most setting changes will require a respin of the instance for the
settings to apply. Can you terminate the instance, let Scalr spin up a
replacement, and verify that your hostname format is correctly applied on
the replacement instance?
Many thanks,
Wm. Marc O'Brien
Scalr Technical Support
On Monday, November 14, 2016 at 11:51:07 AM UTC-7, Ben West wrote:
>
> It looks like changes to "Server Hostname Format" are not applied to a
> running Server in AWS, even if I put that machine through suspend/resume
> cycle. Changing the hostname locally on the machine is possible via
> hostnamectl, but it looks like scalarizr is still coming in and reverting
> it at some point afterwards:
>
> scalarizr_debug.log:2016-11-11 19:14:07,306-06:00 - DEBUG -
> common.utils.subprocess2 - Executing subprocess: ('hostname
> ip-XX-XX-XX-XX',)
>
> Is it possible to make changes to Server Hostname Format "stick" on a live
> Server?
>
> This particular is happening on a CentOS v7.2.1511 machine with this agent:
>
> scalarizr-ec2-4.10.2-1.x86_64
> scalarizr-4.10.2-1.el5.x86_64
>
>
--
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.
