Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug reappeared - DO always enables dhcp on mgmt interface after post declaration #379

Open
xingyuz24 opened this issue Jun 18, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@xingyuz24
Copy link

Environment
Declarative Onboarding Version: 1.43.0.5
BIG-IP Version: 14.1.5.6
Summary

I am using DO v1.43.0.5, I encountered the same issue as it was described in #261 that supposed to be fixed in v1.25.0.

I have mgmt configured static on BIG-IP, when I apply DO declaration without any changes of mgmt state, I always receive dhcp enabled on mgmt interface of BIG-IP.

Steps To Reproduce
Steps to reproduce the behavior:

Submit the following declaration:
{
"schemaVersion": "1.0.0",
"class": "Device",
"async": true,
"Common": {
"class": "Tenant",
"hostname": "bigip.example.com",
"test_vlan2": {
"class": "VLAN",
"tag": 100,
"interfaces": [
{
"name": "1.1",
"tagged": true
}
]
}
}
}
Check that vllan was updated with dhcp state:
[root@bigip:Active:Standalone] config # ip a l mgmt
6: mgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 00:50:56:b8:37:ed brd ff:ff:ff:ff:ff:ff
inet 10.144.109.146/22 brd 10.144.111.255 scope global mgmt
valid_lft forever preferred_lft forever
inet6 2003::77/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feb8:37ed/64 scope link
valid_lft forever preferred_lft forever
[root@bigip:Active:Standalone] config # getdb dhclient.mgmt
enable
[root@bigip:Active:Standalone] config # tmsh list net vlan
net vlan test_vlan2 {
fwd-mode l3
if-index 304
interfaces {
1.1 {
tagged
}
}
tag 103
}
[root@bigip:Active:Standalone] config #

@xingyuz24 xingyuz24 added bug Something isn't working untriaged Issue needs to be reviewed for validity labels Jun 18, 2024
@mdditt2000
Copy link

Sounds like a regression. Jira task AUTOTOOL-4419. Added to next sprint beginning mid August. Expect a pre-release in August. Will follow up with Daniel once pre-release is available.

@mdditt2000 mdditt2000 removed the untriaged Issue needs to be reviewed for validity label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants