fuel-master fail to migrate centos7.4

Bug #1721226 reported by Aleksey Zvyagintsev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
In Progress
High
Aleksey Zvyagintsev

Bug Description

Fuel-master fails on after-update puppet apply action :
$ puppet apply -d -v --detailed-exitcodes "/etc/puppet/modules/fuel/examples/host.pp"

with error:
Debug: Augeas[Turn off sudo requiretty](provider=augeas): /augeas/files/etc/sudoers/error = parse_failed
Debug: Augeas[Turn off sudo requiretty](provider=augeas): /augeas/files/etc/sudoers/error/pos = 2308
Debug: Augeas[Turn off sudo requiretty](provider=augeas): /augeas/files/etc/sudoers/error/line = 65
Debug: Augeas[Turn off sudo requiretty](provider=augeas): /augeas/files/etc/sudoers/error/char = 12
Debug: Augeas[Turn off sudo requiretty](provider=augeas): /augeas/files/etc/sudoers/error/lens = /usr/share/augeas/lenses/dist/sudoers.aug:529.10-.70:
Debug: Augeas[Turn off sudo requiretty](provider=augeas): /augeas/files/etc/sudoers/error/message = Iterated lens matched less than it should
Debug: Augeas[Turn off sudo requiretty](provider=augeas): Will attempt to save and only run if files changed
Debug: Augeas[Turn off sudo requiretty](provider=augeas): sending command 'set' with params ["/files/etc/sudoers/Defaults[*]/requiretty/negate", ""]
Debug: Augeas[Turn off sudo requiretty](provider=augeas): Closed the augeas connection
Error: /Stage[main]/Main/Augeas[Turn off sudo requiretty]: Could not evaluate: Saving failed, see debug

The reason of such error, updated sudoers package, which by default introduce new option
Defaults match_group_by_gid
Read more info at https://groups.google.com/forum/#!topic/puppet-users/IsAigbsPJ9o

Currently, ther is no upstream solution, and only one possible - implement WA with manual updating /usr/share/augeas/lenses/dist/sudoers.aug file

Changed in fuel:
milestone: none → 9.x-updates
status: Confirmed → In Progress
Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :
Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.