Comment 2 for bug 1287393

Revision history for this message
Charles Butler (lazypower) wrote :

-- self monologue for future reference begins now --

Agreed - i had to go back through the deployment to remember why i did this. The exact output on AWS from unit-get private-address is as follows:

unit-get private-address
domU-12-31-39-06-79-5E.compute-1.internal

The need for nslookup was the resolve that address to an IPV4 format
nslookup $(unit-get private-address) | grep Add | grep -v '#' | cut -f 2 -d ' '
10.208.126.172

So - in summation, I suppose this should be a fallback method if private-address is not in numeric form. I wasn't considering LXC the primary provider for this modification when it was written, thus it was not tested elsewhere. Should be a simple fix.