Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

Exception raised when attempting to get a resource URI from a remote respository entity #397

Open
blittle01 opened this issue Oct 16, 2018 · 1 comment

Comments

@blittle01
Copy link

Scenario/Intent

When calling backups.update_remote_archive, the task runs to completion normally and is successful, but following the task termination, task_monitor.py attempts to perform a get on the remote backup resource. OneView throws an HTTP_METHOD_NOT_ALLOWED exception in this case since a GET is not allowed on resources of type '/rest/backups/remotearchive/...' - This is probably similar to the case of "/rest/appliance/support-dumps" which is excluded at line 246 of task_monitor.py - We probably need to exclude the remote backup image in the same manner.

Environment Details

  • **OneView SDK Version: 4.7.1
  • **OneView Appliance Version: 4.2 and 5.0 have both exhibited this issue
  • OneView Client API Version: [API version listed in your configuration file or dictionary]
  • **Python Version: 3.6
  • **Platform: Windows 7

Steps to Reproduce

Create a backup using backups.create
Upload the backup to a remote server using backups.update_remote_archive
See exception thrown following update_remote_archive task completion

Expected Result

A successful upload of a backup file should not result in an exception

Actual Result

The exception HTTP_METHOD_NOT_ALLOWED is thrown from within task_montor.py line 259.

Suggested fix is to add the following in task_monitor.py at line 249 :

if resource_uri and resource_uri.startswith("/rest/backups/remotearchive/"):
return task, resource_uri

@sijeesh
Copy link
Collaborator

sijeesh commented Jul 23, 2019

@blittle01 , Apology for the late replay and thanks for pointing out this issue.
We will have a look into this and fix it in the next version of the SDK.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants