| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Composite of effective changes from:
I36f8fc8130ed914e8a2c2a11c9679144d931ad73
Ia6dac22081c92bbccc803f233dd53740f6b48abb
I820bba1347954b659fd7469ed542f98ef0a6eaf0
Ultimately to reduce CI VM count in terms of memory
utilization and disk utilization in order to get
consumption into a safe range to prevent
out of memory and out of disk space conditions.
Changed l-c job to run on ubuntu bionic to avoid failures
Change-Id: Ic9f3ddc9cd48c5a973996a4136d9832f869c0b08
|
|
|
|
|
|
|
|
|
|
|
| |
This change updates the ansible deploy driver to exclude
devices with "sr", "loop", and "mem" which can appear in the
devices list for consideration as the root device.
This change effectively causes them to be ignored.
Change-Id: I72a422553ee992d313b83df091af2c9deb8393b5
(cherry picked from commit 0071d28460f1c0baa449d8f7920f4cf36e876bdc)
|
|
|
|
|
|
|
|
|
| |
The configuration for json_rpc contains the option use_ssl but its value
was not respected by the json_rpc client. Therefore the client tried to
connect to HTTPS endpoints using HTTP.
Change-Id: I4336d71f57bcfbde90fa7b62a5435a7f9d0a73d3
(cherry picked from commit feae197c5ad02fa0898a30d4ffaaba8a21d4f884)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Our ramdisks have swelled, and are taking anywhere from 500-700
seconds to even reach the point where IPA is starting up.
This means, that a 900 second build timeout is cutting it close
and intermittent performance degredation in CI means that a job
may fail simply because it is colliding with the timeout.
One example I deconstruted today where a 900 second timout was
in effect:
* 08:21:41 Tempest job startes
* 08:21:46 Nova instance requested
* Compute service requests ironic to do the thing.
* Ironic downloads IPA and stages it - ~20-30 seconds
* VM boots and loads ipxe ~30 seconds.
* 08:23:22 - ipxe downloads kernel/ramdisk (time should be completion
unless apache has changed logging behavior for requests.)
* 08:26:28 - Kernel at 120 second marker and done decompressing
the ramdisk.
* ~08:34:30 - Kernel itself hit the six hundred second runtime
marker and hasn't even started IPA.
* 08:35:02 - Ironic declars the deploy failed due to wait timeout.
([conductor]deploy_callback_timeout hit at 700 seconds.)
* 08:35:32 - Nova fails the build saying it can't be scheduled.
(Note, I started adding times to figure out the window to myself, so
they are incomplete above.)
The time we can account for in the job is about 14 minutes or 840
seconds. As such, our existing defaults are just not enough to handle
the ramdisk size AND variance in cloud performance.
Change-Id: I4f9db300e792980059c401fce4c37a68c438d7c0
(cherry picked from commit 9169085db781e2a27bdfc36e45a4d0feeb9bca53)
|
|/
|
|
|
|
|
| |
Yet another place where we missed it :(
Change-Id: Iaa56e5965806e975ed0f97f2d6a0d15e13351c22
(cherry picked from commit 0b0ab9eb167c5a568141518e5a4698fc7f601d2b)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as victoria branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I5e4865f21ee368c801b2fbdb0fac6054ea8b7654
|
|
|
|
| |
Change-Id: I9225461c5088d1b77c5d18a3647300712d8c86f5
|
|\ |
|
| |
| |
| |
| |
| |
| | |
And remove corresponding filter from tox.ini
Change-Id: I226e329151e0f71e793ade432c80a1628aa21511
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
Convert mock.ANY to actual call when possible.
Change-Id: I35e2eb04306cf7538f715e077e0ad12f5bebea49
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I did something stupid when started driving forth the split of ipxe
from the pxe interface: I didn't think about the need to actually
separate bootloaders. In part, because the use case was a mixed
Power8/Power9 and x86 cluster. Mainly because the Power hardware
does not honor or care about the bootfile name provided over DHCP.
The firmware knows how to read the PXELINUX boot file format
and the machines are able to boot from there.
Where this all goes sideways is when:
* Enabled boot interfaces are set to ipxe,pxe
* No default boot interface is set
* Node is created without a default for x86 hardware.
* Node uses ipxe boot_interface, and creates files under /httpboot
* bootfile transmitted via DHCP is pxelinux.0.
Fun right?
The simple workaround for the power user is to just define the iPXE
loader, or maybe use UEFI. But that is neither here nor there, this
is still a bug and a possible use case is GRUB2 via PXE and iPXE.
Not that would really work via ipxe, but hopefully people get the
idea.
The solution kind of seems clear, duplicate configuration and
fallback if not defined.
Story: #2007003
Task: #40282
Change-Id: I4419254c23095929e52a0fda11789f2f5167dc6b
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This corrects the variable examined to determine if falling back from
Redfish boot source override enabled continuous to once should be
performed. The value of the variable 'enabled', instead of
'desired_enabled', should be used.
Story: 2007733
Task: 40273
Change-Id: I26bf32c7f824e8e5ca7018d491e0bc9dc96a8671
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | | |
Change-Id: I8f6abbad1612311887f16a88c0fd3b7de8659e27
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
They are not guaranteed to be stable and actually change in the next
version of jsonpatch.
Change-Id: If6fc0b99c4cb8654ba0b50400d51a184518a32cb
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | | |
Change-Id: I27fee44d8c89ed5dff310822af2a103e5e6e682c
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
This is to fix the missing print format issue in log message.
Change-Id: I183133da0b12352a72206f048e5f4167a25e1f5c
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's usually enough to provide only command[command_error][details],
but this patch also places some safeguards for abnormal responses.
Also fixes error detection for TypeError (we don't have faultstatus
when we have command_error).
Change-Id: I9b2d0eb417211b01ae36c461b19652ff9db7d658
Story: #2002063
Task: #19716
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Follow up of https://review.opendev.org/735127
The assertItemsEqual method has been removed in Python 3.3 [1] but
it was kept alive by unittest2, imported by testtools.
To prevent mayhem and despair caused by testtools removing unittest2
from its requirements in the near future, we switch to assertCountEqual.
For an unknown reason, some asserts were forgotten, this patch fixes
them all, for real, I swear.
[1] https://bugs.python.org/issue17866
Change-Id: I51a31204ddef83fe36a55631f1a81bff346d176b
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Following up on comments from https://review.opendev.org/716889
Change-Id: I805a65478f469b1b4e25c1bf2397f034f61d6ec7
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
Change-Id: Ibac5d07b988438719bf414f314cbc610562e7599
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We should use mock from unittest instead of 3rd party mock.
Since we don't have mock in requirements anymore this could cause
issues like in [1].
[1] https://zuul.opendev.org/t/openstack/build/ff068dc014be42aabde51f95c8c9828e
Change-Id: I5a60aa820b60fd29d8ebbd851f3fd215458bab96
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
Change-Id: Iad6cb02ee4f17b7c5987719b3a0603df210c840d
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The error message is not properly tranlated as desired, raw string
is returned when reached maximum number of traits.
Change-Id: I62b2d32c545b6ad6487aead98c8fab212ed5e83f
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The ovmf pacakge in bionic doesn't really work in our CI.
As a workaround we use the old package from xenial, but we can't keep
using it also in Ubuntu Focal.
This patch aims to convert the uefi jobs to use Ubuntu Focal as
base operating system and use the native ovmf package.
Story: 2007785
Task: 40025
Change-Id: I653e5da2672b14eae88c6cab923b8617432f1dc1
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
PERC H740P controllers supports RAID mode and Enhanced HBA mode.
When the controller is in Enhanced HBA, it creates single disk
RAID0 virtual disks of NON-RAID physical disks.
Hence the user's request for VD creation with supported RAID
fails due to no available physical disk.
This patch checks the Perc H740P controllers whether it supports
enhanced HBA mode and if controllers are found in enhanced HBA
mode it converts back to RAID mode.
Change-Id: I9d295135e6059a47cb541ae1218b11c3d56f85e1
Story: 2007711
Task: 39844
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: If692795221661414b2990f8131433678402dd45b
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
And remove the corresponding H210 filter.
Change-Id: Ib53af28596dc1392f68c956efc6d8750de611c13
|
|\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | | |
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Change-Id: I14ac07661b8741684dcf77ced9e782b57c947d79
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Recent changes to the CI made the python binary magically disappear
in Ubuntu Focal based nodes.
Since we currently support only python3 and the python3 binary is
(hopefully) always present in all current distributions, let's
switch the last python binary call to python3.
Change-Id: Ifeca377c3ada3372406ff90bd72d81f90e9bde21
|
|\ \ \ \ \ \ |
|