Forum Discussion
Are there any known issues with REST API on F5 v17.1.0.3
Hi Team,
We are planning to upgrade to 17.1.0.3 in our environment (we are using only VCMP and LTM) can some one please advice if there are known issues with this code for REST API.
Does 17.1.3 cause any issues with REST API that we should be worried.
Thanks in Advance.
If you're looking for specifics for your device/s you should create a QKVIEW and then upload that to iHealth on the F5 support site and see what it comes back with for you configuration, device, and code version variation.
https://account.f5.com/ihealth2&ved=2ahUKEwiahtKwlaKHAxW2JEQIHTu2AYQQFnoECBYQAQ&usg=AOvVaw1b8yBs5uptzGh1DsdsW5Py
- Aswin_mkCumulonimbus
Hello,
For understanding the bugs and fixes in the Version please go through below link
Also please raise a vendor request before your upgrade and provide the qkview file to verify. F5 will be there as a support if anything occur during upgrade. But before upgrade go through the above document.(If you have a test environment, please upgrade the same first). Hope you have the answer for your query now
- vasu_arkasaliNimbostratus
Hello There,
Just follow up and more specific question on this issue.
We have upgraded our LB from 15.1.8 to 17.1.0.1 and also on 16.1.4.3 on both versions we are seeing below behavior.We have REST API and python scripting to enable/disable pool members which is not working after the upgrade. Below are few logs which we captured duringour debug on device in question. need to know why does it shows exception and also fix needed here.Note : the REST API and Python script works fine on 15.1.8 without any issues.============================================================================Audit logsnotice mcpd[6457]: 01070417:5: AUDIT - client iControlSOAP, user X.X.X - transaction #39540-3 - object 0 - create { pool_member { pool_member_pool_name "/Common/POOL_AA" pool_member_node_name "/Common/172.X.X.31" pool_member_port 80 } } [Status=Command OK]notice mcpd[6457]: 01070417:5: AUDIT - client iControlSOAP, user X.X.X - transaction #39615-3 - object 0 - modify { node_address { node_address_name "/Common/172.X.X.31" node_address_new_session_enable 2 } } [Status=Command OK]notice mcpd[6457]: 01070417:5: AUDIT - client iControlSOAP, user X.X.X - transaction #39616-3 - object 0 - modify { node_address { node_address_name "/Common/172.X.X.31" node_address_monitor_state 3 } } [Status=Command OK]LTM logsDEBUG:bigsuds:Executing iControl method: LocalLB.Pool.set_member_session_enabled_state((['/Common/POOL_AA'], [[{'port': 80, 'address': '/Common/172.X.X.31'}]], [['STATE_DISABLED']]), {})Traceback (most recent call last):File "/usr/bin/poolmembers_disable.py", line 292, in <module>main()File "/usr/bin/poolmembers_disable.py", line 244, in mainpool_members(args)File "/usr/bin/poolmembers_disable.py", line 287, in pool_membersfor pool in pools_dict.keys(): globals()[args.command](pools_dict[pool], *params)File "/usr/bin/poolmembers_disable.py", line 76, in offlinepool.member(m).disable()File "/usr/lib/python2.7/XX-packages/pyFOLDER/F5/__init__.py", line 828, in disableself._set_member_session_enabled_state("STATE_DISABLED")File "/usr/lib/python2.7/XX-packages/pyFOLDER/F5/__init__.py", line 843, in _set_member_session_enabled_state(self, self.pool, err))Any help on this greatly appreciated.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com