We're seeing some job failures with IPv6 when tinycore is
getting pulled in for rackspace hosts. The underlying issue
appears to be that we don't have an IPv6 route in the kernel.
First step, get more data.
Change-Id: I5b478893a2f114bdbeee53af5f44dc8139b02c52
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
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
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