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

I3S extract artifact bundle API missing required parameters #398

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

I3S extract artifact bundle API missing required parameters #398

blittle01 opened this issue Oct 24, 2018 · 1 comment

Comments

@blittle01
Copy link

Scenario/Intent

When attempting to deploy the default artifact bundles included with the I3S image, the task does not complete and the bundle extraction does not make the artifacts available to OneView.

Solution:
Add the following parameters to the end of the artifact bundle URI:
extract=true
forceImport=true

The URI sent to the OS deployment client should be constructed as:
artifactBundle['uri'] + "?extract=true&forceImport=true"

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: 1000
  • Python Version: 3.6
  • Platform: Windows 7

Steps to Reproduce

Fresh install of OneView on a Synergy platform with I3S integrated
Create OS deployment server
Create logical enclosure with OS deployment server
Attempt to extract artifact bundles using the artifact_bundles.extract_bundle API
If timeout is default (-1) the call doesn't return and the artifact bundle extraction does not complete.
If the timeout is > 0 the call returns, but the result is the same, the artifact bundle extraction does not complete.

Expected Result

The artifact bundle task should run to completion and the OS deployment plans contained within the artifact bundle should be presented to OneView via the server profile via the OS deployment plan drop-down selection control.

Actual Result

If timeout is default (-1) the call doesn't return and the artifact bundle extraction does not complete.
If the timeout is > 0 the call returns, but the result is the same, the artifact bundle extraction does not complete.

@sijeesh
Copy link
Collaborator

sijeesh commented Jul 23, 2019

@blittle01 , Apologize for the late replay and thank you for pointing out this issue.
We will add this as an enhancement and add it to the next release.

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