SL provider doesn't reset guest Tcpip Domain in instances from Images

[lonniev]

I just noticed this behavior and it could be my mistake(s) in either construction of the global image or use of it later in the vagrant provisioning.

What I see is that despite explicitly setting sl.hostname and sl.domain to new, unique values, a new instance of a VM that is provided by SoftLayer via the use of sl.image_guid will be provisioned by SL to have the new hostname (good!), a new IP address (whew!), a new DNS record (right!), but the old domain name (bummer!) as it was within the original guest used to form the global image.

I can override that ex post facto, manually and am looking for ways to change it via powershell scripting.

However, I expect that sl.domain = "newDomain.com" should take care of this.

Am I wrong?

[ju2wheels]

@lonniev are you seeing the old domain in the SoftLayer portal or just in the running OS instance itself? If its right in the portal then its most likely something that will have to be done in post install reconfig or something if the SL API is not taking care of resetting. If its the old domain in the portal as well its something that should be raised in an SL ticket to see if thats expected behavior or not.

I dont have resources to test much of this stuff out anymore as I dont have access to the SL infra my previous company used and I didnt do much changes like this during my previous work so im not sure.

[lonniev]

It’s correct in the SL portal and incorrect in the actual OS.

I believe I will have to hack a new chef recipe to tweak TcpIp registry keys to change the domain suffix.

New job, eh? Where are you now if you care to say?

-- 
Lonnie VanZandt
303-900-3048

On 24 June 2015 at 17:33:27, Julio Lajara (notifications@github.com) wrote:

@lonniev are you seeing the old domain in the SoftLayer portal or just in the running OS instance itself? If its right in the portal then its most likely something that will have to be done in post install reconfig or something if the SL API is not taking care of resetting. If its the old domain in the portal as well its something that should be raised in an SL ticket to see if thats expected behavior or not.

I dont have resources to test much of this stuff out anymore as I dont have access to the SL infra my previous company used and I didnt do much changes like this during my previous work so im not sure.

—
Reply to this email directly or view it on GitHub.