Due to the length of the job name and the tox target we run into an
uncommon limitation; the virtualenv that tox launches is nested in a
path that is too long. This leads to an error on our longest named
job which prevents tox from running properly.
This limitation is the limit for the line length of the first line
in a shell script. In this case <virtualenv>/bin/pip has a path that
exceeds that limit by a few characters. This results in a very
confusing "OSError: [Errno 2] No such file or directory" error.
See `man execve` for more info. A quote from that manpage:
'A maximum line length of 127 characters is allowed for the first line
in a #! executable shell script.'
To reproduce this locally you can just create a very long path and
then run tox in it. Example: http://paste.openstack.org/show/478559/
Change-Id: I51f8f67d9ab139f1d539fce05ce3cc4766aeedff
Depends-On: I43fba2a5ff1890d699045496c9eaee5e849f3e75
clarkb suggested dsvm be in the job names for Kolla to follow the
job naming convention. In the case of the experimental job we have
recently merged, that it as a requirement for the name of the job.
To keep consistency within the project and within the OpenStack
community we are renaming all of the gates that use the dsvm's to the
convention that all other jobnames follow.
Since the tox paramaters do not change in the jobs/kolla.yaml, this
requires no change on the Kolla side.
Change-Id: I9a22434d99b4deb7936ecaf7b714d0dc41666367
This adds three additional gates. These new gates will deploy and test
OpenStack. In contrast to the existing gates, these new gates will
only build a subset of the images Kolla provides. It will only build
those needed to deploy OpenStack.
Change-Id: I2c94eac72c61385fe6472a95ea3c9cafa33bc22d
Depends-On: I7a24a704023cc8f19d42844636e9cb512060f693
Remove the kolla-functional-f21 job because it only runs the
removed-from-kolla bash build scripts. The build gating is now
handled by other jobs which run a Python based build tool. As a
result, evreything related to the kolla-functoinal-f21 job can be
removed.
As stands now this check will always fail because the bash buid
scripts are completely removed from the kolla repo and this check
job depends on these removed bash build scripts.
Change-Id: I4de8fb52c6a32b6999f6be4112fa0b76e9f0ac42
This builds centos in binary mode. The tox job uses Kolla's
next generation build script which is not compatible with the
initial version of our build script. As a result of this we
left the existing job intact so we maintain gating of our
image building process with our initial build script tool.
As part of the new gating with the new build, we are also gating an
entirely new Dockerfile infrastructure which is templated. These
new dockerfiles are not compatible with the legacy build script. As
a result we need the existing kolla-functional-f21 to remain intact
until we finish the build and dockerfile templated implementations.
After that we intend to remove the kolla-function-f21 gate job,
the legacy build script and the legacy dockerfiles.
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: I2a3d42d34a32a2f514b8c64f17ff54e7b08d6d7b
Apparently the gate needs more work in Kolla to be stable. I
have filed a Critial bug here after which we should be able to
revert this revert ;)
https://bugs.launchpad.net/kolla/+bug/1466677
This reverts commit 6d3e0cac21.
Change-Id: Ie7f7b4b5db019ea6298fe103aff8c26eedcfa214
Because of a recent change, docker image building cannot be done
as the root user. This is a good thing ;) But breaks the current
gate.
Also we have a setup_docker.sh script already in our tools directory,
so rename the script we are running to setup_gate.sh because that is
actually what the script does.
Change-Id: I8f86616fb19b4b03f34fe40acf1689f6b174ff98
We believe the Kolla build will take between 1 and 3 hours. We
are not certain exactly how long it will take, so we plan to
start with 90 minutes and later tune the timer to match our
average run-times + 20%.
Note our gate functional job builds about 40 docker images which
takes quite awhile.
Change-Id: Ifd052464cacbe4ce4d0584277aa729ab151d48fe
Otherwise, the script will fail.
Also add for tox invocation until potential group issue is sorted out
(group membership applied to current running shell).
Change-Id: Ic84d5435761deae0d28909c813cb1d87540fbb21
The setup_docker script downloads and starts the Docker binary while
the tox run performs the actual test of verifying all the Dockerfiles
in the project successfully builds or fails as expected.
Change-Id: I4d05c32a2faa30f0b15487dfd605089f61baf985