Nodes are not discovered via requisition

Description

Assuming a node XYZ is discovered by default (Node exist in NMS a very long back) at the time there are no requisitions are provisioned in discovery config file.

Now discovery file is created with all requisitions names for all existing subnets.

I’ve deleted a node XYZ in NMS.

When it Discovers the same node XYZ (no change in IP address or DNS name), but this time it discovers again as a default node rather than through requisitions.

Note: New nodes are discovering via requisitions

Environment

PROD

Acceptance / Success Criteria

None

Attachments

1
  • 24 May 2023, 05:15 PM

Activity

Show:

Achut Kantipudi May 24, 2023 at 5:15 PM

- The current version i’m running 31.0.5 Horizon.

 

Step1: Node discovered as a default node from the below mentioned range.

<include-range>
<begin>172.XX.44.XX</begin>
<end>172.XX.44.XX</end>

At this stage no issue.

Step2: I’ve deleted the same node. And updated discovery-configuration.xml file with requisitions name as below.

<include-range retries="1" timeout="2000" foreign-source="XXX-Lab-Servers">
<begin>172.XX.44.XX</begin>
<end>172.XX.44.XX</end>

But again the node discovers as a default node but not with requisitions names

Veena Kannan May 24, 2023 at 1:05 PM

Can you please add details about which version you are using and also add the steps to reproduce the problem? Thanks.

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Due date

Priority

PagerDuty

Created May 2, 2023 at 5:24 PM
Updated June 6, 2023 at 7:39 PM