Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2680
** Bug watch added: github.com/canonical/cloud-init/issues #2680 https://github.com/canonical/cloud-init/issues/2680 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1594576 Title: cc_salt_minion behaves badly if apt-get update fails Status in cloud-init: Expired Bug description: I'm using cloud-init to setup some salt-minion config like so: #cloud-config salt_minion: conf: grains: my_grain_1: a my_grain_2: b cc_salt_minion.py triggers apt-get update. If apt-get update fails, then cc_salt_minion does not update /etc/salt/minion, but nonetheless continues. My automation depends on finding these grains, and salt- minion is already built in. Please consider the attached patch, which will skip the install if a flag is included. Alternatively, cc_salt_minion could write out /etc/salt/minion even if apt-get fails. Ross To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1594576/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp