Bug 1003545
| Summary: | storage node child resources are not created/discovered while storage undeployment-redeployment | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Armine Hovsepyan <ahovsepy> | ||||||
| Component: | Installer | Assignee: | Nobody <nobody> | ||||||
| Status: | NEW --- | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.9 | CC: | hrupp, jshaughn | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 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: | 951619 | ||||||||
| Attachments: |
|
||||||||
Created attachment 792790 [details]
childAlertDefinition-server.log
This series of steps seems somewhat manufactured. It must have triggered some sort of timing issue between uninventory and alert template application for new resources. Unfortunately, we did not log the root cause. I've updated the exception to log the root cause if this occurs again. Given that the issue is not clear, the repro is not 100% and the scenario seems test-oriented, I recommend closing as won't fix. |
Created attachment 792789 [details] storage-node-noChildResouces.png Description of problem: storage node child resources are not created/discovered while storage undeployment-redeployment Version-Release number of selected component (if applicable): a9245fd How reproducible: 1 out of 2 Steps to Reproduce: 1. install and start server, storage and agent on ip1 2. install and start storage and agent on ip2 -> connect agent to server on ip1 3. uninstall storage in ip2 4. reinstall storage in ip2 5. install and start storage and agent on ip3 6. uninstall storage in ip3 7. reinstall storage in ip3 8. run discovery scan for platform on ip3 9. uninstall storage on ip2 10. reinstall storage in ip2 11. run discovery scan for platform on ip2 Actual results: after step11. storage node discovered, exception in server.log on ip1 - cannot create child AlertDefinition for storage node resource under ip2 storage node child resources not present in server-gui Expected results: after step11. storage node discovered, child resources with corresponding AlertDefinitions created and discovered in server-gui, no exceptions in log. Additional info: screenshot and fragment from server.log attached