Age | Commit message (Collapse) | Author |
|
|
|
|
|
Add python3-serial to Depends. This is not resolved by
${python3:Depends} because it is commented out in requirements.txt.
pyserial is problematic both because it is not pure python and
because it is not available for python2.6.
The commit 26ea813d2 removed pyserial and thus lost the automatic
dependency. This makes SmartOS datasource work.
|
|
In systemd, package installation before the system is fully booted
(systemctl is-system-running == starting) may result in the package not
being started. Upgrade (package_upgrade: true) can also cause failure if
that is done during systemd boot.
The solution here is:
a.) move config modules that do or may do package installation to
'final_modules'. That list is:
- snappy
- package-update-upgrade-install
- fan
- landscape
- lxd
- puppet
- chef
- salt-minion
- mcollective
b.) move cloud-final.service to run as 'Type=idle'
LP: #1576692, #1621336
|
|
test_handler_apt_source_v3.py was not cleaning up all its tmp dirs.
|
|
Old behavior allowed a user to provide:
apt_mirror: ""
And that was the same as:
apt_mirror: null
and the same as having not specified apt_mirror at all. This maintains
that behavior for all old string values.
LP: #1621180
|
|
This should be fqdn, not fdqn.
LP: #1607810
|
|
Assuming that the installed package creates the directory
/etc/salt/pki/minion (ubuntu yakkety does), this will pick that
directory for the pki_dir default.
If it does not exist, then it will maintain the old directory.
LP: #1609899
|
|
./packages/bddeb --release=xenial
that will get you a changelog with Distribution of xenial
rather than UNRELEASED.
|
|
This allows both v1/2 and and v3 formats to exist in config.
If both are present, then prefer v3. If values are not the same
then a ValueError is raised.
LP: #1616831
|
|
This syntax doesn't work in python 2.6
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
|
|
Imported using git-dsc-commit.
|
|
Spacewalk is used by some peopel to manage connections into redhat package
management systems and kickstart and various other tasks, so having a
system be able to do the needed tasks on first boot to integrate with that
system would be very useful (to some).
See: https://fedorahosted.org/spacewalk/
|
|
Adds an install option for for OpenRC init scripts.
I've also restricted installing tests more correctly.
Also, don't hardcode the path to ip (/bin/ip on gentoo).
|
|
The OpenStack network_data.json does not provide a name for bond links.
This change makes it so a dummy one is generated and used instead
to satisfy cloud-init which does require one.
In order to write the correct link (underlying 'link' names)
for the bonds, we maintain a list of info by ids so we can easily
get the right device name.
Also:
* add a vlan test case that similarly references an id rather than name.
* make bond interfaces auto
LP: #1605749
|
|
When using get_interface_mac, on a system with bond slaves, it would
return the bond_master's address. That isn't expected, and causes
problems in a caller like get_interfaces_by_mac which would then seem to
find duplicate macs on the system.
Additionally, in read_sys_net catch a errno.ENOTDIR error as ENOENT.
Opening a path as a file that has <existing_file>/anything will will raise
ENOTDIR rather than ENOENT. This handles that case in read_sys_net as a
if the file did not exist.
|
|
This adds some function to the generator to maintain the presense of a
flag file '/run/cloud-init/enabled' indicating that cloud-init is enabled.
Then, only run the dhclient hooks if on Azure and cloud-init is enabled.
The test for is_azure currently only checks to see that the board vendor
is Microsoft, not actually that we are on azure. Running should not be
harmful anywhere, other than slowing down dhclient.
The value of this additional code is that then dhclient having run
does not task the system with the load of cloud-init.
Additionally, some changes to config are done here.
* rename 'dhclient_leases' to 'dhclient_lease_file'
* move that to the datasource config (datasource/Azure/dhclient_lease_file)
Also, it removes the config in config/cloud.cfg that set agent_command
to __builtin__. This means that by default cloud-init still needs
the agent installed. The suggested follow-on improvement is to
use __builtin__ if there is no walinux-agent installed.
|
|
Change atomic_helper.write_file to have same same signature as write_file.
Add some simple unit tests for atomic_helper.
|
|
This gets Gentoo work on simple configs with static IPs or
DHCP on physical interfaces. This gets Gentoo bootable again.
|
|
os.uname is a method, not a property.
|