Bug 488340 - system-config-cluster save/show wrong lvm configure.
system-config-cluster save/show wrong lvm configure.
Product: Fedora
Classification: Fedora
Component: system-config-cluster (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ryan McCabe
Fedora Extras Quality Assurance
Depends On: 488336
  Show dependency treegraph
Reported: 2009-03-03 14:08 EST by ritz
Modified: 2010-06-28 07:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 488336
Last Closed: 2010-06-28 07:23:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ritz 2009-03-03 14:08:23 EST
+++ This bug was initially created as a clone of Bug #488336 +++

Created an attachment (id=333912)

Description of problem:
When configuring LVM resource with tool system-config-cluster, if we save the configure into /etc/cluster/cluster.conf. We can found lv_name and lvm name in the /etc/cluster/cluster.conf are wrong.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. launch system-config-cluster and create a LVM resource.
LVM resource name is "lvmtest"
Volume group name is "vgora1"
Logical volume name is "lvora1"
2. Save config to /etc/cluster/cluster.conf

Actual results:
This is what we get from cluter.conf
<lvm lv_name="lvmtest" name="lvora1" vg_name="vgora1"/>

Expected results:
we should get cluter.conf file with this:
<lvm lv_name="lvora1" name="lvmtest" vg_name="vgora1"/>

Additional info:

From resource.py

    self.lv_name = self.rc_xml.get_widget('entry32')
    self.lv_vgname = self.rc_xml.get_widget('entry33')
    self.lv_lvname = self.rc_xml.get_widget('entry34')

from resource.glade

Name -> entry34
Volume Group name -> entry33
Logical Volume Name -> entry32

patch attached, courtesy - Jerry Jiang

This needs to fixed with upstream code.
Comment 1 Bug Zapper 2009-06-09 07:49:47 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 2 Bug Zapper 2010-04-27 09:05:47 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2010-06-28 07:23:30 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.