Hide Forgot
Azure public clouds support managed disks/managed images. The Azure Stack currently does not and inventory collection fails due to us querying these APIs and getting 404 error responses back. The inventory collection process could be changed to simply catch exceptions when a 404 error is hit while trying to grab inventory on those resources but we probably need a more robust solution (i.e. check for support of disks/images before trying to collect inventory on them)
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
It shouldn't be too difficult to add a check to see if managed images and disks are supported.
Since this is a potential issue for at least one other region - USGov Iowa according to their support matrix - I think it's worth adding a check anyway.
https://github.com/ManageIQ/manageiq-providers-azure/pull/257
Ok, I think I have a working solution: https://github.com/ManageIQ/manageiq-providers-azure/pull/321 Please apply those changes and see if it works. You should see a warning in the logs for managed disks not being supported.
I got this error [----] E, [2019-01-10T08:05:43.381825 #8068:948f68] ERROR -- : [NoMethodError]: undefined method `cached_resource_provider_service' for #<ManageIQ::Providers::Azure::Inventory::Collector::CloudManager:0x0000000007a6b538> Method:[block (2 levels) in <class:LogProxy>] Should I also modify some config?
Brandon, since this only affected Stack, and since Stack is a separate provider now, can this be closed? Assuming it works with the azure-stack provider, of course.
Yes, looks like Angelina verified this in 5.11.0.7 using an Azure Stack provider so I think we're good here. Moving to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4199