99-gce.rules attempts to set 'noop' scheduler, which isn't available in 5.x kernel

Bug #1886391 reported by Eric Agnew
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gce-compute-image-packages (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

"GCE request" seems to indicate a preference for the 'noop' scheduler, but w/ a recently created GCE instance using the Ubuntu18 image & 5.3.0-1029-gcp kernel, noop is not an available option (only 'none' and 'mq-deadline' are available). Apparently 5.0 kernels no longer support non-multiqueue I/O schedulers (https://kernelnewbies.org/Linux_5.0#Block_layer), so this should be changed to "none", although for backwards compatibility with pre-5.0 kernels with 'noop' support, some kind of check will be necessary (unfortunately I'm not familiar enough w/ udev to know if this is possible within the udev rules file itself, or if it'd have to be done at the dpkg/config level).

## cat /sys/block/sdb/queue/scheduler
[none] mq-deadline

## cat /lib/udev/rules.d/99-gce.rules
# Give syslog write access to the kernel logs
KERNEL=="console", GROUP="syslog", MODE="0620"

# Switch to using NOOP as the default scheduler per GCE request
SUBSYSTEM=="block", ENV{DEVTYPE}!="partition", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ATTR{queue/scheduler}="noop"

Eric Agnew (th1rtyf0ur)
summary: 99-gce.rules attempts to set 'noop' scheduler, which isn't available in
- Ubuntu18
+ 5.x kernel
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gce-compute-image-packages (Ubuntu):
status: New → Confirmed
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.