- **status**: review --> fixed
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Thu Nov 10, 2016 02:32 AM UTC
**Owner:** Minh Hon Chau
Multiple SUs
Push into 5.0 branch
changeset: 8302:6557805ec604
branch: opensaf-5.0.x
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** review
**Milestone:** 5.0.2
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Thu Nov 10, 2016
- **Milestone**: 5.1.1 --> 5.0.2
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** review
**Milestone:** 5.0.2
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Thu Nov 10, 2016 01:07 AM UTC
**Owner:** Minh Hon Chau
Multiple
Pushed for 5.1 and default:
changeset: 8301:a25d5d50b01a
changeset: 8300:773643625dc6
Could it happen with 5.0?
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** review
**Milestone:** 5.1.1
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
- **status**: assigned --> review
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** review
**Milestone:** 5.1.1
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Mon Oct 24, 2016 02:31 AM UTC
**Owner:** Minh Hon Chau
Multiple
Thanks Praveen, I will publish the patch with (1)
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** assigned
**Milestone:** 5.1.1
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Fri Oct 21, 2016 10:59 AM UTC
**Owner:** Minh Hon
adjust.patch
Attachments:
-
[adjust.patch](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/76ef399e/abe0/attachment/adjust.patch)
(10.0 kB; application/octet-stream)
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** assigned
Hi Minh,
I have gone through the patch. SU mapping must be same before headless state
and after headless state. I was trying a totally different approach but could
not finish it (attach is a crude patch adjust.patch). I think we are only left
with your other suggestion i.e approach (1) only.
Hi Minh,
I am going through the patch,
Thanks,
Praveen
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** assigned
**Milestone:** 5.1.1
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Mon Oct 17, 2016 12:19 AM UTC
**Owner:**
Hi Praveen,
After headless, config_get_su() has already did a wrong mapping, and
su_add_to_model() also updated this wrong mapping to IMM.
After calling config_get_su after headless, the only right mapping only exists
in the sync information where amfd retrieves from avd_susi_recreate(). But
Hi Minh,
Function avd_susi_recreate() will be called after reading configuration from
IMM. In this function, the second for loop over SUSI_list should overwrite the
node name even if it has been set wrong while creating SU during
config_get_su() from IMM.
Also in the same function there are
Hi Praveen
I have tried (2), I thought it should work, but it doesn't
The reason is after avd_su_config_get(), saAmfSUHostedByNode of all SUs now
have been updated to IMM incorrectly. So reading saAmfSUHostedByNode in
headless sync phase will still give incorrect mapping.
Any ideas?
Thanks,
Attached file is amfd trace that shows how a duplicated node mapped to SUs
Before headless, the node<->su map as below:
SU1: PL3, SU2: PL4, SU3: PL5, SU4: SC1, SU5: SC2
After headless, the nodes read from IMM and initialization phase was reverted
in order, thus the node <-> su map was changed:
- **status**: unassigned --> assigned
- **assigned_to**: Minh Hon Chau
---
** [tickets:#2112] amfd: multiple SUs incorrectly assigned to single node**
**Status:** assigned
**Milestone:** 5.1.1
**Created:** Tue Oct 11, 2016 11:56 PM UTC by Gary Lee
**Last Updated:** Tue Oct 11, 2016 11:58 PM
- Description has changed:
Diff:
--- old
+++ new
@@ -16,6 +16,6 @@
...
saAmfSUHostedByNodeSA_NAME_T
safAmfNode=PL-4,safAmfCluster=myAmfCluster (42)
-SU4 is indeed assigned to PL-4, but SU2 was assigned to one of the SCs and is
not assigned to PL-4.
- Description has changed:
Diff:
--- old
+++ new
@@ -17,3 +17,5 @@
saAmfSUHostedByNodeSA_NAME_T
safAmfNode=PL-4,safAmfCluster=myAmfCluster (42)
SU4 is indeed assigned to PL-4, but SU2 was assigned to one of the SCs and is
not assigned to PL-4.
+
16 matches
Mail list logo
