Bug ID 686101: Creating a pool with a new node always assigns the partition of the pool to that node.

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Fixed In:

Opened: Sep 28, 2017
Severity: 3-Major
Related Article:


When creating a node while creating a pool, the partition of the node is set to the one of the pool regardless of what was expected. For example, after running the command below, the new node will be assigned to differentpartition: root@(v13)(Active)(/differentpartition)(tmos)# create ltm pool my_pool2 members add { /Common/ }


The node is displayed in the wrong partition.


Creating a node while creating a pool in a partition different from the node.


Create a node separately and then add it to the pool.

Fix Information

The requested partition is preserved when creating a node while creating a pool.

Behavior Change