Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
We ran into various pvcreate failures and error messages were not clear. It would be nice if pvcreate gives more clear error messages when different kind of errors happen.
Comment 3Jonathan Earl Brassow
2016-06-30 16:17:15 UTC
(In reply to Vivek Goyal from comment #1)
> We ran into various pvcreate failures and error messages were not clear. It
> would be nice if pvcreate gives more clear error messages when different
> kind of errors happen.
Vivek, the old bug is a lot to plow through. Can you give a couple examples of what type of output you would like to see in response to certain errors?
(In reply to Jonathan Earl Brassow from comment #3)
> (In reply to Vivek Goyal from comment #1)
> > We ran into various pvcreate failures and error messages were not clear. It
> > would be nice if pvcreate gives more clear error messages when different
> > kind of errors happen.
>
> Vivek, the old bug is a lot to plow through. Can you give a couple examples
> of what type of output you would like to see in response to certain errors?
Jon,
pvcreate was giving us following message.
"Device /dev/xvdb1 not found (or ignored by filtering).".
This is very generic and it would be nice if error was more specific.
For example, first breakdown could happen, whether device node is not present or whether it was ignored by filtering.
And even for filtering, it would be nice to know what does that mean. On what specific attribute, a device was filtered out.