Bug 1979282 - timemaster service fails to start on a single domain with multiple interfaces
Summary: timemaster service fails to start on a single domain with multiple interfaces
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 16.2 (Train on RHEL 8.4)
Assignee: Haresh Khandelwal
QA Contact: Joe H. Rahme
URL:
Whiteboard:
: 1979278 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-05 13:13 UTC by Haresh Khandelwal
Modified: 2022-03-23 22:11 UTC (History)
2 users (show)

Fixed In Version: tripleo-ansible-0.8.1-2.20220112214927.5e744eb.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-23 22:10:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 799993 0 None MERGED replacing "," with " " to avoid timemaster to consider it as a single interface 2021-07-12 07:49:20 UTC
Red Hat Issue Tracker NFV-2196 0 None None None 2022-02-04 06:51:43 UTC
Red Hat Issue Tracker OSP-5828 0 None None None 2021-11-15 13:08:59 UTC
Red Hat Product Errata RHBA-2022:1001 0 None None None 2022-03-23 22:11:15 UTC

Description Haresh Khandelwal 2021-07-05 13:13:56 UTC
Description of problem:
Current jinja template (timemaster.conf.j2) is having below.

{% for domain, nic_list in ptp_dict.items() %}
[ptp_domain {{ domain }}]
interfaces {% for nic in nic_list %}
{{ nic }}{% if not loop.last %},{% endif %}
{% endfor %}

{% endfor %}

Due to this, when below is passed via THT,
PTPInterfaces: '0:eno1,0:eno2'

results into

[ptp_domain 0]
interfaces eno1,eno2

timemaster service fails with this message.

[root@computedpdk-0 heat-admin]# systemctl status timemaster
● timemaster.service - Synchronize system clock to NTP and PTP time sources
   Loaded: loaded (/usr/lib/systemd/system/timemaster.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2021-07-05 12:12:05 UTC; 4s ago
  Process: 169838 ExecStart=/usr/sbin/timemaster -f /etc/timemaster.conf (code=exited, status=1/FAILURE)
 Main PID: 169838 (code=exited, status=1/FAILURE)

Jul 05 12:12:05 computedpdk-0 systemd[1]: timemaster.service: Succeeded.
Jul 05 12:12:05 computedpdk-0 systemd[1]: Stopped Synchronize system clock to NTP and PTP time sources.
Jul 05 12:12:05 computedpdk-0 systemd[1]: Started Synchronize system clock to NTP and PTP time sources.
Jul 05 12:12:05 computedpdk-0 timemaster[169838]: timemaster[532409.195]: ioctl SIOCETHTOOL failed: No such device
Jul 05 12:12:05 computedpdk-0 timemaster[169838]: timemaster[532409.195]: failed to get time stamping info for eno1,eno2 <<<<<<<<<<<<<<<<<<<<
Jul 05 12:12:05 computedpdk-0 systemd[1]: timemaster.service: Main process exited, code=exited, status=1/FAILURE
Jul 05 12:12:05 computedpdk-0 systemd[1]: timemaster.service: Failed with result 'exit-code'.

Version-Release number of selected component (if applicable):
16.2

How reproducible:
Always

Steps to Reproduce:
- Perform deployment with above mentioned PTPInterface value.

Expected results:
Ideally, we should have

[ptp_domain 0]
interfaces eno1 eno2 <<<<No ","

To start timemaster service successfully.

Actual result:
Failed timemaster service on the node.

We need to replace "," with "" in order to generate working template.

Additional info:

Comment 3 Karrar Fida 2021-09-16 12:07:51 UTC
*** Bug 1979278 has been marked as a duplicate of this bug. ***

Comment 14 errata-xmlrpc 2022-03-23 22:10:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.2), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1001


Note You need to log in before you can comment on or make changes to this bug.