This new alarm is raised when the controllers deploy
state is out of sync during the deployment.
Test Plan:
PASS: alarm raised when the deploy state is out of sync
PASS: alarm cleared when the deploy state is in sync
Task: 49732
Story: 2010676
Change-Id: Ibdcc54f02c9e156b2b78313b527cd273a62425f1
Signed-off-by: junfeng-li <junfeng.li@windriver.com>
Configuring new alarm 850.002 which will be used when K8s
periodic audit happens and any of the endpoint health check
fails.
Test Plan:
PASS: Performed tox test locally and packages were built
successfully
PASS: Verify that k8s orchestrated upgrade will get blocked,
if it is tried while alarm is set. And k8s orchestrated
upgrade will complete, if it is tried when alarm is
cleared.
Story: 2011037
Task: 49535
Change-Id: I335179ea98ef63d7c35c89d82328a52ab2391f5c
Signed-off-by: rakshith mr <rakshith.mr@windriver.com>
Currently there is no alarm for node taint.
This new alarm 900.701 describes the attributes
of the node taint.
Test Plan:
PASSED: Verified the details of the alarm
using fm alarm-list.
Partial-Bug: 2046273
Change-Id: I929ddb45b75f1e4b097b84919f703d458d8fa39e
Signed-off-by: Vanathi.Selvaraju <vanathi.selvaraju@windriver.com>
The alarm 280.004 is added and will be raised when the system peer
connection failure has been detected, and will be cleared when the
system peer connection has been restored.
The alarm 280.005 is added and will be raised when the a subcloud peer
group is being managed by a remote system with a lower priority, and
will be cleared when the subclouds belonging to the subcloud peer group
have been migrated back to current system.
Test Plan:
PASS - Verify successful tox test and package build
Story: 2010852
Task: 48492
Change-Id: I3068676933c0446a88bd4290277456cd0962f941
Signed-off-by: Zhang Rong(Jon) <rong.zhang@windriver.com>
The 250.002 alarm has been deprecated long time ago.
This change deletes it from the alarm list.
Test plan:
PASS:
* Build fm-doc and fm-api packages.
* Check that all parsing checks were run and package was built
successfully.
Depends-on: https://review.opendev.org/c/starlingx/distcloud/+/886001
Closes-bug: 2024010
Signed-off-by: Agustin Carranza <agustin.carranza@windriver.com>
Change-Id: I0180bd5addc1feae6e3e45edd24c1f50d6622e2c
System config update alarms are 900.6xx series
The new alarms are originated by a new type of vim strategy
orchestrating configuration update.
The new alarms are similar in numbering and wording as the
kube upgrade auto apply 900.4xx series alarms and logs.
System config update in-progress alarm is 900.010.
System config update aborted alarm is 900.011.
Story: 2010719
Task: 47947
Change-Id: Ieb6e68adf359ac7b0489d15bb33cb4b4a9f3ef3f
Signed-off-by: Yuxing Jiang <Yuxing.Jiang@windriver.com>
This commit is intended to update the 260.002 alarm. As the 'severity'
is set to 'minor', it is desired to classify it as
non-management-affecting by adjusting its Management_Affecting_Severity
value to 'none'.
Test Plan:
PASS: Build and install Debian package.
Story: 2010719
Task: 47938
Change-Id: Ie228191ebdda5f2651dab1309b929ae06bc1f7f6
Signed-off-by: Enzo Candotti <enzo.candotti@windriver.com>
This commit adds a new alarm id and definition for resources
that has INSYNC=False.
The alarm will be raised when a resource is not
synchronized during a process of update. It will be cleared when
the resource is synchronized again.
Test Plan:
- Verify successful tox test and package build
- Verify the alarm can be raised using FmClientCli
Story: 2010719
Task: 47910
Change-Id: I24a976ed4beaa8248df25fd97eeee27f5754b969
Signed-off-by: Enzo Candotti <enzo.candotti@windriver.com>
Some documentation generating scripts were introduced in order to avoid
manual intervention every time an alarm/log is changed/added/removed.
Those scripts required a way to know where the alarm/log belongs to.
For that requirement, the field Context was introduced in previous
commits. During that development, it was taken the current
classification at that time in the docs as source of truth, but it was
outdated.
This commits modifies the values that were detected as wrong/outdated.
The scripts also require the value 'none' in the Context field for when
an alarm/log should not be included in the documentation but still be
defined in the events.yaml file. So the Context value is updated for
that case too.
Context incorrectly tagged as openstack and changed to starlingx:
* 900.006
Context incorrectly tagged as starlingx and changed to openstack:
* 100.105
* 100.112
* 100.113
* 300.001
* 300.002
Closes-bug: 2012981
Test plan
PASS: Since the Context field does not have impact in functionality,
build and install fm-doc package successfully.
Check the file in the filesystem contains this change.
PASS: Trigger random alarms and check FM functionality.
Signed-off-by: Agustin Carranza <agustin.carranza@windriver.com>
Change-Id: I16f858bbb712349f08b2ceca33152e365b0ed733
Currently, there is no alarm for Restore in progress.
Because of this, the system is shown as healthy,
before restore has been completed.
This new alarm will prevent the system from being healthy
until restore has properly been completed.
TEST PLAN
PASS: On any available system, the following commands can
be triggered at anytime:
* Run "system restore-start" to trigger alarm
* Run "system restore-complete" to clear alarm
Story: 2010117
Task: 47689
Signed-off-by: Joshua Kraitberg <joshua.kraitberg@windriver.com>
Change-Id: I292b5c8083c08b68ac757fe5a650989178eb819f
Added in the following tox targets for fm-rest-api:
- bandit
- flake8 / pep8
- pylint (suppressing most of the codes)
All the tox targets run on python3
The test-requirements.txt have been updated
The StarlingX Debian upper constraints are utilized.
The spec-lint (rpm) job is removed from Zuul.
Zuul runs pylint for sub directories
Bandit exclusions are updated.
Included a change to a .py file to trigger
the bandit zuul job.
Test Plan (for fm-rest-api)
PASS: tox -e bandit
PASS: tox -e coverage
PASS: tox -e flake8
PASS: tox -e pylint
Story: 2010531
Task: 47575
Signed-off-by: Al Bailey <al.bailey@windriver.com>
Change-Id: I7ecaf1c90495b283c26e02e3b481bfe4c77c3939
Removal of stale alarm 270.001(Host compute service failure)
is raised by the vim. This might be an old reference to nova.
It’s likely not in use since stx.
Test Plan:
PASS: Verify with a load without the changes (removal of alarm)
and the event log in platform.log shows an entry for 270.001 alarm.
PASS: Verify with a load with changes of alarm removal and
the event log in platform.log does not show an entry for 270.001 alarm.
Closes-Bug: 2004744
Change-Id: I47a9f5cede2cfade4a16c63a2dc1bcfd563e88cf
Signed-off-by: Vanathi.Selvaraju <vanathi.selvaraju@windriver.com>
The Debian packaging has been changed to reflect all the
git commits under the directory, and not just the commits
to the metadata folder.
This ensures that any new code submissions under those
directories will increment the versions.
All packages have a higher version than before the change.
Test Plan:
PASS: build-pkgs -c -p fm-api
PASS: build-pkgs -c -p fm-common
PASS: build-pkgs -c -p fm-doc
PASS: build-pkgs -c -p fm-mgr
PASS: build-pkgs -c -p fm-rest-api
PASS: build-pkgs -c -p python-fmclient
Story: 2010550
Task: 47226
Signed-off-by: Al Bailey <al.bailey@windriver.com>
Change-Id: I65e881ba96512d2eaba25c44332d5ae82efea502
The events.yaml file contains every alarm and log used by platform and
openstack. There is no way to know which one relates to one or
the other.
In order to know that, it is required an additional field as part of
each record to differential between platform and openstack.
Story: 2010143
Task: 46723
Test plan
PASS: Build the fm-api and fm-doc packages.
Install fm-api first and then fm-doc.
No errors are found during build and installation process.
Signed-off-by: Agustin Carranza <agustin.carranza@windriver.com>
Change-Id: I8598afc77d27d107c4f9a108dd46b2ebc79b30a1
This change reorganizes the source directories of the stx-fm-rest-api
container to be reused by both CentOS and Debian Dockerfiles in order
to build the images having the corresponding OS-specic base.
As part of this, the fm-api, fm-rest-api, fm-common and
python-fmclient packages have been ported in order to generate deb
files that contain .whl.
Test plan:
PASS: Build debian iso and perform fresh install. Verify fm commands are
working as expected.
PASS: Build python3 wheels tarball on Debian. Verify fm, fm_api, fm_core
and fmclient .whl files are added.
PASS: Build Debian-based container and push it to a public registry.
Apply openstack application and update the fm-rest-api url to pull
this new image. Verify that:
- pods are up and running with the new image/tag specified.
- the container is running on Debian.
- from inside the container, fm querys are working as expected.
Story: 2009831
Task: 46634
Depends-On: https://review.opendev.org/c/starlingx/config/+/862498
Signed-off-by: Enzo Candotti <enzo.candotti@windriver.com>
Change-Id: I2b35139f8775141e39f97a5a6037c5de2b4d5d76
This commit adds a new alarm id and definition for subcloud backup.
The alarm will be raised and cleared by dcmanager upon subcloud backup
failure and successful retry respectively.
Test Plan:
- Verify successful tox test and package build
Story: 2010116
Task: 46162
Change-Id: I9a34a827e484bb691c8ce0da63e1a7d26735c289
Signed-off-by: Tee Ngo <Tee.Ngo@windriver.com>
Constant FM_ALARM_ID_STORAGE_CEPH_FREE_SPACE was being used only in
legacy code by ceph-manager. The code was updated to remove this
unused constant and its respective alarm.
Test plan:
PASS: Verify that no alarms are raised related to quotas.
PASS: Confirm that no quota messages are present in the logs.
Depends-On: https://review.opendev.org/c/starlingx/config/+/827545
Depends-On: https://review.opendev.org/c/starlingx/utilities/+/820933
Closes-Bug: 1959894
Signed-off-by: Daian Cardoso Sganderlla <Daian.CardosoSganderlla@windriver.com>
Change-Id: I606d0e6dca102189a26c8cd4d587a1e772e610f0
Add debian packaging infrastructure for fm-api
so we can create a debian packaging for it.
Also update the directory layout due to limitations
of the STX tool. Update the centos build information
to reflect the new layout.
Story: 2009101
Task: 43091
Signed-off-by: Charles Short <charles.short@windriver.com>
Change-Id: I5c9784647581f31384d7475f596663adc0d26498
Added two new alarm IDs and details for expiring-soon and
expired certificates.
Story: 2008946
Task: 43049
Signed-off-by: Sabeel Ansari <Sabeel.Ansari@windriver.com>
Change-Id: I61cb835c38473cef61238de8cf4a21361e123da4
This change added a KUBE_ROOTCA_UPDATE_ABORTED alarm for kube
rootca update abort.
Story: 2008675
Task: 43068
Signed-off-by: Andy Ning <andy.ning@windriver.com>
Change-Id: I3096b57697d2c6a548f5c54002705cb1797ae97b
Kubernetes rootca update alarms are 900.5xx series
The new alarms are similar in numbering and wording as the
kube upgrade auto apply 900.4xx series alarms and logs.
Story: 2008675
Task: 42708
Signed-off-by: albailey <Al.Bailey@windriver.com>
Change-Id: I480dc50b1cb03d12cc7ba2a7eefad80d3c56e32c
Update in events.yaml adding alarm 900.008 indicating that procedure
for k8s root CA update started in the system.
Task: 2008675
Story: 42411
Signed-off-by: Joao Soubihe <JoaoPaulo.Soubihe@windriver.com>
Change-Id: I0df40423735e1c76acc21206b96c9e8b7924121f
This commit adds a new alarm type for Kubernetes Persistent Volume
patching errors during AIO-SX to AIO-DX migration.
Partial-Bug: 1927224
Signed-off-by: Pedro Henrique Linhares <PedroHenriqueLinhares.Silva@windriver.com>
Change-Id: I8f64280394999249c829372d1748a9c26fdb9ced
Adds a Kubernetes Upgrade in progress alarm 900.007
Kubernetes auto apply upgrade alarms are 900.4xx series
The new alarms are similar in numbering and wording as the
firmware update auto apply 900.3xx series alarms and logs.
Change-Id: Iab4fb79aebfd999ebc5f17c109371caf566671be
Story: 2008137
Task: 41427
Signed-off-by: albailey <Al.Bailey@windriver.com>
flake8 2.5.5 fails on ubuntu-focal zuul machines running python3.8
with the following error:
AttributeError: 'FlakesChecker' object has no attribute 'CONSTANT'
Fixed:
E117 over-indented
E741 ambiguous variable name
F841 local variable is assigned to but never used
Per-Line-Suppressed:
E402 module level import not at top of file
F632 use ==/!= to compare constant literals
Global Suppress:
W504 line break after binary operator
W605 invalid escape sequence
The suppressed errors can be fixed by later submissions.
Change-Id: I2df3ece427f0c84ce16c1a82f4d9f0c9a5a6982b
Partial-Bug: 1895054
Signed-off-by: albailey <Al.Bailey@windriver.com>
This update changed the TIS_PATCH_VER to use the PKG_GITREVCOUNT
variable to auto-version the packages.
Adds an upper constraint to fm-rest-api to pass zuul.
Story: 2006740
Task: 39842
Change-Id: I4a180f1395ff9764ecc9d617a514e265db670b9c
Signed-off-by: Teresa Ho <teresa.ho@windriver.com>
Added a system alarm to indicate device image update
is in progress.
Story: 2006740
Task: 39842
Change-Id: I7aa8d3bba353256b1ecad65e2d5e488f2aeecbae
Signed-off-by: Teresa Ho <teresa.ho@windriver.com>
1. Raise alarm if image-conversion is not added on both controllers
2. Raise alarm if the size of the filesystem is not the same on both controllers
Change-Id: I803b313cfee372fd5d025efbba74c1ae34b9e248
Partial-bug: 1819688
Signed-off-by: Elena Taivan <elena.taivan@windriver.com>
Adding a pylint tox target which only suppresses
the error codes that are currently failing.
This will prevent any of the passing checks from being
broken by future submissions.
The currently suppressed codes can be fixed by subsequent
commits.
Adds a zuul pylint target to invoke the new tox target.
Unified the install_command in tox.ini to ensure
the upper constraints are used.
Change-Id: Id2fb8cbb7ce63f844a06403410d461c601822ad6
Story: 2007082
Task: 39020
Signed-off-by: albailey <Al.Bailey@windriver.com>
Some of the fault components rely on having all the dependencies
installed in the StarlingX ISO so having missing dependencies listed
in the spec files is not an issue. However, when we take those compo-
nents and run them in a non StarlingX installation these problems
started to arise.
This patch is the result of the analysis of all imports and a manual
execution of the fault components in opensuse. This is a summary of
the findings:
- fm-api: This component imports `fm_core` which is provided by
`fm-common` but not listed in the dependencies. Same
case for `six` module.
- fm-mgr: `fmManager` links to `libfmcommon` but is not listed in the
requirements. Also, it expects to find the `/etc/fm/events.yaml`
file which is provided by `fm-doc`.
- fm-rest-api: A set of imports that are missing. This component also
depends on other StarlingX compoments.
- python-fmclient: Missing python imports.
Story: 2006684
Task: 36971
Change-Id: I6719ab8a8d9a35d105be1c6f7dac57b855da543e
Signed-off-by: Erich Cordoba <erich.cordoba.malibran@intel.com>
After changing the version to 1.0.0, the install target of the
specfile wasn't changed. This change updates the version to meet
the new convention.
Story: 2006508
Task: 36863
Change-Id: I142800fb2ea41c31aa63bcf440ee055b10164401
Signed-off-by: Erich Cordoba <erich.cordoba.malibran@intel.com>
These files are part of OBS infrastructure and shouldn't be part of
this repository.
Story: 2006508
Task: 36862
Change-Id: I8cc056a49a888352d8dbb03b2a55e86549e6a45a
Signed-off-by: Erich Cordoba <erich.cordoba.malibran@intel.com>
All opensuse version are being standardize with the same format,
this requires that all components will change from 1.0 to 1.0.0.
Story: 2006508
Task: 36811
Change-Id: I301759895e4ed816633daa6595d5f60f2f1d59c7
Signed-off-by: Erich Cordoba <erich.cordoba.malibran@intel.com>
The rpmlintrc files helps to configure the behavior of the rpm linter
executed by the opensuse build system. This patch adds the rpmlintrc
files that were defined in the opensuse build system.
Story: 2006508
Task: 36799
Change-Id: If75264e809bb78bbcff1dd474b1a5fc1819ac193
Signed-off-by: Erich Cordoba <erich.cordoba.malibran@intel.com>
In the opensuse build system (OBS) the `_service` files are being
standardized to generate tarballs with gz compression. The fault's
specfiles were created before this decision, therefore an update
in the extension is required.
Story: 2006508
Task: 36670
Change-Id: I96cb185a9a0e089e4f8e184e8fdeaa709f77915e
Signed-off-by: Erich Cordoba <erich.cordoba.malibran@intel.com>
fm-api already has a LICENSE file no need to copy LICENSE in
Closes-Bug: 1842667
Change-Id: I9232e73f4d38394ad7d427431d0b766c1fbadf5b
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This commit adds a "pending application reapply" alarm to fm,
which will be raised when there has been a configuration change
to nodes that affects the helm overrides.
Partial-Bug: 1837750
Change-Id: Iec5852a798eee51dacbc5ea5016e4c20d85b668c
Signed-off-by: Tyler Smith <tyler.smith@windriver.com>
The newly introduced fault constants will be used to raise and
clear application related alarms.
Closes-Bug: 1833323
Change-Id: I992ab7a788cfab8d52d2e6a498519c591148f588
Signed-off-by: Tee Ngo <Tee.Ngo@windriver.com>
This commit adds the RPM specfile that supports openSUSE, these
include the _service file which creates the tarball, the changes
files and specfile itself.
These are all built via the OpenBuildService (OBS) and can be
found here:
https://build.opensuse.org/project/show/Cloud:StarlingX:2.0
Change-Id: I676aae8cb9554eab2740232fd0dd77e0ed876506
Signed-off-by: Saul Wold <sgw@linux.intel.com>
The Maintainer was change from a proper name to the StarlingX
project as it can be confusing the responsibilities of the person.
Change-Id: I32faf658388bc38e248362c71589f70f8f22ad4d
Story:2004792
Signed-off-by: Marcela Rosales <marcela.a.rosales.jimenez@intel.com>
Zuul