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.

Bug 1100263

Summary: RHEL 7 RC 3.1 install crashes with "no enough arguments for format string" exception
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kolman <mkolman>
Component: python-blivetAssignee: Martin Kolman <mkolman>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: jstodola
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-blivet-0.18.35-1 Doc Type: Bug Fix
Doc Text:
Cause: An error message was using an incorrect string formatting syntax. Consequence: Blivet crashed when trying to report the error message. Fix: The string formatting syntax was corrected. Result: Blivet no longer crashes when reporting the error message.
Story Points: ---
Clone Of:
: 1100269 (view as bug list) Environment:
Last Closed: 2015-03-05 14:07:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1100269    
Attachments:
Description Flags
traceback
none
anaconda log
none
storage log
none
program log none

Description Martin Kolman 2014-05-22 11:46:06 UTC
Created attachment 898351 [details]
traceback

Description of problem:
During an autoparted VM install on a 16 GB virtio disk, the installation tracebacks due to a string formatting error in Blivet.

BTW, there actually seem to be two problems - tre traceback occurs when blivets tries to report a vg creation error. This bug is for the string formatting problem and I'll fill a separate bug for the vg sizing problem.


Version-Release number of selected component (if applicable):
Anaconda & Blivet versions from RHEL 7 RC 3.1

Comment 1 Martin Kolman 2014-05-22 11:46:37 UTC
Created attachment 898353 [details]
anaconda log

Comment 2 Martin Kolman 2014-05-22 11:47:10 UTC
Created attachment 898354 [details]
storage log

Comment 3 Martin Kolman 2014-05-22 11:47:48 UTC
Created attachment 898355 [details]
program log

Comment 7 Jan Stodola 2015-01-13 11:44:58 UTC
Fixed in python-blivet-0.61.0.20-1.el7:

log.error("Failed to get free space for the %s VG: %s", self.vg.name, lvmerr)

Moving to VERIFIED.

Comment 9 errata-xmlrpc 2015-03-05 14:07:02 UTC
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-2015-0313.html