Bug 1434988
Summary: | [Regression] Azure provider refresh fails | |||
---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Nandini Chandra <nachandr> | |
Component: | Providers | Assignee: | Daniel Berger <dberger> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nandini Chandra <nachandr> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 5.8.0 | CC: | cpelland, jfrey, jhardy, obarenbo, simaishi, tachoi | |
Target Milestone: | GA | Keywords: | Regression, TestOnly | |
Target Release: | 5.9.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | azure:refresh | |||
Fixed In Version: | 5.9.0.1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1438092 1438094 1438095 (view as bug list) | Environment: | ||
Last Closed: | 2018-03-06 15:21:25 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1438092, 1438094, 1438095 |
Description
Nandini Chandra
2017-03-22 20:36:24 UTC
I'm hitting an error, though a different one. I've created an issue on github: https://github.com/ManageIQ/azure-armrest/issues/264 The PR above solved one issue, but now I'm hitting the same issue as the OP: It can be duplicated like so just using the azure-armrest gem: tds = Azure::Armrest::TemplateDeploymentService.new(conf) tds.get_template("nestedTemplate", "miq-automate") Sorry, I meant https://github.com/ManageIQ/azure-armrest/pull/265 in the previous comment. Anyway, we're going to need to change our get_template method and update the gem version: https://github.com/ManageIQ/azure-armrest/pull/266 PR: https://github.com/ManageIQ/manageiq-providers-azure/pull/42 https://github.com/ManageIQ/manageiq-gems-pending/pull/100 *** Bug 1431912 has been marked as a duplicate of this bug. *** Verified in 5.9.0.4 |