conformance test should set phc2sys domain to 24
jianzzha opened this issue · comments
Currently conformance test set up this ptp config,
apiVersion: v1
items:
- apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
creationTimestamp: "2022-11-08T15:59:13Z"
generation: 1
name: test-slave1
namespace: openshift-ptp
resourceVersion: "10761981"
uid: b4e88bab-dd92-4d3e-ae7e-972a8387930e
spec:
profile:
- interface: ens1f0
name: test-slave1
phc2sysOpts: -a -r
ptp4lConf: |-
[global]
tx_timestamp_timeout 50
ptp_dst_mac 01:1B:19:00:00:00
p2p_dst_mac 01:80:C2:00:00:0E
domainNumber 24
logging_level 7
ptp4lOpts: -2 -s
ptpSchedulingPolicy: SCHED_OTHER
ptpSchedulingPriority: 65
recommend:
- match:
- nodeLabel: ptp/clock-under-test
priority: 5
profile: test-slave1
kind: List
metadata:
resourceVersion: ""
Because `domainNumber 24` is used in ptp4lConf, phc2sysOpts should be updated to `phc2sysOpts: -a -r -n 24`
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
.
Mark the issue as fresh by commenting/remove-lifecycle rotten
.
Exclude this issue from closing again by commenting/lifecycle frozen
./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.