questioning lack of updates thus whether installation option was ignored

Bug #1714723 reported by Nick
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

A new installation needed no updates. I installed Ubuntu 16.04.2 desktop amd64 near midnight on Aug. 16-17, 2017, and opted against updating during the installation (I wanted to test one issue before updating). So either Ubuntu 16.04.2 had never been updated when I installed it to the HDD on the above date, in which case this bug report is invalid and can be closed, or it auto-updated during installation, in which case it ignored the option against auto-updating during installation and therefore this is properly a bug. I don't know how to check which is the case but I hope someone knows how to find out if a Ubuntu server was storing updates for new installations.

I have cold-rebooted multiple times before reporting this, so I don't have the logs you prefer. Also, a search does not produce System or lsb_release -rd and a CLI terminal tells me that lsb is not a command on my system.

Revision history for this message
Nick (nick-levinson) wrote :

Correcting my error: I revisited the CLI terminal. For lsb_release, it says that no LSB modules are available.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Etienne Papegnies (etienne-papegnies) wrote :

I can confirm that this parameter seems to be ignored.
I've recently witnessed this on 17.10, and have previously seen this happening on Xenial and Zesty.
Steps to reproduce are easy:

- Create a new virtual machine in virtualbox with all default options (including networking)
- Proceed to install the system
- Monitor network usage

You'll notice a large amount of data is downloaded during install.

tags: added: xenial zes
tags: added: artful zesty
removed: zes
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.