Back to bug 1019328
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Petr Rockai | 2013-10-30 08:29:29 UTC | Status | NEW | ASSIGNED |
| Dean Jansa | 2015-03-06 20:07:46 UTC | QA Contact | mspqa-list | cluster-qe |
| Peter Rajnoha | 2015-10-14 08:16:50 UTC | Assignee | prockai | prajnoha |
| QA Contact | cluster-qe | |||
| Peter Rajnoha | 2015-10-14 08:17:50 UTC | QA Contact | cluster-qe | |
| Peter Rajnoha | 2016-01-22 14:46:24 UTC | Assignee | prajnoha | teigland |
| Peter Rajnoha | 2016-01-26 12:57:29 UTC | Status | ASSIGNED | POST |
| Peter Rajnoha | 2016-01-26 12:58:54 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.140-3.el6 | |||
| Corey Marthaler | 2016-01-26 14:48:28 UTC | CC | cmarthal | |
| errata-xmlrpc | 2016-01-26 14:56:24 UTC | Status | MODIFIED | ON_QA |
| Roman Bednář | 2016-02-26 11:02:29 UTC | Status | ON_QA | VERIFIED |
| CC | rbednar | |||
| David Teigland | 2016-05-04 20:05:07 UTC | Doc Text | Cause: Multiple Volume Groups with the same name were not handled consistently. Consequence: Warnings about the duplicate VGs were not printed when lvmetad was used. The VG name specified by a command would not always translate to the intended VG. Fix: LVM always checks if the VG name specified by a command refers to more than one actual VG. Result: Copied from lvm(8): When VGs with the same name exist, commands operating on all VGs will include all of the VGs with the same name. If the ambiguous VG name is specified on the command line, the command will produce an error. The error states that multiple VGs exist with the specified name. To process one of the VGs specifically, the --select option should be used with the UUID of the intended VG: '--select vg_uuid=<uuid>'. |
|
| errata-xmlrpc | 2016-05-09 17:40:35 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-05-11 01:14:55 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-05-10 21:14:55 UTC |
Back to bug 1019328