f5-appsvcs-extension icon indicating copy to clipboard operation
f5-appsvcs-extension copied to clipboard

shareNodes notworking for FQDN nodes

Open DahlPatric opened this issue 1 year ago • 1 comments

Environment

  • Application Services Version: 3.46.2
  • BIG-IP Version: 14.1

Summary

Issues when trying to use SharedNodes with FQDN nodes what we believe causing the issue.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Submit the following declaration:
{
    "servicePort": 1525,
    "hostname": "flosvl1014.flo.volvocars.net",
    "addressDiscovery": "fqdn",
    "shareNodes": true
}
  1. Observe the following error response:
"errors": [
        "/Tenant/app-MyApp/app-MyPool/members: pool member /Tenant/app-MyApp/app-MyPool/members/0 fqdn hostname server1.locl conflicts with bigip fqdn node /app-MyPool/server1.locl"
    ],

When we using ShardNodes in declaration we does not either see them be installed in /Common/Shared.

Expected Behavior

Actual Behavior

SharedNodes seam not be installed in ShardNodes folder initially. When installing another declaration with same nodes causing error,

DahlPatric avatar Jan 31 '24 10:01 DahlPatric

Please reach out to us at [email protected] in order for us to prioritize. Thanks.

sunitharonan avatar Feb 21 '24 18:02 sunitharonan

Also having this issue. Reached out to your email.

We get a little different error but the result appears triggered from the similar input.

"errors": [ "/tenant/app/p_vip-443/members: pool member /tenant/app/p_vip-443/members/0 static address 10.0.0.10 conflicts with an ephemeral address to which app.fqdn.oursite.com resolves for bigip FQDN node /Common/_auto_10.0.0.10" ],

MicSkr avatar Apr 15 '24 20:04 MicSkr

Jira issue is AUTOTOOL-4178. I only have one customer name for this Jira. Would help prioritize if i had both. Please reach out at the email address above. Spring planning is tomorrow.

mdditt2000 avatar Apr 16 '24 17:04 mdditt2000

Reached out. Thanks @mdditt2000 !

MicSkr avatar Apr 16 '24 20:04 MicSkr

Is there an update on when this will be released? This is holding back FQDN configurations and making it difficult for operators to perceive devices by FQDN.

MicSkr avatar May 08 '24 14:05 MicSkr

Reached out to customer through email to gather more information. Closing as we are unable to reproduce.

sunitharonan avatar Jun 26 '24 17:06 sunitharonan