The packer log hadn't given any extra information when I had been using it.
We've considered network issues but haven't seen any evidence of them. I'm using Packer 0.12.2, our Jenkins box(which also has the issue) is on 1.0.0. I'll try out the newest 1.0.2 locally and see if that fixes it, but looking through the changelog(from 1.1 forward since we're having the issues on 1.0), I'm not seeing much mention of something that might fix this behavior. If it does fix it I'll post back here as such. On Monday, July 10, 2017 at 10:07:17 AM UTC-5, Rickard von Essen wrote: > > If you add PACKER_LOG=1 PACKER_LOG_PATH=./packer.log > > You may catch some more info. I expect that there isn't any network > issues, you are probably building in the same datacenter. Which packer > versions do you use? > > > On Jul 10, 2017 16:27, "Austin D" <[email protected] <javascript:>> wrote: > > My team is having some intermittent issues with the file provisioner > failing for an unknown reason. It doesn't return why it failed, only that > it did. > > 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 Upload dir > './build/cookbooks' to '/tmp' >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 opening new ssh session >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 Starting remote scp process: >> scp -rvt /tmp >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 Started SCP session, >> beginning transfers... >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 No trailing slash, creating >> the source directory name >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 SCP: starting directory >> upload: cookbooks >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 SCP session complete, >> closing stdin pipe. >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 Waiting for SSH session to >> complete. >> 2017/07/07 11:06:09 packer: 2017/07/07 11:06:09 non-zero exit status: 1 >> >> > I've poked around inside the build instance after one of these failures, > and haven't been able to find much out about what is going on here. It > happens a couple times a day max when trying to re-create it, but it's a > slight annoyance in our deployment pipeline that I'm trying to iron out. > > Has anyone seen this before and know what could be going on? Any ideas on > where to look to debug this further? > > We're building on RHEL 6 and 7. > > -- > 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/packer-tool/d05d0b41-ecc2-4025-9061-d2323a57497a%40googlegroups.com > > <https://groups.google.com/d/msgid/packer-tool/d05d0b41-ecc2-4025-9061-d2323a57497a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/df17af9c-c947-47f1-98f6-ca148796e55f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
