Adds ntpdate to the binary package list for the diskimage-builder
element, and added ntpclient to the tinycore package list and added
a small shim to wrap ntpclient as ntpdate is not a native tinycore
package.
For larger ramdisks, we attempt to use chrony, which superceeds the ntp
package as a combined time server and client.
Change-Id: If99f2df31af8e4d41ad7813d25f0d779abc23f7a
Needed-By: https://review.opendev.org/#/c/707911/
Upgrading tinycore from version 9.x to 10.x
This change was merged [1] and reverted [2], let's give it another
try and eventually discuss about possible issues.
[1] https://review.opendev.org/688411
[2] https://review.opendev.org/698098
Change-Id: I831b414461f77c65e34b0f357763e38e74e65e29
Tinycore needs xfs support in order to be used in certian
low memory testing situtions with images that prefer
to use XFS as the filesystem.
Change-Id: Ief9c04a57c3e3249ddf081b249aa583169065582
I'm requesting this job be temporarily merged for testing publishing
artifacts to an AFS volume instead of pushing it to a static server.
This is part of the efforts to retire our static.openstack.org server
and serve files from our distributed storage [1].
Because the publishing steps happen in the post phase using a secret
value in project-config to get the kerberos ticket for writing to AFS,
we have to commit changes to really test them.
This repository is a good user of the artifact upload process and a
good target for testing the changes on just one repository.
This adds a job ironic-python-agent-build-image-tinyipa-publish-to-afs
which is ultimately parented to the new
publish-openstack-artifacts-with-afs from project-config. The only
difference is that this will upload the output to AFS, where I will
check that everything copied as expected. We can then revert this.
Ultimately we will change the publish-openstack-artifacts job in
project-config -- this will be transparent to end-users such as this
repository as we will be switching tarballs.openstack.org to use this
at the same time.
Depends-On: https://review.opendev.org/705159
[1] https://docs.opendev.org/opendev/infra-specs/latest/specs/retire-static.html
Change-Id: Ib2ae8c2d9f59695ce7af5414f73e1f4bcc7ae462
Using the virtualenv command will generate a virtualenv with the
default python exec for the entire system, that means that even
if DIB_PYTHON is python3, the virtualenv will use python2.
With this change we use the venv embedded command if the version
of Python is 3.x to generate a virtualenv with the correct
Python 3 version.
Change-Id: I8bec32c5e0dae2dee27615146f946a9649f23fd1
As found recently, pip with Python 3.6 and forward has some issues
installing tarballs that contain files with non-ascii characters
in their names.
This is due mainly to the fact that the default locale in the
system is set to C [1].
As a workaround, we run the installation of the packages in the
virtualenv forcing C.UTF-8 locale.
[1] https://github.com/pypa/pip/issues/7667
Change-Id: Idfb8b121a43a0bb74844fd63d5c2507d7b888b15
This job is used on stable branches and is currently broken. This
change introduces a workaround for older DIB and re-enables the job.
Change-Id: I100576c639649a69a8e95463ca87bedda4bbadc3
We need to be able to pick up fixes quicker than now and to use
depends-on with DIB changes. This change achieves it.
Change-Id: Ic6ab011370b08d06a5c914736949ead2cb498e56
These systems use LIO via python-rtslib, and targetcli depends
on libX11 and other GUI packages. The target-restore package
(coming from python-rtslib) is enough to create the necessary
directories (e.g. /etc/target).
Change-Id: Ide0d23d3834c52edcbc569c05ce95ba78e1bf73d
CentOS 7 uses Python 2. Although it's possible to install Python 3
on it, it not trivial with DIB. We should rather switch to
a distribution where Python 3 is the default version.
As a nice side effect, the CentOS 8 images seem smaller.
The CentOS 7 job definitions are kept around since they're used
on stable/train.
Change-Id: I6b23da21eab19c69f7b070adff76b35e1752bf8d
Seems we have no real way to grok if there was a rescue setup failure
because we don't log any information to the console about the node
once dhcp has occured.
As such, added an additional line of text to be logged and added
the ip addr command which should save a list of addresses by
interface to the console to assist in CI job troubleshooting.
Change-Id: Ib3f6e24d0687e9da8e551355fe04faf3f86ff582
This patch converts the versions of the custom dependencies builds
to variables.
Includes:
tgt
qemu
lshq
biosdevname
ipmitool
Change-Id: I516256624b6ec12329dc02b185701b287897954d
While running TinyIPA stable/stein images in KVM virtual machines with
Tenks, we noticed that IPA would start but not execute further, which
appeared to be caused by a lack of entropy.
This patch installs haveged, a simple entropy daemon [1], into the
tinyipa ramdisk and starts it on boot, which resolves the issue.
While this problem was reproduced reliably with stable/stein and not
seen with stable/train or stable/rocky images, we will start running
haveged in all versions, for consistency. It adds less than 20 KiB to
the ramdisk.
[1] http://www.issihosts.com/haveged/
Change-Id: I7d47b7828733cc03c1ed6c370c451465a6d492b6
Story: 2006911
Task: 37554
For tinyIPA, migrate the generate_upper_constraints script in-tree.
For DIB, use a source repository with requirements to fetch
upper-constraints. As a nice side effect, it allows depending on
requirements patches in the CI.
Change-Id: I6be51b98adab641cfaa1613306cbdcc3b42de1c2
