Re: [packer] AMI Tags not propagated to other accounts?

2018-04-09 Thread Byte Flinger 
Thank you very much for the answer Rickard. It is too bad one cannot rely
on that functionality but at least I am now aware of the issue.

On Fri, 6 Apr 2018, 11:08 Rickard von Essen, 
wrote:

> This is how AWS works. AMI's can be shared with other accounts, basically
> giving them read access. But tags are a separate construct, metadata
> separate from the resources they "tag". They are not shared and and not
> visible from the other account just because the AMI is shared.
>
> The other account can add it's own tags to an AMI shared with it.
>
> Hope that clears things up a bit. Feel free to follow up with further
> questions.
>
> On Fri, Apr 6, 2018, 09:44 Byte Flinger  wrote:
>
>> I have built an AWS AMI image using the EBS backed builder and I set the
>> "ami_users" to a couple of different accounts so the ami is available for
>> using in all of these acounts.
>>
>> I noticed that the AMI in the account which I built the image on has all
>> the AMI tags I configured in the packer configuration however the other
>> accounts have no tags whatsoever in that same ami.
>>
>> Is anybody aware if this is by design or an issue with packer ebs backed
>> builder?
>>
>> Regards
>> Byte
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/packer/issues
>> IRC: #packer-tool on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Packer" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to packer-tool+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/packer-tool/521def5a-952a-424b-9576-ce44ef28f8d2%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/CALz9Rt88%2BPZckxHCBBN09pic4geL0eD-aQn7VXX8sz-HdUotiQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CAELTqdrU8cRwarL44zU4sqqWTd-D3G7jmNF9u3SP8m%3Db1jPoSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [packer] Packer not working when setting winrm_password

2018-04-09 Thread Rickard von Essen 
If you set winrm_password you have to ensure that that pwd is allowed to
connect to the VM. When not setting one AWS will set a random one and then
Packer reads that. Did you set the password with cloudbase-init? or did the
source AMI already have this password baked into it?

On 30 March 2018 at 20:02,  wrote:

> Sorry, wasn't able to get it, but the error is that it just times out
> after about 10min. Any idea why it would work without a set password but
> timeout after setting a password.
>
> On Thursday, March 29, 2018 at 10:53:14 PM UTC-7, Rickard von Essen wrote:
>>
>> There is no error in that log.
>>
>> On Fri, Mar 30, 2018, 00:30  wrote:
>>
>>> When creating a Windows AMI on AWS, I am getting stuck at "Waiting for
>>> WinRM to become available" when I set winrm_password.
>>> But when I remove winrm_password, it is able to build the AMI. Anyone
>>> have an suggestions what might be going on here?
>>>
>>> This is what I see in the console:
>>>
>>> ==> amazon-ebs: Creating temporary keypair:
>>> packer_5abd5b4e-51d1-1f2f-ec27-86b7c804c5a9
>>> ==> amazon-ebs: Launching a source AWS instance...
>>> ==> amazon-ebs: Adding tags to source instance
>>> amazon-ebs: Adding tag: "Name": "Packer Builder"
>>> amazon-ebs: Instance ID: i-0dd75cb661ee63bd7
>>> ==> amazon-ebs: Waiting for instance (i-0dd75cb661ee63bd7) to become
>>> ready...
>>> ==> amazon-ebs: Skipping waiting for password since WinRM password set...
>>> ==> amazon-ebs: Waiting for WinRM to become available...
>>>
>>> Seems weird that winrm_password is causing it to failed..
>>>
>>> "winrm_password": "TestPassword123!"
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/packer/issues
>>> IRC: #packer-tool on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Packer" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to packer-tool...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/packer-tool/d3b00ef8-319c-4d78-b0be-238cd38762ac%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/packer-tool/56d53263-19cc-479f-9ed1-e4a19cf1856e%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CALz9Rt-To9%3DH09%2Br9cXLgbP-%2BYoX9ME1_UpR95kaVVZzrdY-kQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [packer] Windows 2016 AMI AWS error

2018-04-09 Thread Megan Marsh 
Are you sure your file InitializeInstance.ps1 exists on the guest already?
you may need to put it in place with the file provisioner before running
your powershell provisioner.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CAGPV1urLLoivzwJf%2BahQJR_tFFw2eWtdVbpr-Azms6wjrv%2BbJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [packer] Packer v1.2.1 - WinRM communicator timeout

2018-04-09 Thread Dave Nelson 
Hi Megan,

No worries at all.  Thanks for getting back to me :o)

The test JSON file and WinRM config files are here:

https://github.com/DaveDingle75/packer-windows

If you need anything else, let me know.

Cheers,

Dave.


On Friday, April 6, 2018 at 5:17:27 PM UTC+1, Megan Marsh wrote:
>
> Sorry to hear you're having trouble :( . Can you share the relevant parts 
> of your Packer config? It'll make it a lot easier to troubleshoot.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/42731364-fa71-4d4b-91fe-8d549e997d13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[packer] Windows 2016 AMI AWS error

2018-04-09 Thread James W 
Hi,

I am trying to build a Windows 2016 AMI for AWS, attached is my build.json 
file. I am getting an error when trying to run "InitializeInstance.ps1 
-Schedule" as inline commands. 

==> amazon-ebs: Provisioning with Powershell...
==> amazon-ebs: Provisioning with powershell script: 
C:\Users\ADMINI~1\AppData\Local\Temp\2\packer-powershell-provisioner933417395
amazon-ebs: 
C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeInstance.ps1 : 
The
amazon-ebs: term 
'C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeInstance.ps1'
amazon-ebs: is not recognized as the name of a cmdlet, function, script 
file, or operable
amazon-ebs: program. Check the spelling of the name, or if a path was 
included, verify
amazon-ebs: that the path is correct and try again.
amazon-ebs: At 
C:\Windows\Temp\script-5acaf9bd-4306-241c-77fd-d6adb74e86bd.ps1:1 char:1
amazon-ebs: + 
C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeInstance.ps1
amazon-ebs: -Schedul ...
amazon-ebs: + 
~~~
amazon-ebs: + CategoryInfo  : ObjectNotFound: 
(C:\ProgramData\...izeInstance.p
amazon-ebs:s1:String) [], CommandNotFoundException
amazon-ebs: + FullyQualifiedErrorId : CommandNotFoundException
amazon-ebs:
==> amazon-ebs: Stopping the source instance... 


Has anyone else run into this error ?

James

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/fd5f6f6f-224f-415a-adc1-d48330476bfa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Windows 2016 Base.json
Description: application/json