Alarm “compute-0 is not locked to remote PTP Grand Master“ not clearing . After compute is lock to master

Bug #1856238 reported by Anujeyan Manokeran on 2019-12-12
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Low
David Sullivan

Bug Description

Brief Description
-----------------
       PTP master slave was provisioned controller-1 as master on management and compute-0 and compute-1 as slave on management . Prior to this provisioning there was alarm compute-0 is not locked to remote PTP Grand Master .Which is not clearing after clock was sync for both compute-0 and compute-1 with controller-1. These alarms are generated during the PTP master /slave provisioning.

| | | | | |
| 100. | compute-1 is not locked to remote PTP Grand Master | host=compute-1.ptp=no-lock | major | 2019-12-12T18: |
| 119 | | | | 13:02.330463 |
| | | | | |
| 100. | compute-0 is not locked to remote PTP Grand Master | host=compute-0.ptp=no-lock | major | 2019-12-12T18: |
| 119 | | | | 06:49.024867 |
| | | | |

[sysadmin@controller-1 ~(keystone_admin)]$ sudo /usr/sbin/pmc -u -b 0 'GET TIME_STATUS_NP'
Password:
sending: GET TIME_STATUS_NP
        001e67.fffe.e6c6f6-0 seq 0 RESPONSE MANAGEMENT TIME_STATUS_NP
                master_offset 0
                ingress_time 0
                cumulativeScaledRateOffset +0.000000000
                scaledLastGmPhaseChange 0
                gmTimeBaseIndicator 0
                lastGmPhaseChange 0x0000'0000000000000000.0000
                gmPresent false
                gmIdentity 001e67.fffe.e6c6f6
[sysadmin@controller-1 ~(keystone_admin)]$ ssh compute-0

compute-0:~$ sudo /usr/sbin/pmc -u -b 0 'GET TIME_STATUS_NP'
Password:
sending: GET TIME_STATUS_NP
        90e2ba.fffe.a743d0-0 seq 0 RESPONSE MANAGEMENT TIME_STATUS_NP
                master_offset 0
                ingress_time 1576178473071332290
                cumulativeScaledRateOffset +0.000000000
                scaledLastGmPhaseChange 0
                gmTimeBaseIndicator 0
                lastGmPhaseChange 0x0000'0000000000000000.0000
                gmPresent true
                gmIdentity 001e67.fffe.e6c6f6

Severity
--------
Major

Steps to Reproduce
-----------------

1. System have alarm when PTP was enabled on host level without any interface was provisioned.
2. Provision compute-0 and compute-1 as management interface as slave for PTP
System host-lock compute-0
System host-lock compute-1
system host-if-modify compute-1 6186b26a-c9a8-4b34-8953-c618c53cc515 --ptp-role slave
system host-if-modify compute-0 6186b26a-c9a8-4b34-8953-c618c53cc515 --ptp-role slave
System host-unlock compute-0
System host-unlock compute-1

3. Provision controller-1 management as master interface for ptp
system host-if-modify controller-1 f675fa0e-a28e-49e1-b65d-7822bb0fa44d --ptp-role master
System host-unlock controller-1

4. Verify PTP clock sync using cli sudo /usr/sbin/pmc -u -b 0 'GET TIME_STATUS_NP' for the computes as per description.
5. Verify fm alarm-list not cleared.

Expected Behavior
------------------
No alarms for the hosts that master and slave clocks are sync

Actual Behavior
----------------
As per description alarms are not cleared after master and slave clocks are sync

Reproducibility
---------------
Seen only once tested once.

System Configuration
--------------------
Storage
Lab-name:
WCP-15-22

Branch/Pull Time/Commit
-----------------------
2019-12-09_20-00-00

Last Pass
---------
New feature

Timestamp/Logs
--------------

2019-12-12T18

Test Activity
-------------
Feature Testing

summary: - Alarm not clearing compute-0 is not locked to remote PTP Grand Master
+ Alarm not clearing compute-0 is not locked to remote PTP Grand Master .
+ After compute is lock to master
summary: - Alarm not clearing compute-0 is not locked to remote PTP Grand Master .
- After compute is lock to master
+ Alarm “compute-0 is not locked to remote PTP Grand Master“ not clearing
+ . After compute is lock to master
Ghada Khalil (gkhalil) on 2019-12-12
description: updated
Changed in starlingx:
assignee: nobody → David Sullivan (dsullivanwr)
Ghada Khalil (gkhalil) wrote :

There were some issues with the switch configuration for ptp during this test. Waiting for Jeyan and David to confirm if this alarm was related to that.

Ghada Khalil (gkhalil) on 2019-12-13
tags: added: stx.config
David Sullivan (dsullivanwr) wrote :

The issue seen was due to our switch configuration. The system is working as expected.

Changed in starlingx:
status: New → Invalid
Ghada Khalil (gkhalil) wrote :

Low / not gating - not a software issue

Changed in starlingx:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers