Opened 7 months ago

Closed 7 months ago

Last modified 5 months ago

#13593 closed Patch - Bug Fix (fixed)

Python: Use 'MasterServerName' instead of 'MasterServerIP'

Reported by: rcrdnalor Owned by: rcrdnalor
Priority: minor Milestone: 31.1
Component: Bindings - Python Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Ticket #13024 : Networking Improvements introduced new settings for 'MasterServerName', 'BackendServerAddr' and 'BackendServerPort' and deprecates '!MasterServerIP' and 'MasterServerPort'.

'BackendServerAddr' can be an IPv4 or IPv6 in the classical "dot/colon" notation, or is provided in it's canonical form.

From settings table:

| value             | data                | hostname |
+-------------------+---------------------+----------+
| BackendServerAddr | 192.168.1.100       | myserver |
| BackendServerPort | 6543                | myserver |
| MasterServerName  | myserver            | NULL     |
+-------------------+---------------------+----------+

or

| value             | data                | hostname |
+-------------------+---------------------+----------+
| BackendServerAddr | server.example.com  | myserver |
| BackendServerPort | 6543                | myserver |
| MasterServerName  | myserver            | NULL     |
+-------------------+---------------------+----------+

Thanks to Ross Boylan for pointing this out in the user mailing list and to and to Peter Bennett for additional explanation.

The workaround until this ticket gets fixed is to use only IP addresses in the ".dot" notation and take care, that the "!MasterServerIP" is identical to the "BackendServerAddr".

Attached patch uses these new settings for the Python Bindings instead of the deprecated ones.

Attachments (2)

Python_Replace_deprecated_settings.patch (4.1 KB) - added by rcrdnalor 7 months ago.
Replace deprecated settings 'MasterServerIP' and 'MasterServerPort?'
0001-BackendServerAddr-and-MasterServerName-replaced-Mast.patch (10.0 KB) - added by rcrdnalor 7 months ago.
Updated patch for replacing deprecated setting 'MasterServerIP'

Download all attachments as: .zip

Change History (7)

Changed 7 months ago by rcrdnalor

Replace deprecated settings 'MasterServerIP' and 'MasterServerPort?'

Changed 7 months ago by rcrdnalor

Updated patch for replacing deprecated setting 'MasterServerIP'

comment:1 Changed 7 months ago by Roland Ernst <rcrernst@…>

Resolution: fixed
Status: assignedclosed

In 105faee393/mythtv:

BackendServerAddr? and MasterServerName? replaced MasterServerIP

in V30, according ticket #13024.

Replace any occurrences of the deprecated settings and allow
'BackendServerAddr?(MasterServerName?)' to be an alias for the
host-ip as well.

Fixes #13593

comment:2 Changed 5 months ago by Stuart Auchterlonie

Roland,

does this need to be cherry-picked back to fixes/31?

Regards Stuart

comment:3 Changed 5 months ago by Stuart Auchterlonie

Milestone: needs_triage32.0

comment:4 Changed 5 months ago by rcrdnalor

Milestone: 32.031.1

comment:5 Changed 5 months ago by Roland Ernst <rcrernst@…>

In c8e779649/mythtv:

BackendServerAddr? and MasterServerName? replaced MasterServerIP

in V30, according ticket #13024.

Replace any occurrences of the deprecated settings and allow
'BackendServerAddr?(MasterServerName?)' to be an alias for the
host-ip as well.

Fixes #13593

(cherry picked from commit 105faee393b682e79a336d7ee893f82f8c10a896)

Note: See TracTickets for help on using tickets.