FYI to customers suffering the same fate we are: I have Red Hat Support telling me that this problem is not reproducible on their system -- and it must be because we are not running the latest system-config-cluster package (1.0.55-1.0) ... alas, from a customer perspective, that latest package is NOT in our RHEL 4 subscription channel. It is only in the RHEL 5 channel. So, we will wait for another round of responses ... because we won't just arbitrarily apply "other" packages.
It would also be nice if the RHEL 4 CS / GFS channels were kept aligned with RHEL 4 kernel releases, too. Sigh. On Wed, 2009-01-21 at 09:47 -0500, Robert Hurst wrote: > This appears to be new behavior for us, too, ever since applying the > new updates for kernel-smp-2.6.9-78.0.8.EL and the subsequent Cluster > Suite / GFS for it. > > > $ rpm -q system-config-cluster > system-config-cluster-1.0.54-2.0 > > > With this version, regardless, I can no longer ADD / CHANGE working > fence device configurations, from any existing production cluster or > by starting a new one. The management tab also does not display the > NAME of the node any longer -- it places the node STATUS, i.e. "M" or > "X", in that column now. > > Exmaple of EXISTING RUNNING CLUSTER, editing a fence device: > > > [r...@phoenix-1 cluster]# system-config-cluster > Traceback (most recent call last): > File "/usr/share/system-config-cluster/ConfigTabController.py", line 1129, > in on_fd > self.fence_handler.populate_fd_form(agent_type, attrs) > File "/usr/share/system-config-cluster/FenceHandler.py", line 274, in > populate_fd_form > apply(self.fd_populate[agent_type], attrs) > File "/usr/share/system-config-cluster/FenceHandler.py", line 503, in > pop_ilo_fd > self.ilo_ssh.set_active(False) > AttributeError: 'NoneType' object has no attribute 'set_active' > > > Example of NEW CLUSTER, creating a new fence device: > > > [r...@atlantia ~]# system-config-cluster > Traceback (most recent call last): > File "/usr/share/system-config-cluster/ConfigTabController.py", line 1232, > in on_fd_panel_ok > return_list = self.fence_handler.validate_fencedevice(agent_type, None) > File "/usr/share/system-config-cluster/FenceHandler.py", line 713, in > validate_fencedevice > returnlist = apply(self.fd_validate[agent_type], args) > File "/usr/share/system-config-cluster/FenceHandler.py", line 1188, in > val_bladecenter_fd > if self.bc_ssh.get_active == True: > AttributeError: 'NoneType' object has no attribute 'get_active' > > > I also tried the new GUI in luci, did the luci_admin init, but its > service won't startup either -- it fails at: > > > [r...@atlantia ~]# sh -x /var/lib/luci/bin/runzope > + PYTHON=/usr/bin/python > + ZOPE_HOME=/usr/lib64/luci/zope > + INSTANCE_HOME=/var/lib/luci > + CONFIG_FILE=/var/lib/luci/etc/zope.conf > + '[' -d /usr/lib64/luci/zope/lib64/python ']' > + SOFTWARE_HOME=/usr/lib64/luci/zope/lib/python > + PYTHONPATH=/usr/lib64/luci/zope/lib/python > + export PYTHONPATH INSTANCE_HOME SOFTWARE_HOME > + ZOPE_RUN=/usr/lib64/luci/zope/lib/python/Zope2/Startup/run.py > + /bin/grep True /var/lib/luci/.default_password_has_been_reset > + exec /usr/bin/python /usr/lib64/luci/zope/lib/python/Zope2/Startup/run.py > -C /var/lib/luci/etc/zope.conf > Traceback (most recent call last): > File "/usr/lib64/luci/zope/lib/python/Zope2/Startup/run.py", line 56, in ? > File "/usr/lib64/luci/zope/lib/python/Zope2/Startup/run.py", line 21, in run > File > "/var/tmp/conga-0.11.1-5.el4-root-brewbuilder/usr/lib64/luci/zope/lib/python/Zope2/Startup/__init__.py", > line 95, in prepare > File > "/var/tmp/conga-0.11.1-5.el4-root-brewbuilder/usr/lib64/luci/zope/lib/python/Zope2/Startup/__init__.py", > line 272, in makeLockFile > ImportError: No module named misc.lock_file > > > > What gives?? > > > > Robert Hurst, Sr. Caché Administrator > Beth Israel Deaconess Medical Center > 1135 Tremont Street, REN-7 > Boston, Massachusetts 02120-2140 > 617-754-8754 ∙ Fax: 617-754-8730 ∙ Cell: 401-787-3154 > Any technology distinguishable from magic is insufficiently advanced. > > > On Wed, 2009-01-07 at 16:57 -0500, Bob Peterson wrote: > > > ----- "Gary Romo" <[email protected]> wrote: > > | When I opened system-config-cluster today, I got this error; > > | > > | Poorly Formed XML Error > > | > > | A problem was encountered while reading configuration file > > | /etc/cluster/cluster.conf > > | Details or the error appear below. Click the `New` button to create a > > | new configuration file. > > | To continue anyway (Not recommended), click the `Ok` button > > | > > | Relax-NG validity error : Extra element rm in interleave > > | /etc/cluster/cluster.conf:2: element cluster: Relax-NG validity error > > | : Element cluster failed to validate content > > | /etc/cluster/cluster.conf fails to validate > > | > > | Can anyone tell me what this is and how to correct? Thanks! > > | > > | Gary Romo > > > > Hi Gary, > > > > Could it be: > > > > http://sources.redhat.com/cluster/wiki/FAQ/GUI#gui_validityerror > > > > Without seeing your cluster.conf it's hard to tell if it's a "real" error. > > > > Regards, > > > > Bob Peterson > > Red Hat GFS > > > > -- > > Linux-cluster mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/linux-cluster > > > > > > -- > Linux-cluster mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list [email protected] https://www.redhat.com/mailman/listinfo/linux-cluster
