writing of sudoers is not idempotent

Bug #1998539 reported by Mina Galić
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Undecided
Unassigned

Bug Description

after several (full) re-runs of cloud-init, my /usr/local/etc/sudoers.d/90-cloud-init-users file looks like this:

# Created by cloud-init v. 22.3 on Wed, 05 Oct 2022 21:34:14 +0000

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

# User rules for freebsd
freebsd ALL=(ALL) NOPASSWD:ALL

while this has no affect on sudo's functionality, it's also not deduplicated:

freebsd@fbsd14-amd64 ~> sudo -l
User freebsd may run the following commands on fbsd14-amd64:
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL
    (ALL) NOPASSWD: ALL

given what we're trying to accomplish with writing sudoers rules, I think it would make sense to *always* rewrite the file, regardless of whether it exists or not.

Tags: bitesize
Chad Smith (chad.smith)
Changed in cloud-init:
status: New → Incomplete
status: Incomplete → Triaged
Chad Smith (chad.smith)
tags: added: bitesize
Revision history for this message
James Falcon (falcojr) wrote :
Changed in cloud-init:
status: Triaged → Expired
Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 23.3.

This bug is believed to be fixed in cloud-init in version 23.3. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Expired → Fix Released
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.