Bug 1527335
Summary: | wrong self.logger calls: self.log.error should be self.logger.error | ||
---|---|---|---|
Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Ido Rosenzwig <irosenzw> |
Component: | General | Assignee: | Ido Rosenzwig <irosenzw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.2.0 | CC: | bugs, irosenzw, stirabos |
Target Milestone: | ovirt-4.2.2 | Keywords: | Triaged |
Target Release: | 2.2.3 | Flags: | rule-engine:
ovirt-4.2+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-hosted-engine-setup-2.2.3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-29 10:53:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1458709 |
Description
Ido Rosenzwig
2017-12-19 09:22:15 UTC
Please provide more detailed reproduction steps. hosted-engine --deploy --noansible with default answers (In reply to Ido Rosenzwig from comment #2) > hosted-engine --deploy --noansible with default answers "typo mistakes: Some files contain self.log.error instead of self.logger.error" After deployment, what I should look for? Where I should check the logs or what? No. just check that deployment finish successfully. self.log.error is a typo mistake that may fail the deployment, it should be self.logger.error for it to work properly. Nothing specific to check beside successful deployment Deployment is working fine on NFS, Gluster and FC. ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST 2018 x86_64 x86_64 x86_64 GNU/Linux This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |