Age | Commit message (Collapse) | Author | Files | Lines |
|
While at it, limit functest & yardstick to master and
stable/euphrates, trying to work around missing job references
in Danube scenarios on ZTE PODs.
Change-Id: I89de0c3b3c914e1ad735980a995e5cae625238be
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
On rare occasions, Fuel/Armband verify jobs can get into a deadlock
on nodes with exactly 2 executors.
Add a build blocker to prevent such scenarios.
Change-Id: Ia00d88df0dd033264eaeb66e27188c62514b74d8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Fixes some final yamllint issues introduced by recent patchsets in apex
and armband.
JIRA: RELENG-254
Change-Id: I26b45d737f06c215413e29c92031d14e23967506
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Armband uses different 'pod' naming/labeling, so instead of Fuel's
'baremetal' reference, we have 'armband-baremetal', leading to
unresolved job references for the recently added log collection.
Fix that by adding a new 'deploy-type' variable, which corresponds
to either 'baremetal' or 'virtual', aligning with Fuel naming.
While at it, slightly refactor our pod definitions to use the new var.
Change-Id: Ie84c40a5c208072da2e4766233a844f2670d4f87
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Debugging test suite failures is often hard without physical access
to the POD, and even then the environment might be automatically
redeployed before successfully debugging the problem.
So, collect all contents of </var/log> from all cluster nodes
(including the Salt Master node) after all test suites have been
executed as part of the CI job.
Change-Id: Ie5e2526c74f4ed21be9c76c6f6101eb3f434be36
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Fuel and Armband Euphrates jobs are always marked as failed, even
when at least one sub-job passes, due to missing Dovetail job for
that respective stream.
Change-Id: Ibcdde75d70111e82f8498114deabaf7808cc6d74
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Id47f61c950e1cc036e32e8efe2e2b55193e7c49e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: RELENG-254
Change-Id: I1c658e0af40d2973301b33f760d7fd420e80f253
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Functest Alpine not supported yet for aarch64 architecture.
Task for Armband project but until support could be done, the
traditionnal docker shall be used for armband tests
usage of alpine leads to errors [1]
[1]: https://build.opnfv.org/ci/view/functest/job/functest-fuel-armband-baremetal-daily-master/214/console
Change-Id: I48e05a0c7cd97989784fd97348bd331425c4877e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
JIRA: FUEL-279
Change-Id: Ie87ecaee17d6bb29776c3056274c59c1264762de
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Using include-raw-escape inside macros adds extra curly braces, which
breaks bash scripts.
JIRA: FUEL-287
Change-Id: If1e5f528e76aff78d2c9b99530b72070b6731f75
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-278
Change-Id: I9f5496d02097c2a6ae1db73b8a5df20b75ce728d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Enable virtual deploy phase for verify multijob for both projects.
Since fuel-defaults already define SSH_KEY param, drop it from
individual jobs.
Fuel:
- drop merge jobs, which used to perform virtual deploys based on
ISO created during verify job;
- cleanup fuel-download-artifact (rm support for merge/verify);
Armband:
- while at it, remove "opnfv-build-enea-defaults", preparing for
arm-build2's retirement.
JIRA: FUEL-278
JIRA: FUEL-287
Change-Id: I354d72d88187e41070f44c723ccc651a0bb9b021
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Cleanup commit c0ba4a5 removed the timed triggers for Armband
baremetal scenarios, bring them back.
Change-Id: I8b8d8d366ecf95594e26f30c1392b26692504021
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Armband no longer requires any artifact before starting a deployment.
Fuel (master and stable/E) no longer requires the artifact either,
but since there are some stable/danube deploy jobs on ZTE PODs, we
will hold off removing <fuel-download-artifact.sh> for a while.
Deprecation warning: fuel-download-artifact.sh will be removed later.
JIRA: ARMBAND-295
Change-Id: I3b26733a1120306879eff83b9fac3390b3f5c7b8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, cleanup obsolete parameters specific to build ops.
JIRA: FUEL-277
JIRA: FUEL-278
Change-Id: Id45dfe6855c95c425ac9aa771519d450ba9da3b5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Since armband-deploy.sh is merely a clone of fuel-deploy.sh, which
we recently synced, drop armband-deploy.sh in favor of an universal
fuel-deploy.sh, which will handle deploys for both projects.
Change-Id: I653b4e67d9246951a284671e0cf559394661a1ad
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Run shellcheck on touched files, fix minor warnings.
Prepare for upcoming changes:
- ISO artifact will be obsoleted (later);
- Fuel and Armband should use the same deploy script;
Fuel:
- rename securedlab local copy to lab-config;
Armband:
- drop deploy cache, Danube jobs can work without it, master/next
jobs no longer use it;
- move TMPDIR to $HOME (was in $WORKSPACE), so it's persistent;
Change-Id: I9f8c47f9ca50de3c53c62ca6a08df0cc3a73abd3
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I134feba421d12c4ca428b098aaa2bf52b3dec0ca
|
|
arm-pod3 pod name is changed to arm-pod5
arm-virtual1 pod name is changed to arm-virtual2
Change-Id: I6746fcdd52bbed5b6a61147d0abc5db64876dc97
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
arm-pod4 and arm-pod3 are now both obsolete, so we no longer need
the ad-hoc translation of the slave name in the deploy script.
Change-Id: Ib81d0574507f8c0e8b513cdc00b35124eaaeeb68
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Re-enable baremetal scenario CI for Fuel scenarios:
- os-nosdn-nofeature-ha-baremetal
- os-odl_l3-nofeature-ha-baremetal (to be renamed to just odl later)
- os-nosdn-ovs-ha-baremetal (Fuel only, no Armband equiv yet)
Change-Id: I9b3b929366a3657c45181632ed46936cb15c3cba
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, revert BRIDGE default value to "pxebr" after recent
Fuel rework was merged in [1].
This mechanism will be leveraged by [2].
Partially reverts commit: 68195fd
[1] https://gerrit.opnfv.org/gerrit/#/c/38855/
[2] https://gerrit.opnfv.org/gerrit/#/c/39521/
Change-Id: Ic61487384029a7d16547a5035a1f1b34ecbea8d4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Adds the 'email-jenkins-admins-on-build-failures' publishers for jobs
which have overridden the default list of publishers.
This will provide Jenkins administrators a time-series list of build
failures to assist in debugging issues with the master and agents.
JIRA: RELENG-257
Change-Id: I28f12877562113c9197ed6429ee2a7f3cdbaf346
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
While at it, also rename some leftover "danube" reference for
the armband project.
Change-Id: Icddcf19ca9dfd7880ae2f78ed690988bded25abd
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
MCP does not have a self-test healtcheck suite, similar to old
Fuel, so we dropped the "-H" deploy argument (which used to disable
healtcheck autorun).
Adjust deploy command to reflect this installer change.
While at it, fix leftover "pxebr" default installer parameter,
which we missed in the previous commit where we changed the
default only in releng deploy scripts.
Change-Id: I55e1f5cad17687bdf304fbf04d67366dd32ed42a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Fuel and implicitly Armband switched to a newer format for parsing
the "-B" deploy arg, used to pass bridge(s) information.
For now, we will default to ",,,", which is equivalent to not
setting any default value for any of the 4 possible bridges.
NOTE: Armband overrides this on a per-pod basis, since bridge
information is POD specific in our lab.
Change-Id: I3635b0eb6f8233cf99022a97d5642f2e49197e3b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- rename "danube" to "euphrates";
- disable "euphrates", to be enabled when ready;
Change-Id: Id4932986e19c664b28749d0b6926d825ea632250
Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Old Fuel deploy scripts required the virtual POD name to be
virtual_kvm, which needed to be translated at CI level after
source enviroment specific configuration.
New Fuel deploy scripts no longer need this translation, so
drop it.
Change-Id: I18164e77895bbb03a1ca7798e3c0ba78c34d1c65
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Using sudo triggers a chain of dependencies in our infrastructure,
ranging from issues cleaning up the Jenkins workspace to deploy-time
permission issues.
As it turns out, cleaning all looses ends after that change is not a
trivial task, and the remaining work outweights the benefits of using
sudo in the first place.
The original motivation for using sudo was a superposition of:
- hardcoded check for running as root in Fuel's ci/deploy.sh;
- the ability to install packages on the hosts via apt-get/yum;
- the ability to spawn VMs using virt-manager;
All of the above can be mitigated by imposing a series of restrictions
for the Jenkins slave / jump server workstation and the jenkins user:
- check for sudo rights instead of running as root user;
- explicitly use sudo for package installation and/or system-level
changes;
- add jenkins user to "kvm" and "libvirtd" groups;
So, revert using sudo when calling the deploy script, and limit sudo
actions to package installation in Armband's deploy script.
To compensate running as a regular user, a series of small changes is
required in Armband project itself, together with the appropiate
Jenkins slave user configuration on the machines running this script.
This reverts commit 67d8bac7b2a97531ad465f275747b3dc455d4fe4.
Change-Id: I88df6db1a43b93b7314ceca53d353f9000f15153
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Previous commit adding sudo for ci/deploy.sh call breaks Armband
deploys, since ci/deploy.sh relies on $WORKSPACE env var being set.
Change-Id: I948c8e3c00b430e0c186c0a727e1b7e027d7a089
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
New MCP deploy scripts have a hard requirement on running as root.
Bring back sudo for the `ci/deploy.sh` invocation, aligning with
Fuel@OPNFV.
NOTE: This can be later avoided/reverted if we can guarantee the
"jenkins" user has sudo rights, even without a tty present.
Change-Id: Ibec7b14e9174a7f482609890e5e68912931a8d05
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Sync with changes for Fuel@OPNFV targeting master branch (MCP):
- disable ISO build for master branch;
- turn off upload action & checkout;
- add retrieving OS credentials for MCP;
- disable ISO download for master branch;
Change-Id: I11eacfad7ee1f738119e17c2e63c3d92707f8e1f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Removed the master jobs until mcp is functional on arm.
Rescheduled the danube jobs 8 hours apart.
Change-Id: I90037a76a50d61c76c13cd68fa5926e1a73e88e6
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
JIRA: DOVETAIL-432
1, only run against os-(nosdn-odl_l2)-(nofeature-bgpvpn)-ha scenario
this can reduce the CI/pod time resource
dovetail test cases by now (refstack, ha, ipv6, bgpvpn)
2, this has been tested on compass pod, and works well
Change-Id: I1bcf8165d5fcc93c78b47cbd23e0c07f19b01189
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Arm-pod3-2 is a second jenkins slave for arm-pod3.
This slave is arm while the old jenkins slave is x86.
Fatih requested for this slave to be renamed to arm-pod4
instead of arm-pod3-2, even if it's a slave for an existing pod
JIRA: ARMBAND-252
Change-Id: I5645edd7d774f763e5e72115851c7061bfafd344
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
of "debug""
|
|
JIRA: DOVETAIL-397
now, team decide to use proposed_tests suite instead of debug
Change-Id: Iff8ec0b32a24e51bc2d2536605c9867b94f8921c
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I1ae47f2105744bfea8c8c589f41282d1c4ae2159
Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
|
|
A non-ci pod is made ci-pod for danube release, therefore this patch
modifies the cron jobs to be 4 hours apart instead of 8
This commit should be merged after the lable of the pods are changed
Request: OPNFV Helpdesk #39128
Change-Id: Ic88180d01d9ea03d03b79355cd78891ad612c59b
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
arm-pod3-2 is an aarch64 jenkins slave for the same POD as the existing
x86 jenkins slave arm-pod3. This commit adds jobs so we can deploy the
POD and run functest from the aarch64 jenkins slave.
These jobs are non-ci
JIRA: ARMBAND-241
Change-Id: Ie3b808a641e44649c02f3b75c83d79119217fdfe
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Previously, if an upstream patchset contained a change for a file
listed in 'forbidden-file-paths' the job would not be triggered. This
is not desirable since such a patchset may contain important changes so
we enable the 'disable-strict-forbidden-file-verification' option which
triggers the job unless the patchset only contains changes for the
files listed in 'forbidden-file-paths'.
Note: The diff was generated using the following script:
for i in $(grep -l -r forbidden-file-paths *);do sed -i "s/\(^.*\)forbidden-file-paths/\1disable-strict-forbidden-file-verification: \'true\'\n&/" $i; done
Please double check that the changes look sensible for each team's project.
Change-Id: Ifa86d3a39b36375b2fd52b449e29c8dc757499b4
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
This commit rebalances the nr of runs between master and danube branch
for CI jobs
JIRA: ARMBAND-238
Change-Id: I541ddf3974680096d503829b279cb26ab76577bc
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Here are the projects that were branched:
I will double check against this list that these changes make sense
and that no one is missing as I go forward.
wiki page of participating projects, and their jobs:
https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube
apex - already enabled
armband - done
availability - already enabled
barometer - done
bottlenecks - already enabled
compass4nfv - done
copper - already enabled
daisy - (not participating -- keep jobs disabled?)
doctor - already enabled
domino - already enabled
fds - N/A
fuel - done
functest - already enabled
ipv6 - already enabled
joid - done
kvmfornfv - already enabled
models - already enabled
multisite - done
netready - NOT DONE
opera - NOT DONE
opnfvdocs - done
orchestra - Not participating
onosfw - done
ovsnfv - done
parser - N/A
promise - already enabled
qtip - already enabled
sdnvpn - N/A
snaps - done
securityscanning - N/A
sfc - N/A
storperf - done
ves - already enabled
vswitchperf - already enabled
yardstick - already enabled
Change-Id: I803662faf05c8554cfe7fa5f85da9521f72b03ff
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
The jenkins slave arm-build2 was retagged from opnfv-build-arm
to opnfv-build-enea. This change was made to avoid confusion, as
this slave is an x86 machine building an iso that is used by armband
Change-Id: Iac4e9bf635c128070c32818874626a81a28e6cf7
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|