FEDORA-2016-aceff68672 created by kevin 6 years ago for Fedora 23
stable

Update to 2.1 upstream with bugfixes and enhancements. See https://github.com/ansible/ansible/blob/stable-2.1/CHANGELOG.md for more details.

How to install

sudo dnf upgrade --advisory=FEDORA-2016-aceff68672

This update has been submitted for testing by kevin.

6 years ago

This update has been pushed to testing.

6 years ago
User Icon melmorabity commented & provided feedback 5 years ago
karma

Works fine

User Icon filiperosset commented & provided feedback 5 years ago
karma

no regressions noted

This update has been submitted for stable by bodhi.

5 years ago
User Icon hhlp commented & provided feedback 5 years ago
karma

Look Good to Me

This update has been pushed to stable.

5 years ago
User Icon anonymous commented & provided feedback 5 years ago

Could you please stop updating ansible versions within stable releases? Ansible upgrades are not backwards compatible. After already having to deal with fedora 23 getting ansible 2 in the middle of the release, now I have to deal with https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user. This is not what I believe is the accepted behavior in fedora stable releases.

karma: -1

User Icon kevin commented & provided feedback 5 years ago

Serveral notes:

  • If you want to stay on old/stable, you can install the 'ansible1.9 ' package.
  • You don't have to switch to the become syntax, the old syntax is depreciated, but should still work fine.
User Icon anonymous commented & provided feedback 5 years ago

Thanks for the comments, I wasn't aware of the ansible1.9 package. As for the new become syntax, it definitely broke on me before. Is this something that's patched now? As far as I can tell, it would only work if setfacl is installed on the target machine. There's nothing that would require that to happen as far as I can tell.

User Icon kevin commented & provided feedback 5 years ago

Well, first it's a security issue, so erroring is better than silently being insecure (IMHO). Also, install setfacl on the target machine is only one of a number of workarounds. You can enable pipelining, you can make the connection as root, or you can set allow_world_readable_tmpfiles in your ansible.cfg. Sorry if this broke things for you, but the eariler versions were insecure here. ;(


Please login to add feedback.

Metadata
Type
enhancement
Karma
3
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
disabled
Dates
submitted
6 years ago
in testing
6 years ago
in stable
5 years ago
BZ#1332233 remote_tmp filling up since upgrading to ansible 2
0
0
BZ#1334097 ansible fails when running Task [setup]
0
0
BZ#1336266 Ansible 2.0.2.0 regression (known bug, fixed upstream)
0
0
BZ#1337474 dnf: state=present|absent returns skipping instead of changed
0
0

Automated Test Results