Bug 12491
| Summary: | rpm 4.0.32 lock message is wrong | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | R P Herrold <herrold> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | jbj |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-06-21 01:43:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
R P Herrold
2000-06-19 00:28:30 UTC
This is largely a problem with aging and misleading error messages rather than a real problem. The current algorithm, when the desired db3 open fails, is to attempt a db1 open, which of course also fails. A more precise return from the db3 open will permit skipping the futile db1 open attempt. This should be fixed in rpm-4.0-0.56. Please reopen if not. |