Bug 884359

Summary: VG name not substituted in "Volume Group name %s is already in use. Not saving changes."
Product: [Fedora] Fedora Reporter: Steve Tyler <stephent98>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-18.36.1-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-15 03:16:53 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:
Attachments:
Description Flags
screenshot showing "Volume Group name %s is already in use. Not saving changes." none

Description Steve Tyler 2012-12-06 03:43:07 UTC
Created attachment 658513 [details]
screenshot showing "Volume Group name %s is already in use. Not saving changes."

Description of problem:
The volume group name is not substituted in this info message:
"Volume Group name %s is already in use. Not saving changes."

See attached screenshot.

Version-Release number of selected component (if applicable):
anaconda-18.36-1.fc18

How reproducible:
Always.

Steps to Reproduce:
Create a new volume group with name "fedora".
  
Actual results:
Info message contains "%s".

Expected results:
Info message contains volume group name.

Additional info:
The fix for the following bug exposes this bug:
Bug 883632 - TypeError: set_info() takes exactly 2 arguments (3 given)

Comment 1 Fedora Update System 2012-12-08 01:45:57 UTC
anaconda-18.37-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.37-1.fc18

Comment 2 Fedora Update System 2012-12-08 22:13:32 UTC
Package anaconda-18.37-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.37-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19991/anaconda-18.37-1.fc18
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-12-12 20:40:44 UTC
Package anaconda-18.37.2-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.37.2-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19991/anaconda-18.37.1-1.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-12-15 03:16:54 UTC
anaconda-18.37.2-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.