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

"type" field in migratable vc domains is invalid #431

Open
Manoj-M-97 opened this issue Apr 22, 2019 · 1 comment
Open

"type" field in migratable vc domains is invalid #431

Manoj-M-97 opened this issue Apr 22, 2019 · 1 comment

Comments

@Manoj-M-97
Copy link

Scenario/Intent

[What you are trying to achieve but can't?]
I am trying to use migratable VC domains to get the compatibility report of c7000 and synergy.
But it gives an error that the "type" field in the json is invalid.

Environment Details

  • OneView SDK Version: 4.80
  • OneView Appliance Version: 4.0
  • OneView Client API Version: 600
  • Python Version: 3.7.1
  • Platform: Windows , Server 2012

Steps to Reproduce

[What are the complete steps needed to do in order to reproduce your problem?]
Clone the repository. Run the function 'Collect_Data_from_C7000' in the migratable_vc_domains.py which is in the examples folder

Expected Result

[What do you expect to happen after taking the steps above?]
The compatibility report will be generated.

Actual Result

[What actually happens after the steps above? Include error output or a link to a gist.]
Error : the "type" field in json is invalid. The report is not generated.

Details

In the file "migratable_vc_domains.py" which is present in \hpOneView\resources\servers, the call for make_migration_information is failing as the "type" is assigned to "migratable-vc-domains". There is no way to change this(not a parameter to be given). The value presently for the type is "MigratableVcDomainV300" (this is working). So the change that is done and works for us is that to add a keyword parameter for with the name 'type' which has a default as "migratable-vc-domains" and then while calling the function, we pass type="MigratableVcDomainV300".

@madhav-bharadwaj
Copy link
Member

Hi @Manoj-M-97, Thanks for raising this. Yes this should throw an error as this is the type in API v200. We haven't added support for this resource for API600 yet.
Since you already have a workaround for this, can you raise this as a PR so that we can review it? We would like to track this as your contribution to our repo :)

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