Bug 1400204
Summary: | Filter out events from Azure Classic providers | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> | ||||
Component: | Providers | Assignee: | Bronagh Sorota <bsorota> | ||||
Status: | CLOSED ERRATA | QA Contact: | Ievgen Zapolskyi <izapolsk> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.7.0 | CC: | bsorota, cpelland, jfrey, jhardy, obarenbo | ||||
Target Milestone: | GA | Keywords: | ZStream | ||||
Target Release: | 5.7.1 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | azure:event | ||||||
Fixed In Version: | 5.7.1.0 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | 1399296 | Environment: | |||||
Last Closed: | 2017-02-27 19:25:44 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | Azure | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1399296 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Comment 2
CFME Bot
2017-01-09 16:35:41 UTC
Bronagh, Actually, I havn't noticed any create/start/stop/remove events related to classic event. However, event_streams contains deployment messages for class vm created by me. I've attached those events. Could you confirm that such events shouldn't be filtered out along with classic vm events ? Levgen I don't see the attachment but the info you sent me privately did not come from a classic provider, instead it came from Microsoft.Resources. The classic version of that provider is called "Microsoft.ClassicResources" so I would not expect that particular event to be filtered out. Did you follow the steps I outlined above to reproduce? Did you see the debug in step 4? Bronagh Created attachment 1246669 [details]
deployment events
sorry, I'd prepared file with those events but forgot to attach it. Regarding your question, yes, I followed your steps and saw appropriate debug messages for that vm. I'm closing this ticket since you think these deployment messages shoudn't be filtered. 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://rhn.redhat.com/errata/RHSA-2017-0320.html |