[GBP-197] Tenant is put to CONF DS before EPs are registered -> No Tenant in OPER Created: 06/Oct/15  Updated: 07/Oct/15  Resolved: 07/Oct/15

Status: Resolved
Project: groupbasedpolicy
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Tomas Cechvala Assignee: Vladimir Lavor
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 4421
Priority: Normal

 Description   

Policy (tenant) is missing in OPERATIONAL DS if you

  • PUT tenant into CONF DS
  • register endpoints

It works when you change the order of actions

  • register endpoints
  • PUT tenant into CONF DS

Tenant
http://pastebin.com/77hVAyFC

Endpoints (data for endpoint registration)
http://pastebin.com/7SUk6sJe

Happened in stable/lithium.

 Comments   
Comment by Vladimir Lavor [ 07/Oct/15 ]

In tenant rest is action-instance "chain1" which requires service function chain with name "SFCGBP". This chain must be present in DS, otherwise tenant will not pass validation. It does not matter in which order is tenant/EP put to DS.

So there are two options:

Comment by Vladimir Lavor [ 07/Oct/15 ]

(In reply to Vladimir Lavor from comment #1)
> In tenant rest is action-instance "chain1" which requires service function
> chain with name "SFCGBP". This chain must be present in DS, otherwise tenant
> will not pass validation. It does not matter in which order is tenant/EP put
> to DS.
>
> So there are two options:

1. Put SFC to DS before the tenant will be validated (validation runs when tenant and EP are present in DS)
2. Remove action-instance "chain1" from tenant (and keep "allow1")

Generated at Wed Feb 07 20:01:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.