Bug 1746394
| Summary: | Additional hosts not getting added in RHV-M | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | bipin <bshetty> | |
| Component: | rhhi | Assignee: | Sahina Bose <sabose> | |
| Status: | CLOSED ERRATA | QA Contact: | bipin <bshetty> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhhiv-1.6 | CC: | godas, rhs-bugs, sasundar | |
| Target Milestone: | --- | Keywords: | Regression, ZStream | |
| Target Release: | RHHI-V 1.6.z Async Update | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | cockpit-ovirt-dashboard-0.13.8 | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1746395 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-03 12:24:16 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: | 1746395 | |||
| Bug Blocks: | ||||
|
Description
bipin
2019-08-28 10:59:25 UTC
The fix is already available in the build - cockpit-ovirt-dashboard-0.13.8 And also the dependent oVirt bug is ON_QA Verified the bug using cockpit-ovirt-dashboard-0.13.8-1.el7ev.noarch The additional hosts are now automatically added to the RHV-M. So closing the bug. Logs: ===== 2019-09-06 10:44:03,952+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [5da7dd55] EVENT_ID: USER_ADD_VDS(42), Host rhsqa-grafton8-nic2.lab.eng.blr.redhat.com was added by admin@internal-authz. 2019-09-06 10:44:03,957+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2) [68a805c8] EVENT_ID: USER_ADD_VDS(42), Host rhsqa-grafton9-nic2.lab.eng.blr.redhat.com was added by admin@internal-authz. 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:2963 |