starlingx/platform-armada-app
Code Issues Proposed changes

Fix zuul failures during setup

Browse Source 
The ubuntu-jammy nodeset gets selected by default
and is causing problems during setup.

Collecting cffi>=1.1
Failed to build cffi

ubuntu-focal seem to work fine.
Will specify the nodeset to be focal to resolve this.

Need to update a file under python-k8sapp-platform in
order to trigger the failing zuul jobs.

Partial-Bug: 1994843

Signed-off-by: Al Bailey <al.bailey@windriver.com>
Change-Id: I18235473c04fbcf97dd5df676f054f34cd18b8b8
This commit is contained in:
Al Bailey 2022-10-28 13:55:30 +00:00
parent 48859ba190
commit baccc223f0
2 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.zuul.yaml
View File

@ -60,6 +60,7 @@
parent: tox
description: |
Run flake8 test for k8sapp_platform
nodeset: ubuntu-focal
files:
- python-k8sapp-platform/*
vars:
@ -88,6 +89,7 @@
parent: tox
description: |
Run bandit test for k8sapp_platform
nodeset: ubuntu-focal
files:
- python-k8sapp-platform/*
vars:

1
python-k8sapp-platform/k8sapp_platform/tox.ini
View File

@ -41,6 +41,7 @@ setenv = VIRTUAL_ENV={envdir}
TOX_WORK_DIR={toxworkdir}
PYLINTHOME={toxworkdir}
# for debian the path to cgcs-patch is incorrect
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
-e{[tox]stxdir}/config/sysinv/sysinv/sysinv