pyjuju

peer interface relationship data not propagating

Bug #806184 reported by Juan L. Negron
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Invalid
Undecided
Unassigned

Bug Description

In peer relationships, the data set using relation-set is not being propagated. As a result, the corresponding relation-get information on the peer is returning empty.

I have also tried using relation-get <unit_name> and relation-get <remote_name>. I am only able to get information about my own unit but nothing on the peer(s).

-Juan

Revision history for this message
Juan L. Negron (negronjl) wrote :

I am using debug-hooks and I just noticed that the relationship-changed hook is called twice. which in my case fixed the issue as the second time it had all of the data.

I am going to investigate this a bit further by adding several more units.

-Juan

Revision history for this message
Juan L. Negron (negronjl) wrote :

closing the bug as it is invalid. the hooks just get called several times depending on the number of extra nodes. This does seem like a limitation. As the number of nodes increases, the number of times that the hooks get called increases as well.

Changed in ensemble:
status: New → Invalid
Revision history for this message
Kapil Thangavelu (hazmat) wrote : Re: [Bug 806184] Re: peer interface relationship data not propagating

Excerpts from Juan L. Negron's message of Tue Jul 05 20:53:29 UTC 2011:
> closing the bug as it is invalid. the hooks just get called several
> times depending on the number of extra nodes. This does seem like a
> limitation. As the number of nodes increases, the number of times that
> the hooks get called increases as well.
>
> ** Changed in: ensemble
> Status: New => Invalid
>

We ended up changing the system a few weeks ago to always invoke relation-changed after relation-joined. Its effectively a spurious execution
of relation-changed, but we had found that most of the extant formulas at that time where getting it wrong, by waiting till relation-changed
had been invoked to check for data, instead of checking in both relation-changed and relation-joined for the remote side data (as the remote
side could possibly have already joined and added its data by the time relation-joined was invoked on the original unit). hth. kapil

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.