From 679b7dce635830bc02ab38a8e5f92c345189802c Mon Sep 17 00:00:00 2001
From: johnstudarus <john@jhlconsulting.com>
Date: Thu, 22 Nov 2018 08:53:24 -0800
Subject: [PATCH] Update guide_packet.rst (#49007)

Properly parses the returned data to get the device data and IP address.


+label: docsite_pr
---
 docs/docsite/rst/scenario_guides/guide_packet.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docsite/rst/scenario_guides/guide_packet.rst b/docs/docsite/rst/scenario_guides/guide_packet.rst
index 0f419bf7fe2..7b3c2076338 100644
--- a/docs/docsite/rst/scenario_guides/guide_packet.rst
+++ b/docs/docsite/rst/scenario_guides/guide_packet.rst
@@ -178,7 +178,7 @@ The following playbook will create an SSH key, 3 Packet servers, and then wait u
           port: 22
           state: started
           timeout: 500
-        loop: "{{ newhosts.devices }}"
+        loop: "{{ newhosts.results[0].devices }}"
 
 
 As with most Ansible modules, the default states of the Packet modules are idempotent, meaning the resources in your project will remain the same after re-runs of a playbook. Thus, we can keep the ``packet_sshkey`` module call in our playbook. If the public key is already in your Packet account, the call will have no effect.