[Pacemaker] [GUI][PATCH]An orphan resource was displayed by GUI.
renayama19661014 at ybb.ne.jp
renayama19661014 at ybb.ne.jp
Mon Feb 8 07:35:53 UTC 2010
Hi Yan,
Hi Andrew,
The phenomenon of the problem does not reappear.
I considerably try it, but do not readily reappear.
But, I found the interesting output from the log that the problem happened.
When a problem happened, GUI became the following display.
----------------------------------------------------------
clnUMgroup01
clnUmResource:0
clnUMdummy01:0 on ['cgl60'] ocf::heartbeat:Dummy
clnUMdummy02:0 on ['cgl60'] ocf::heartbeat:Dummy
clnUmResource:1
clnUMdummy01:1 on ['cgl63'] ocf::heartbeat:Dummy
clmUMdummy02:1 on ['cgl63'] ocf::heartbeat:Dummy
clnUmResource:2
clnUMdummy01:2 not running (orphaned)
clnUMdummy02:2 not running (orphaned)
----------------------------------------------------------
Log has the output that pengine changes the name of the resource.
And the name is the resource name that is ORPHANED displayed in GUI.
----------------------------------------------------------
(snip)
Jan 29 15:39:29 cgl60 pengine: [4338]: info: unpack_config: Node scores: 'red' = -INFINITY, 'yellow' =
0, 'green' = 0
Jan 29 15:39:29 cgl60 pengine: [4338]: WARN: unpack_nodes: Blind faith: not fencing unseen nodes
Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl60 is online
Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl63 is online
Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl61 is online
Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy01:0 on cgl61 to
clnUMdummy01:2 (ORPHAN)
Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy02:0 on cgl61 to
clnUMdummy02:2 (ORPHAN)
Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl62 is online
Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy01:0 on cgl62 to
clnUMdummy01:2 (ORPHAN)
Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy02:0 on cgl62 to
clnUMdummy02:2 (ORPHAN)
(snip)
----------------------------------------------------------
Is there any probable cause?
I thought that the problem did not happen with this patch.
I confirm that a problem appears again.
Best Regards,
Hideo Yamauchi.
--- renayama19661014 at ybb.ne.jp wrote:
> Hi Yan,
>
> This problem seems to still occur somehow or other.
> The Orphaned resource of the clone is extremely rarely displayed.
>
> I confirm a condition and report it again.
>
> Best Regards,
> Hideo Yamauchi.
>
>
> --- renayama19661014 at ybb.ne.jp wrote:
>
> > Hi Yan,
> >
> > > Could you please try the attached patch?
> >
> > I confirmed that a problem was solved with your patch.
> > Please reflect your patch in the latest edition.
> >
> > Best Regards,
> > Hideo Yamauchi.
> >
> > --- Yan Gao <ygao at novell.com> wrote:
> >
> > > Hi,
> > >
> > > renayama19661014 at ybb.ne.jp wrote:
> > > > Hi,
> > > >
> > > > An orphan resource was displayed by GUI.
> > > > There is the displayed orphan resource nowhere.
> > > >
> > > > Step1) I start corosync service.
> > > >
> > > > Step2) I spend cib.xml by a cibadmin command.
> > > >
> > > > Step3) I confirm a resource in GUI.
> > > >
> > > > The orphan resource of the clone is displayed by GUI.
> > > > However, there cannot be this orphan resource (clnUmResource:2).
> > > >
> > > > I attached hard copy of GUI and a result of hb_report.
> > > >
> > > > And I attached the patch of the revision again.
> > > > However, this patch may be unfinished.
> > > >
> > > > Please confirm a patch, and please solve this problem.
> > > Thanks for reporting and the patch!
> > > Could you please try the attached patch?
> > >
> > > Regards,
> > > Yan
> > >
> > > --
> > > Yan Gao <ygao at novell.com>
> > > Software Engineer
> > > China Server Team, OPS Engineering, Novell, Inc.
> > > > diff -r 8b56e4d03dc8 mgmt/daemon/mgmt_crm.c
> > > --- a/mgmt/daemon/mgmt_crm.c Tue Jan 12 13:25:09 2010 +0800
> > > +++ b/mgmt/daemon/mgmt_crm.c Tue Jan 19 17:11:53 2010 +0800
> > > @@ -1475,7 +1475,10 @@
> > > ret = strdup(MSG_OK);
> > > while (cur != NULL) {
> > > resource_t* rsc = (resource_t*)cur->data;
> > > - ret = mgmt_msg_append(ret, rsc->id);
> > > + gboolean is_active = rsc->fns->active(rsc, FALSE);
> > > + if (is_not_set(rsc->flags, pe_rsc_orphan) || is_active) {
> > > + ret = mgmt_msg_append(ret, rsc->id);
> > > + }
> > > cur = g_list_next(cur);
> > > }
> > > free_data_set(data_set);
> > > > _______________________________________________
> > > Pacemaker mailing list
> > > Pacemaker at oss.clusterlabs.org
> > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> > >
> >
> >
> > _______________________________________________
> > Pacemaker mailing list
> > Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
More information about the Pacemaker
mailing list