Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Ansible playbook error - 'Resource temporarily unavailable'
2020-11-17
08:27 AM
4,318 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am trying out some of the examples on netapp.io site, namely creating a NetApp Volume, and I get the following error message:
...
"msg": "Error fetching volume AnsibleTestVolume : NetApp API failed. Reason - URL error:URLError(error(11, 'Resource temporarily unavailable')
Any ideas on what I am doing wrong?
Solved! See The Solution
1 ACCEPTED SOLUTION
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Team,
Thank you for the feed-back. In the meantime we were able to solve the problem. We had for this particular case no ssh connection to the target. After the connect problem was fixed, the playbook ran without problem.
BR
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Storageservice,
Unfortunately the "Resource temporarily unavailable" is a generic error message, but it is commonly caused by a connection issue. You can modify the ansible.cfg file to the following to output more context around the "resource temporarily unavailable" error.
[DEFAULTS]
stdout_callback = debug
Regards,
Team NetApp
Team NetApp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello STORAGESERVICE,
Are you still having issues with creating volumes? Were you able to check what @ttran have recommended you to check?
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Team,
Thank you for the feed-back. In the meantime we were able to solve the problem. We had for this particular case no ssh connection to the target. After the connect problem was fixed, the playbook ran without problem.
BR
