Bug 1472325
Summary: | [RFE] clean up STAGE_BOOT priorities/schedule | ||
---|---|---|---|
Product: | [oVirt] otopi | Reporter: | Yedidyah Bar David <didi> |
Component: | Core | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | master | CC: | bugs, didi, lsvaty, oourfali |
Target Milestone: | ovirt-4.2.0 | Keywords: | CodeChange, FutureFeature |
Target Release: | 1.7.2 | Flags: | sbonazzo:
ovirt-4.2?
jbelka: testing_plan_complete- rule-engine: planning_ack? sbonazzo: devel_ack+ lsvaty: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-20 11:02:04 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: | 1169099 |
Description
Yedidyah Bar David
2017-07-18 13:14:47 UTC
Could you please provide verification steps if there are any? Thank you. (In reply to Jiri Belka from comment #1) > Could you please provide verification steps if there are any? Thank you. Comment 0 is very detailed, and IIRC the patches actually do exactly what I wrote there. Most of the stuff there would probably have been noticed already by basic sanity tests done elsewhere - e.g. log file in /tmp and not in /var, stuff like that. Feel free to review it and decide to do a few specific tests if you think they make sense. Other than that, can't think of anything specific, setting CodeChange. ok, otopi-1.7.2-0.0.master.20170919135351.gitf2bfc9c.el7.centos.noarch ovirt-host-deploy-1.7.0-0.0.master.20170912090102.git1eeb5a2.el7.centos.noarch deploying hosts works ok This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |