| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Let morph recognise the architecture string reported by
a big-endian ARMv8 kernel.
Change-Id: I64323e6c2a4675a8cc34f185b10fa04754ebe8c8
|
| |
| |
| |
| | |
Change-Id: I1521c0bdec4d7a6812f8988a2349e66b08161de8
|
| |
| |
| |
| | |
Change-Id: I44693d15aa5e92d5f09720065788adff34f8685c
|
| |
| |
| |
| | |
Change-Id: If011a5518fd30914c89b00099b9d05cff5cd3959
|
|/
|
|
| |
Change-Id: Ic715815bbad3ef1ee9ab457b62a194eaef45744c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I accidentally tried to deploy a Baserock upgrade to a Fedora cloud
machine. Every SSH command that Morph ran got the following output:
Please login as the user "fedora" rather than the user "root".
The existing implementation of check_ssh_connectivity() didn't raise
an exception, leading to confusing errors further down.
The new implementation produces this error:
ERROR: Unexpected output from remote machine: Please login as the
user "fedora" rather than the user "root".
Change-Id: Ida5a82b25d759167aa842194b0d833d0565b4acf
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I6e714d1994632875a5a15f840fe8ab3a66dddc77
|
|\ \ \
| |/ /
| | |
| | | |
of definitions format"
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
definitions format
This patch will add the following restriction:
if VERSION exist
and its a YAML file
and its a dict
and has the key 'version'
and the type stored in the 'version' key is an int
and that int is not in the supported format,
then fail.
So, if someone is using 'version: 4' in VERSION, morph will fail (as
opposed to current morph, that will not fail in the check but will
likely fail when it tries to compile)
Change-Id: I555f7e6018b9bdf18c80039df92a253acbd51c8c
|
| | |
| | |
| | |
| | |
| | |
| | | |
This adds a new config extension to allow deployments to write to /etc/hosts
by adding HOSTS_x: </etc/hosts line> to a cluster morph in a similar manner
to the fstab.configure extension.
|
| | | |
|
| | |
| | |
| | |
| | | |
A function to read lines from a dictionary and append them to a file
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Some lines were more than 79 characters long. This was causing
./check --full to fail on master of morph. This commit fixes the
lines in question.
Change-Id: I80969d2d89d3922e021b716c250796188d7a7f4c
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Ibda7a938cd16e35517a531140f39ef4664d85c72
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Rename instead removal in case the user is already using a
10-dhcp.network file
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use DHCP by defaul in the default interfaces:
- for /etc/networ/interfaces: "lo:loopback;eth0:dhcp,hostname=$(hostname)"
- for networkd: "e*:dhcp"
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
255.255.255.0 -> 24
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
a function
|
|/ / /
| | |
| | |
| | | |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
| | |
| | |
| | |
| | | |
I was meant to do this at merge time but didn't.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I771c3de9cecda7a503f4d36ae5d9fabc040892e4
|
|\ \ \ \
| |/ / / |
|
| |/ /
| | |
| | |
| | | |
Change-Id: I7c6f618d5d19e03d906798a6f799d74ac55b0d09
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
Reviewed-By: Adam Coldrick <adam.coldrick@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If we know the build system for a chunk is cached then we also know that
it doesn't have a chunk morph, so we don't need to look for one.
(We only cache the build systems of chunks that don't have chunk morphs)
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug that causes morph to run build system detection
even though the build system has already been cached.
The cache is accessed before the key has been computed
(absref isn't known until after we've called resolve_ref)
so it always misses.
|
|\ \
| |/
|/|
| |
| | |
Reviewed-By: Adam Coldrick <adam.coldrick@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
| |
| |
| |
| |
| | |
This makes it easier to spot if an incomplete build was due to the user
cancelling, or if it represents a dropped connection or internal error.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It gets messy having hundreds of build-step-xx.log files in the current
directory, and if two builds are run in parallel from the same directory
the logs for a given chunk will be mixed together in one file.
Now, a new directory named build-0, build-1, build-2 etc is created for
each new build.
If the user passes --initiator-step-output-dir the logs will be placed
in that directory, instead. This behaviour is the same as before.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only fail if:
- VERSION file exists
- and its a yaml file
- and its a dict
- and has the key 'version'
- and the contents of the key 'version' is an int
- and that int is in the list of non_supported_versions (empty
at the moment)
|
| | |
| | |
| | |
| | | |
_get_morphology_from_definitions() and _get_morphology_from_repo()
|
| | |
| | |
| | |
| | | |
load_from_string()
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
And make _get_morphology() use it
|
| | |
| | |
| | |
| | | |
And make _get_morphology_from_definitions() use it
|