[Bug 1900852] Re: Remove uart1 connection from Vagrant boxes

[John Chittum]

2.5 years later, no comments or "also affects me." The workaround in
place is sub-optimal, but we're not hearing chatter of wanting something
different.

Setting as won't fix for cloud-images, as the workaround seems to be
"accepted."

** Changed in: cloud-images
       Status: New => Won't Fix

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1900852

Title:
  Remove uart1 connection from Vagrant boxes

Status in cloud-images:
  Won't Fix
Status in livecd-rootfs package in Ubuntu:
  Opinion

Bug description:
  In discussions on lp: 1874453, a user (haggai-eran) ran into an issue
  with File::NULL being turned into an absolute path on a derivative
  image rather than staying the Ruby handling of File::NULL.

  In comment 54 during verification (https://bugs.launchpad.net/cloud-
  images/+bug/1874453/comments/54), nginer tried disabling uart1
  connection entirely. He noted that previously this did not work on
  releases, however, in his current setup it did work.

  This led to me (jchittum) investigating removing configuring uart1 in
  CPC's base Vagrantfile (https://git.launchpad.net/livecd-
  rootfs/tree/live-build/ubuntu-cpc/hooks.d/base/vagrant.binary#n149).
  An initial test using the ubuntu/master branch of livecd-rootfs
  successfully booted. I also tested a user's ability to enable and add
  a serial debugging file and it worked.

  I propose the removal of the entire `config.vm.provider "virtualbox"
  do |vb|` stanza from the base Vagrantfile in Groovy and newer images,
  with further testing needed for possible SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1900852/+subscriptions