App metadata behavior is mispelled in metadata.yaml for ptp-notification-app

Bug #2065428 reported by Cole Walker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
In Progress
Undecided
Cole Walker

Bug Description

Brief Description
During review of app metadata.yaml it was observed that ptp-notification has 'behaviour' in metadata.yaml instead of 'behavior'. This is probably causing the app to omit 'platform_managed_app' option.

    stx-ptp-notification-helm/stx-ptp-notification-helm/files/metadata.yaml

Severity
Minor

Steps to Reproduce
list="ptp-notification-armada-app/stx-ptp-notification-helm/stx-ptp-notification-helm/files/metadata.yaml"

grep "behaviour" $list

Expected Behavior
The spelling should be the expected spelling as presented in config repo files:

    sysinv/sysinv/sysinv/sysinv/common/constants.py
    sysinv/sysinv/sysinv/sysinv/common/app_metadata.py

Actual Behavior
Mispelled.

Reproducibility
100%

System Configuration
Any, n/a

Load info (eg: 2022-03-10_20-00-07)
Master branch, latest

Last Pass
N/A, day one

Timestamp/Logs
N/A

Alarms
N/A

Test Activity
Reviewing platform app metadata

Workaround
N/A

Cole Walker (cwalops)
Changed in starlingx:
assignee: nobody → Cole Walker (cwalops)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ptp-notification-armada-app (master)
Changed in starlingx:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.