Bug 1335436
| Summary: | Rebase ovirt-node-ng (including kickstart) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Fabian Deutsch <fdeutsch> |
| Component: | ovirt-node-ng | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED ERRATA | QA Contact: | Ying Cui <ycui> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.0.0 | CC: | dfediuck, gklein, rbarry, ycui |
| Target Milestone: | ovirt-4.0.1 | Keywords: | Rebase |
| Target Release: | 4.0.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-ng-4.0.0-0.20160707.0.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-23 21:12:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Fabian Deutsch
2016-05-12 08:44:27 UTC
Ryan, could you provide the git rebase command you used for this bug, without the command, I don't know how to 100% verify this bug to make sure we get all upstream fixes into downstream. The command was "git checkout ovirt-4.0 && git rebase master" I don't actually know that there's a good way to verify this from a QE perspective, unfortunately. (In reply to Ryan Barry from comment #2) > The command was "git checkout ovirt-4.0 && git rebase master" > > I don't actually know that there's a good way to verify this from a QE > perspective, unfortunately. Yes, to verify this bug, here need to provide which commit we need to rebase or detail bugs list. OR strict check all commits one by one. So I would like to let devel do bug verification to make sure all expected commits are rebased correct. 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/RHBA-2016-1688.html |