Re: Friday bug triage

[Dan Streetman]

On Fri, Jan 7, 2022 at 5:10 PM Bryce Harrington
 wrote:
>
> On Fri, Jan 07, 2022 at 08:34:57PM +0530, Utkarsh Gupta wrote:
> > Hello,
> >
> > On Fri, Jan 7, 2022 at 7:56 PM Utkarsh Gupta
> >  wrote:
> > >   LP: #1954854 - (Incomplete) [bind9] - bind
> > >   9.16.1-ubuntu on ubuntu 20.04 randomly
> > >   exits with [...]
> > >
> > > The bug reporter got back with some logs
> > > and files collected via apport. Since the
> > > bug is not easily reproducible, I am not quite
> > > sure what's the best way forward. That said,
> > > me/Paride are looking into it.
> >
> > Here's an update: we couldn't find anything worthwhile from the
> > upstream tracker or changelog or anything and neither of us have
> > enough experience with crash files.
>
> Here's a paint-by-numbers way to get stacktraces from .crash files:
>
> 0.  Enable debug symbols.  Various ways to do this, one way is to append
> ddebs to your apt sources:
>
> $ echo "deb http://ddebs.ubuntu.com focal main restricted universe 
> multiverse" | sudo tee -a /etc/apt/sources.list
> $ echo "deb http://ddebs.ubuntu.com focal-updates main restricted 
> universe multiverse" | sudo tee -a /etc/apt/sources.list
>
> $ sudo apt install ubuntu-dbgsym-keyring
> $ sudo apt update
>
> 1.  Install package with debug symbols
>
> $ sudo apt install bind9 bind9*-dbgsym

Note this (using ddebs repo) only works if the crash resulted with the
latest version of all associated packages; in a normal support
situation where at least some package versions (that are relevant to
what caused the crash, e.g. application package and dep libs) are not
the latest, the ddebs repo unfortunately isn't useful since it only
provides the dbgsyms for the latest package versions.

It's frequently more helpful to simply use pull-lp-ddebs to get the
specific dbgsyms for the package versions that generated the crash
file.

Of course, hopefully eventually someone (*ahem* sergiodj) will get an
Ubuntu debuginfod server set up, which would allow direct access to
the appropriate dbgsyms, but that's not available yet.

>
> Often there are also secondary libs or deps with more syms we'll
> need.  This examines the binary for other possible dbgsym's:
>
> $ sudo apt install debian-goodies
> $ sudo apt install $(find-dbgsym-packages /usr/sbin/named 2>/dev/null)
>
> The following NEW packages will be installed:
>   libcap2-dbgsym libcom-err2-dbgsym libgcc-s1-dbgsym libicu67-dbgsym 
> libjson-c5-dbgsym libkeyutils1-dbgsym
>   libkrb5-dbg liblmdb0-dbgsym liblzma5-dbgsym libmaxminddb0-dbgsym 
> libxml2-dbgsym zlib1g-dbgsym
>
>
> 2.  Download the .crash file to a tmp directory
>
> $ mkdir /tmp/bind9-crash
> $ cd /tmp/bind9-crash
> $ wget 
> https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1954854/+attachment/5551855/+files/_usr_sbin_named.114.crash
>
> 3.  Register the package with the crash file
>
> $ cat <(echo "Package: bind9") _usr_sbin_named.114.crash > 
> bind9_named.114.crash
>
> Apport-retrace complains if the package isn't specified, but apport
> hooks don't insert it, so you have to do it manually.  ¯\_(ツ)_/¯
>
> 4.  Doublecheck that your installed version matches the reporter's
> version exactly:
>
> $ apt-cache policy bind9 | grep '^  Installed'
>   Installed: 1:9.16.1-0ubuntu2.9
>
> Unfortunately the .crash file doesn't include the version number,
> but the LP bug report will show it:
>
>  Package: bind9 1:9.16.1-0ubuntu2.9
>
> 5.  Retrace symbols
>
> $ sudo apt-get install apport-retrace
> $ apport-retrace bind9_named.114.crash
>
> The above command inserted an empty 'separator: ' line into the crash
> file, which apport-unpack will choke on, so delete that line:
>
> $ sed -i '/^separator: *$/d' ./bind9_named.114.crash
>
>
> 6.  Unpack crash
>
> $ apport-unpack bind9_named.114.crash crash-114
>
> The 'crash-114/' subdirectory will now include a ThreadStacktrace file
> that hopefully(!) should have a usable backtrace.  This one looks
> great but the full stacktrace is rather TMI.
>
> $ wc -l crash-114/ThreadStacktrace
> 415 crash-114/ThreadStacktrace
>
>
> 7.  (Advanced) GDB
>
> $ apt-get source bind9
> $ cd bind9-9.16.1/
>
> $ apport-retrace --gdb /tmp/bind9-crash/bind9_named.114.crash
>
> This will give you an interactive gdb session on the reporter's
> coredump.  For example, with this particular crash, we can get a
> simple backtrace:
>
> (gdb) bt
> #0  isc__nm_tcp_send (handle=0x7eff7522dbb0, region=0x7eff7d39a9b8, 
> cb=0x7eff887675a0 ,
> cbarg=0x7eff7d39a9a8) at tcp.c:852
> #1  0x7eff88a2e707 in client_sendpkg (client=client@entry=0x7eff754c31b0, 
> buffer=,
> buffer=) at client.c:331
> #2  0x7eff88a2ffe9 in ns_client_send (client=client@entry=0x7eff754c31b0) 
> at client.c:592
> #3  0x7eff88a3e9b0 in query_send (client=0x7eff754c31b0) at query.c:552
> #4  0x7eff88a469a7 in ns_query_done 

Re: Wednesday Triage Report (2021-07-14)

[Dan Streetman]

On Wed, Jul 14, 2021 at 11:48 AM Sergio Durigan Junior
 wrote:
>
> ustriage found 9 bugs.  Nothing worthwhile to report; everything is
> being properly handled by the team.

Could you expand on this a bit? It's not exactly clear what it means.

For example from the links on the server team wiki page
(https://wiki.ubuntu.com/ServerTeam) I see the 'Top 20 Bugs' (which
are all the ones tagged 'server-next' right?) which includes bugs
where there's been no update in over a year (e.g. LP:#1860997,
LP:#1872145) and others where the bug appears to be already fixed
(e.g. LP:#1916485).

The full list of bugs subscribed by ~ubuntu-server is larger than
seems useful, currently 815, so is that list being used for active
work? If so, can you go into some detail on what work is done to bugs
in that list?

>
> --
> Sergio
> GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Tuesday bug triage report

[Dan Streetman]

On Tue, Jun 22, 2021 at 8:34 AM Lucas Kanashiro
 wrote:
>
> Bugs last updated on 2021-06-21 (Monday)
> Date range identified as: "Tuesday triage"
> Found 12 bugs
>
> There are active people working on almost all bugs, just one comment below:
>
> https://pad.lv/1933161 - (New)[ubuntu-advantage-tools] - Errors 
> on enabling livepatch
> -> I believe this bug is missing information to actually be reproducible, but 
> I decided to not touch it since I am not aware of what's happening in the 
> ua-tools land. I'll leave this to someone from the table-flip squad.

what's the "table-flip squad"?

>
> ---
> Bugs tagged 'server-next' and not touched in 60 days
> Found 0 bugs
>
> ---
> Bugs in backlog and not touched in 180 days
> Found 0 bugs
>
> Lucas Kanashiro.
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Bug Triage Monday 22nd Feb 2021

[Dan Streetman]

On Tue, Feb 23, 2021 at 7:12 AM Lucas Kanashiro
 wrote:
>
> Hi,
>
> On Tue, Feb 23, 2021 at 4:41 AM Christian Ehrhardt 
>  wrote:
>>
>>
>> https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1915828
>> An issue with pacemaker / libqb not releasing the cluster.
>> Lucas is already subscribed I also added the team subscription now.
>> @Lucas should this be server-next tagged and assigned to you?
>
>
> I think so, this bug needs some further investigation. However, I am not sure 
> what is the exact meaning of the "sts" tag, is someone from the STS team 
> working on it? Or are they just tracking changes on the bug report?

Yes, this is owned by dgadomski and slashd

>
> Lucas Kanashiro.
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: ubuntu-helpers: New script "enable-proposed"

[Dan Streetman]

On Wed, Jul 22, 2020 at 3:39 PM Bryce Harrington
 wrote:
>
> On Wed, Jul 22, 2020 at 08:57:05AM -0500, Simon Quigley wrote:
> > Hello,
> >
> > On 7/22/20 8:22 AM, Dan Streetman wrote:
> > > Since it's related to this topic, the add-apt-repository in this ppa
> > > has support for adding/enabling deb-src and arbitrary pockets as well
> > > as private ppas and more:
> > > https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/add-apt-repository
>
> If that makes it easy to enable -proposed, that would indeed be very
> helpful.

yeah just like

$ sudo add-apt-repository -p proposed

>
> Googling "how to enable -proposed from CLI" returns too many results
> that have people either hand edit sources.list or simply append
> hand-written deb strings.  If those docs can give a simple-to-run
> invocation of add-apt-repository it would help eliminate user error and
> confusion.
>
> > > I need to find some time to push the changes into the upstream repo.
> > > https://code.launchpad.net/~ubuntu-support-team/software-properties/+git/software-properties/+ref/devel
> >
> > Merged, here you go:
> > https://launchpad.net/ubuntu/+source/software-properties/0.99.0
> >
> > (We're still a little bit away from Feature Freeze and we just released
> > an LTS. Now is the time to test major updates to software.)
> >
> > On 7/21/20 8:37 PM, Bryce Harrington wrote:> I've also added an
> > 'enable-proposed' script, similar to enable-debsrc,
> > > which adds DIST-proposed entries (deb and deb-src) for components
> > > currently enabled.  IOW, if you don't have
> > > universe/restricted/multiverse components enabled for anything, it won't
> > > add them for -proposed, but if you do, it will.
> > >
> > > The script also strives to use the same archive URI you are using for
> > > the main component, so if you're using a mirror it will also pull
> > > -proposed from that mirror too.
> > >
> > > https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/bryce/enable-proposed
> >
> > Thanks for your work here! How much of this is now in Groovy with the
> > above changes, and what can be merged into software-properties?
>
> Not sure, but I did notice a couple things I wished were in the API.
>
> First, a way to easily fuzzy search for a given entry, such as the one
> for the main component.  I ended up just iterating through all the
> components and examining their props, but it feels a bit brittle.  A
> sp.sourceslist.search() or similar would have given a cleaner solution.

I added a list option, e.g.:

$ add-apt-repository -L
deb http://archive.ubuntu.com/ubuntu focal universe restricted multiverse main
deb http://archive.ubuntu.com/ubuntu focal-updates universe restricted
multiverse main
deb http://archive.ubuntu.com/ubuntu focal-backports universe
restricted multiverse main
deb http://security.ubuntu.com/ubuntu focal-security universe
restricted multiverse main
deb http://ppa.launchpad.net/ubuntu-support-team/add-apt-repository/ubuntu
focal main

it filters out deb-src lines by default but you can include them with:

$ add-apt-repository -Ls
deb http://archive.ubuntu.com/ubuntu focal multiverse main universe restricted
deb-src http://archive.ubuntu.com/ubuntu focal multiverse main
universe restricted
deb http://archive.ubuntu.com/ubuntu focal-updates multiverse main
universe restricted
deb-src http://archive.ubuntu.com/ubuntu focal-updates multiverse main
universe restricted
deb http://archive.ubuntu.com/ubuntu focal-backports multiverse main
universe restricted
deb-src http://archive.ubuntu.com/ubuntu focal-backports multiverse
main universe restricted
deb-src http://archive.canonical.com/ubuntu focal partner
deb http://security.ubuntu.com/ubuntu focal-security multiverse main
universe restricted
deb-src http://security.ubuntu.com/ubuntu focal-security multiverse
main universe restricted
deb http://ppa.launchpad.net/ubuntu-support-team/add-apt-repository/ubuntu
focal main
deb-src http://ppa.launchpad.net/ubuntu-support-team/add-apt-repository/ubuntu
focal main

>
> Second, I'm not sure whether it's expected that users should access the
> internals of entries (e.g. entry.dist, entry.file).  If so, the docs
> don't document them and would make them more convenient to use.  If not,
> then getter/setter routines or similar might be appropriate.
>
> > Thanks Dan and Bryce, this definitely makes things a lot easier.
>
> Hey and thanks for maintaining SoftwareProperties.  Going into this task
> I was anticipating needing to parse sources.list myself, so in examining
> add-apt-repository's code was pleased to discover SoftwareProperties and
> find that it did most of the work for me, and let me mak

Re: ubuntu-helpers: New script "enable-proposed"

[Dan Streetman]

Since it's related to this topic, the add-apt-repository in this ppa
has support for adding/enabling deb-src and arbitrary pockets as well
as private ppas and more:
https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/add-apt-repository

I need to find some time to push the changes into the upstream repo.
https://code.launchpad.net/~ubuntu-support-team/software-properties/+git/software-properties/+ref/devel

On Wed, Jul 22, 2020 at 8:38 AM Bryce Harrington
 wrote:
>
> I've also added an 'enable-proposed' script, similar to enable-debsrc,
> which adds DIST-proposed entries (deb and deb-src) for components
> currently enabled.  IOW, if you don't have
> universe/restricted/multiverse components enabled for anything, it won't
> add them for -proposed, but if you do, it will.
>
> The script also strives to use the same archive URI you are using for
> the main component, so if you're using a mirror it will also pull
> -proposed from that mirror too.
>
> https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/bryce/enable-proposed
>
> Bryce
>
> On Tue, Jul 21, 2020 at 04:20:58PM -0700, Bryce Harrington wrote:
> > I've added a simple little script to enable deb-src lines in
> > sources.list to ubuntu-helpers:
> >
> >   
> > https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/bryce/enable-debsrc
> >
> > This script modifies your /etc/apt/sources.list and
> > /etc/apt/sources.list.d/* files, and for each enabled deb line, it
> > uncomments the corresponding deb-src line.
> >
> > In case anyone else finds it useful, there it is.
> >
> > Bryce
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry

[Dan Streetman]

On Mon, Jun 15, 2020 at 3:08 AM Rafael David Tinoco
 wrote:
>
> Bugs last updated between 2020-06-12 (Friday) and 2020-06-14 (Sunday) 
> inclusive
> Date range identified as: "Monday triage"
> Found 20 bugs
>
> https://pad.lv/1817955 -  (Confirmed) [krb5]   - Getting
> new DN is out of the realm subtree error on adding principal
>
> > subscribed ebarretto (author of the security fix that caused the regression)
> > subscribed ubuntu-server
> > triaged for trusty, fix released for groovy
>
> https://pad.lv/1882527 -  (Confirmed) [mysql-8.0]  - mysql
> timeoutsec results in killing mysql process
>
> > triaged for all supported releases
> > tagged as server-next and high prio for groovy
> > it shall be an easy fix/sru: disable TimeoutSec from systemd service unit 
> > (upstreamed already)
>
> https://pad.lv/1882791 -  (Confirmed) [mysql-8.0]  - package
> mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade:
> installed mysql-server-8.0 package post-installation script subprocess
> returned error exit status 1
>
> > incomplete (upgrade)
> > could not stop previous instance issue (very frequent)
>
> https://pad.lv/1883090 -  (Confirmed) [apache2]- package
> apache2 2.4.41-4ubuntu3 failed to install/upgrade: el subproceso
> instalado paquete apache2 script post-installation devolvió el código
> de salida de error 1
>
> > similar upgrade issues have been seen with apache2 and its mods
> > asked @bryce if he hadn't worked on this (iirc) recently
> > it seems that deferred pkg configuration (after deps) does not work
>
> https://pad.lv/1883307 -  (New)   [mysql-8.0]  - package
> mysql-server-8.0 (not installed) failed to install/upgrade: el
> subproceso nuevo paquete mysql-server-8.0 script pre-installation
> devolvió el código de salida de error 1
>
> > incomplete, weird error about /etc/mysql/FROZEN
> > asked more information
>
> https://pad.lv/1883320 -  (New)   [sosreport]  - [kvm]
> change check_enabled to /dev/kvm
>
> > sosreport and @slashd is on it, nothing on our side
>
> https://pad.lv/1883398 -  (New)   [qemu]   - USB
> serial device passtrough causes qemu to segfault and kill the VM
>
> > asked for detailed reproducer or core file
> > subscribed ubuntu-virt and @cpaelzer
> > stated as incomplete until then
>
> https://pad.lv/1883413 -  (New)   [bind9]  - bind9
> /var/cache/bind rights not set properly
>
> > not a bug, end user wanted to document his finding more than anything
> > flagged as opinion and subscribed ubuntu-server
>
> ---
> Bugs tagged 'server-next' and not touched in 60 days
> Found 2 bugs
>
> https://pad.lv/1785383 - (Triaged)[dnsmasq]- missing
> EDNS0 record confuses systemd-resolved
> also:  - (New)[systemd]- missing
> EDNS0 record confuses systemd-resolved
>
> > @ddstreet seems to have caught this to himself, cc'ing him

yes, this is an unfortunate loong running bug that is due to a
patch to systemd that we carry, that isn't upstream.  It will require
me (or someone) being able to go to a Starbucks to test with their
wifi, so I (or someone) can create a proper patch to workaround their
broken wifi captive portal, that we can then get merged upstream and
drop the problematic patch we carry.  That's been made difficult by
COVID-19, of course, but I do still want to try to get to this
sometime this summer.

>
> ---
> Bugs in backlog and not touched in 180 days
> Found 0 bugs

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Triage report for 2020-05-04 (Tuesday triage)

[Dan Streetman]

On Tue, May 5, 2020 at 6:28 PM Lucas Kanashiro
 wrote:
>
> == Migration ==
>
> The regressions below seem real issues, they were already re-triggered and 
> they failed:
>
> * php-parser/4.2.2-2 regression in armhf is blocking php7.4/7.4.3-4ubuntu2
> * chrony/3.5-6ubuntu6 regression in armhf is blocking libcap/1.9.1-4
>
> I did not have too much time to investigate the issues above. And most of the 
> other packages listed in our page are waiting for builds or are candidates to 
> migrate.
>
> == Triage ==
> Bugs last updated on 2020-05-04 (Monday)
> Date range identified as: "Tuesday triage"
> Found 12 bugs
>
> Many bugs have been worked on by the team.
> Some notes below:
>
> LP: #1869848 - (Confirmed)  [libvirt]- libvirtd 
> virNetSocketReadWire:1811 : End of file while reading data: Input/output error
> * Subscribed ubuntu-server. It has affected some users but I was not able to 
> confirm the bug be
> cause they are using a version not in the main archive, maybe in some cloud 
> related PPA? I think Christian or Rafael should take a look at it.
>
> LP: #1876537 - (Incomplete) [dovecot]- dovecot eating mail 
> indexes /var/dovecot-index/user
> * The reporter mentioned it was an issue on their side, not a bug, so I 
> marked it as Invalid.
>
> LP: #1876781 - (New)[vlan]   - ifupdown scripts have no 
> execute rights!
> * Marked as Triaged and subscribed ubuntu-server. The scenario described in 
> the bug report is true, and we should check this out.

wow, it's been like that since disco...I'm not really sure how I
screwed that up, but I definitely did...I'll do an upload for that.
Oops.

>
> ---
> Bugs tagged 'server-next' and not touched in 60 days
> Found 2 bugs
> LP: #1723350 - (Confirmed)  [sssd]   - sssd offline on boot, 
> stays offline forever
> * Andreas, I think you want to revisit this bug when you have some time.
>
> LP: #1865501 - (Triaged)[libpcap]- libpcap-dev and 
> derivatives missing libpcap.pc
> * Bryce, you provided a patch for this bug for Disco, are you planning to 
> keep working on this?
>
> ---
> Bugs in backlog and not touched in 180 days
> Found 0 bugs
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: git-ubuntu commands to drop for 1.0?

[Dan Streetman]

On Thu, Apr 9, 2020 at 5:29 PM Bryce Harrington
 wrote:
>
> git-ubuntu has proof-of-concepted a number of subcommands during its
> initial development.  As we're nearing the 1.0 release, we'd like to
> narrow our supported featureset to the ones in heaviest use by users.
>
> Ones that are more challenging to support or that are less heavily used,
> will be removed from the codebase, allowing us to focus on strengthening
> the remaining set.
>
> The UNIX philosophy is "Do one thing, and do it well", and for
> git-ubuntu the principle theme is the management of the repository
> itself, as opposed to the wider packaging workflow for which there are
> other tools available.
>
> Here's our first take at what we think might stay vs. go:
>
>   * git ubuntu clone  [Keep]

this is the only command I've ever used, actually.  I think that's
probably largely due to:

$ git ubuntu --help
No manual entry for git-ubuntu

I know there are issues around being able to provide man pages from a
snap, but man pages really are helpful...

Also, I also know that 'git-ubuntu --help' (or 'git ubuntu -h') does
produce some help output, but that output also refers to man pages
that don't (seem to) exist, e.g.:

"For more information on the commands see:

  $ git ubuntu  --help
  $ man git-ubuntu-

More information about git ubuntu itself is available at:

  $ man git-ubuntu
"

In any case, removing any of the subcommands below wouldn't impact me
personally.  Thanks!

>   * git ubuntu export-orig[Keep]
>   * git ubuntu import [Keep]
>   * git ubuntu merge  [Keep]
>   * git ubuntu queue  [Keep]
>   * git ubuntu remote [Keep]
>   * git ubuntu submit [Keep]
>   * git ubuntu tag[Keep]
>
>   * git ubuntu import-local   [Remove]
> - We suspect this is mostly unused?
>
>   * git ubuntu import-ppa [Remove]
> - We suspect this is mostly unused?
>
>   * git ubunt lint[Remove]
> - We suspect this is mostly unused?
> - Has been useful in the past, might be candidate to return later
>
>   * git ubuntu build  [Remove]
> - It's a good idea, definitely a candidate to return one day, but
>   the code for this is cumbersome, has no test cases, and constrains
>   our internal refactoring.  There are numerous bugs reported about
>   it, and there are numerous alternate build approaches users can
>   use.
>
>   * git ubuntu review [Remove]
> - Another good idea, but was highly experimental and needs more
>   implementation work to be actually useful.
>
>
> What do you think?  If you have strong reasons to keep any of the
> above, please explain the justifications for consideration.
>
> Otherwise, in the next week or two I plan to start proposing MPs to drop
> the subcommands, with the goal of finishing their removal by the 1.0
> release.
>
> Post-1.0, new CLI subcommands will be introduced (and wanted old ones
> re-introduced), using some standard engineering processes.  E.g. a spec
> outlining the feature, a prototype done in a branch, and corresponding
> test cases.
>
> Bryce
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Proposed-migration and Triage report for Tuesday, March 31, 2020

[Dan Streetman]

On Tue, Mar 31, 2020 at 10:44 AM Lucas Kanashiro
 wrote:
>
> == Migration ==
> No packages in migration more than a day
>
> == Triage ==
> Bugs last updated on 2020-03-30 (Monday)
> Date range identified as: "Tuesday triage"
> Found 35 bugs
>
> Most of the bugs have been worked on by the team.
> Notes on remainder:
>
> LP: #1866385 - *+(New)  [kronosnet]  - [FFe][focal] kronosnet 
> need fixes from just released upstream version
> * Rafael requested a FFe, so now it is up to the release team
>
> LP: #1869649 - *+(New)  [gpsd]   - provide a skeleton for 
> /etc/device-hook
> * Triaged it as a wishlist bug for the next cycle
>
> LP: #1641238 - *(New)   [apache2]- as a reverse proxy, a 100 
> continue response is sent prematurely when a request contains expects: 
> 100-continue
> * A new issue was brought up by another user in the linked upstream bug, I 
> asked them to file a new Ubuntu bug if the issue is pertinent.
>
> LP: #1673255 - (New)[drbd-utils] - drbd udev rule with 
> multiple symlinks fails
> * I did nothing. It is not clear to me what to do here, the 
> sts-sponsor-volunteer tag was added. Please let me know if I need to do 
> something.

you can ignore it.

>
> ---
> Bugs tagged 'server-next' and not touched in 60 days
> Found 0 bugs
>
> ---
> Bugs in backlog and not touched in 180 days
> Found 0 bugs
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Merge Opportunities Report - 2019-12-09

[Dan Streetman]

On Mon, Dec 9, 2019 at 8:08 AM Bryce Harrington
 wrote:
>
> New Version in Debian Unstable
> --
> high  clamav0.102.1+dfsg-1   
> 0.101.4+dfsg-1ubuntu1
> high  nut   2.7.4-10 2.7.4-9ubuntu1
> high  vlan  2.0.52.0.4ubuntu1

vlan is only needed by ifupdown; since that's being removed from focal
(right?), vlan should probably be removed too

> low   autofs5.1.6-1  5.1.5-1ubuntu1
> low   ebtables  2.0.10.4+snapshot20181205-3  
> 2.0.10.4+snapshot20181205-1ubuntu1
> low   exim4 4.93~RC7-1   4.93~RC2-1ubuntu1
> low   freeipmi  1.6.4-3  1.6.3-1.1ubuntu2
> low   ipxe  1.0.0+git-20190125.36a4c85-1 
> 1.0.0+git-20190109.133f4c4-0ubuntu2
> low   libvirt   5.6.0-3  5.4.0-0ubuntu5
> low   lxc   1:3.1.0+really3.0.4-23.0.4-0ubuntu2
> low   net-snmp  5.8+dfsg-2   
> 5.7.3+dfsg-5ubuntu6
> low   nss   2:3.47.1-1   2:3.47-1ubuntu2
> low   php7.37.3.12-1 7.3.11-0ubuntu1
> low   qemu  1:4.1-3  
> 1:4.0+dfsg-0ubuntu10
> low   resource-agents   1:4.4.0-21:4.4.0-1ubuntu1
> low   runc  1.0.0~rc9+dfsg1-1
> 1.0.0~rc8+git20190923.3e425f80-0ubuntu1
> low   spice-protocol0.14.0-1 0.14.0-0ubuntu1
> low   xen   4.11.1+92-g6c33308a8d-2  4.9.2-0ubuntu2
>
>
> New Version in Experimental
> --
> low   dpdk  19.11-1   18.11.5-1
> low   freeradius3.0.20+dfsg-2 3.0.20+dfsg-1
> low   haproxy   2.1.0-2   2.0.10-1ubuntu1
> low   ipmctl02.00.00.3658+ds-1
> 02.00.00.3474+really01.00.00.3481-1
> low   ruby-defaults 1:2.5.7~0 1:2.5.2
>
>
> New Upstream not in Debian
> --
> high  logwatch  7.5.2/logwatch-7.5.2  7.5.0-2ubuntu1
> high  multipath-tools   0.8.2 0.7.9-3ubuntu6
> high  openipmi  2.0.272.0.27-0ubuntu1
> high  pacemaker 2.0.2 2.0.1-5ubuntu1
> (Low priority upstream releases skipped)
>
> high == Packages seeded for Ubuntu-Server
> low == Non-seeded packages Server team is subscribed to
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Triage/Migration report of the day

[Dan Streetman]

On Sat, Sep 28, 2019 at 1:58 PM Christian Ehrhardt
 wrote:
>
> On Fri, Sep 27, 2019 at 1:32 PM Dan Streetman
>  wrote:
> >
> > On Fri, Sep 27, 2019 at 1:58 AM Christian Ehrhardt
> >  wrote:
> > >
> > > Triage
> > > - 16 bugs to triage, interesting ones:
> > >  - Mostly activity from us => no-action items
> > >  - 1841936 is interesting as a planned no-change-rebuild against
> > > openssl1.1.1 not only
> > > picked up the expected TLSv1.3 but also increased DH key sizes.
> > >  - No new bugs added to our work queues (all that need action are
> > > already on our queues)
> > >
> > > Proposed migration
> > > - libvirt test is still broken by new systemd 243
> > >=> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879
> >
> > hasn't systemd been reverted back to 242 in Eoan?
>
> Yes, but we have to fix it in systemd and/or libvirtd for the 20.04 scope.
> So the bug still exists, it just doesn't matter for Eoan and current
> proposed migration anymore.

that was my only confusion, that it was listed as a work item for
current (Eoan) proposed migration.

>
> > > - No new issues since yesterday (again - thanks beta freeze)
> > >
> > > --
> > > Christian Ehrhardt
> > > Software Engineer, Ubuntu Server
> > > Canonical Ltd
> > >
> > > --
> > > ubuntu-server mailing list
> > > ubuntu-server@lists.ubuntu.com
> > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> > > More info: https://wiki.ubuntu.com/ServerTeam
>
>
>
> --
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Ubuntu Server Guide - VCS docs

[Dan Streetman]

On Fri, Sep 27, 2019 at 5:47 PM Joshua Powers  wrote:
>
> Hi Dan,
>
> On 9/27/19 2:41 PM, Dan Streetman wrote:
> > So, the "commercial" and "community" support links go to the same page
> > - UA support.  Is that intentional?
>
> Can you to the page you are referring to?

sorry, I was referring to the first "support" page; it has both:

"For more information see the Ubuntu Advantage1 page."
which links to http://www.ubuntu.com/management

"See the Ubuntu Support page for more information."
which links to http://www.ubuntu.com/support

the ubuntu.com/management just redirects to ubuntu.com/support, and
the /support page is just the UA landing page.  Maybe it meant to link
to https://ubuntu.com/support/community-support

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Ubuntu Server Guide - VCS docs

[Dan Streetman]

So, the "commercial" and "community" support links go to the same page
- UA support.  Is that intentional?

On Fri, Sep 27, 2019 at 4:35 PM Bryce Harrington
 wrote:
>
> On Thu, Sep 26, 2019 at 02:15:15PM -0700, Doug Smythies wrote:
> > On 2019.09.25 10:28 Bryce Harrington wrote:
> >
> > > - Removed the git basic usage directions
> >
> > Sorry to be late to the party.
> > I disagree with the deletion of the git page.
> >
> > On 2019:09:12 12:51 Bryce wrote:
> >
> > > Given the prevalence of git these days, ...
> > > and I think it is safe to assume most readers
> > > will know at least the minimal amount
> > > of git documented here.
> >
> > Disagree.
> > We want the serverguide to be useful to new and old server types.
> > It was my bible when I started.
> >
> Thanks for the feedback on the vcs changes, and appreciate the
> opportunity to further justify the changes.
>
> Years ago git was one of many vcs's, and many of us were new to it.
> These days it really is common knowledge, at least among technical
> folk.  I think it's safe to assume people already know it.
>
> Second, in terms of scope, the guide is more about services that run on
> ubuntu, and less about training for sysadmin skills.
>
> Third, given our low manpower I think the guide will be healthiest if
> we're selective in what we commit to maintain.  Just as pruning a tree
> helps it focus its energy for growth, pruning the guide will help ensure
> we're delivering unique value to our readers.
>
> > Also I never remember how to do those two git config lines,
> > and find them useful.
>
> Since these are global, you set them only once per user account.
> They're stored in your ~/.gitconfig, so you could just copy them along
> with your editor settings, .bash*, etc. when setting up a new account.
>
> The guide really doesn't address account management (maybe it should),
> but if it did I could see moving the git config settings there.
>
> Bryce
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Triage/Migration report of the day

[Dan Streetman]

On Fri, Sep 27, 2019 at 1:58 AM Christian Ehrhardt
 wrote:
>
> Triage
> - 16 bugs to triage, interesting ones:
>  - Mostly activity from us => no-action items
>  - 1841936 is interesting as a planned no-change-rebuild against
> openssl1.1.1 not only
> picked up the expected TLSv1.3 but also increased DH key sizes.
>  - No new bugs added to our work queues (all that need action are
> already on our queues)
>
> Proposed migration
> - libvirt test is still broken by new systemd 243
>=> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879

hasn't systemd been reverted back to 242 in Eoan?

> - No new issues since yesterday (again - thanks beta freeze)
>
> --
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: UA for Apps process docs

[Dan Streetman]

On Fri, Sep 20, 2019 at 5:28 AM Bryce Harrington
 wrote:
>
> Hi Josh,
>
> Lucas and I have a draft completed for your review of a doc defining the
> processes for handling UA for Apps projects, from effort estimation, to
> package development, to review and upload for the security team.

Hi Bryce, Josh,

I like the doc, but I'm concerned that it doesn't mention Sustaining
Engineering anywhere in the doc, nor are we involved in reviewing or
approving new UA for Apps packages during or after the process.  Can
you please include us in the process since we're the team supporting
these packages?

>
> There are a couple of ?'s sprinkled in for latter steps we're not clear
> on.  As we progress to the finish line on Kafka we should update with
> proper links/teamnames/etc.
>
> https://docs.google.com/document/d/1SAC1qgrxLiD7qdYfip7qVFb7QZk5M7Ik0o7qVvJJV-o
>
> Bryce
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Where is network configuration "hidden" on Ubuntu 16.04?

[Dan Streetman]

On Fri, Oct 5, 2018 at 3:31 PM Leroy Tennison  wrote:
>
> I have two identical hardware devices, call them "2" (running Ubuntu 16.04.5 
> x86_64) and "5" (running Ubuntu 16.04.3 i686).  On "2" a couple of NICs 
> failed so I replaced the chassis by doing a hard drive swap between "2" and 
> "5".  I updated /etc/udev/rules.d/70-persistent-net.rules on the swapped hard 
> drive and everything worked on "2" with the swapped chassis (this was the 
> subject of my last post to this list).
>
> The chassis of "2" (the original "2") has enough good NICs to use for testing 
> a planned keepalived enhancement but has the unit "5" hard drive.  I updated 
> /etc/network/* (recursive) to have the configuration from "2" but, upon boot, 
> the device keeps getting it's old IP address for eth3 and eth9 (the unit "5" 
> IP addresses).  It gets the correct IP address for eth0, no IP address for 
> eth5, eth6 or eth8 (all of which are configured as static in the interfaces.d 
> file).  eth9 is the more unusual IP address so I did a recursive grep of /etc 
> for it's first two octets and found nothing.  In fact /etc/rc.local has the 
> default contents and neither /etc/network/interfaces or the file in 
> /etc/network/interfaces.d even configures eth9.

It's unclear what configuration exactly you're using for each
interface, but if you're using dhcp then the dhcp server is likely
giving the same IP address to the nic mac address, so it would follow
the hardware (not your configuration).

If you're not using dhcp, then I suggest you post exactly your config
and what you want your nics to be configured as, and people can help
you adjust your files.

>
> Where else can I look for the remnnts of the "5" configuration which are 
> being applied at boot and preventing parts of the file-based configuration 
> from working?  I even decompressed a copy of initrd.img... and found nothing.
>
>
> Leroy Tennison
> Network Information/Cyber Security Specialist
> E: le...@datavoiceint.com
> 2220 Bush Dr
> McKinney, Texas
> 75070
> www.datavoiceint.com
> TThis message has been sent on behalf
> of a company that is part of the Harris Operating Group of
> Constellation Software Inc. These companies are listed
> here
> .
> If you prefer not to be contacted by Harris
> Operating Group
> please notify us
> .
> This message is intended exclusively for the
> individual or entity to which it is addressed. This communication
> may contain information that is proprietary, privileged or
> confidential or otherwise legally exempt from disclosure. If you are
> not the named addressee, you are not authorized to read, print,
> retain, copy or disseminate this message or any part of it. If you
> have received this message in error, please notify the sender
> immediately by e-mail and delete all copies of the
> message.
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Where is network configuration "hidden" on Ubuntu 16.04?

[Dan Streetman]

On Sun, Oct 7, 2018 at 9:16 PM Mark Constable  wrote:
>
> On 08/10/18 10:57, Little Girl wrote:
> >> Where else can I look for the remnnts of the "5" configuration which
> >> are being applied at boot and preventing parts of the file-based
> >> configuration from working?  I even decompressed a copy of
> >> initrd.img... and found nothing.
> > [...]
> > If nothing else, hopefully this message will draw attention to your
> > original message and maybe someone with a more appropriate solution
> > will join in.
>
> I find this alias useful to search or query various config settings...
>
> alias q='find -type f -print0 | xargs -0 grep '
>
> then "cd /etc" (most often) and ie; "q 12.34.56.78" the IP being set

you can do that a lot easier with just:

$ grep -r 12.34.56.78 /etc

> from the previous 5 machine on the 2 machine. Change the IP for any
> unique info related to the other machine and you may locate the
> remnants of old config files. /var/lib/ is another place to look.
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Testing for lp #1701023

[Dan Streetman]

Hi all,

I've fixed a regression in how ifupdown handles vlans in lp 1701023,
and would like to ask for anyone with ifupdown configurations using
vlans to give it a test.  The patched ifupdown and vlan pkgs are in
-proposed for t/x/a/b, so if you upgrade to them and notice any issues
with your network configuration, at boot, or ifup, or interface
hotplug, please let me know and/or add a comment to the bug.  I'll
leave them in -proposed for a bit longer than usual to try to get more
testing in.

https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1701023

Thanks!

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Timeout for Ubuntu Server ISO bootsplash

[Dan Streetman]

On Thu, Nov 23, 2017 at 10:01 AM, Mathieu Trudel-Lapierre
 wrote:
> On Thu, Nov 23, 2017 at 4:55 AM, Christian Ehrhardt
>  wrote:
>> On Thu, Nov 23, 2017 at 1:02 AM, Mathieu Trudel-Lapierre
>>  wrote:
>>> Hi,
>>>
>>> I'm revising some of the bootloader logic for the ISO images. Ubuntu Server
>>> currently seems to be one of the things that just wait indefinitely at the
>>> bootloader (grub or isolinux, depending on what/where you are booting).
>>>
>>> Is anyone against putting a 5 second timeout in the bootloader, such that
>>> the system carries on to starting the installer automatically?
>>
>> Hi Mathieu,
>> not against the change, but I want to check on a Detail.
>> Is it correct that today it does:
>> A1. boot into bootloader
>> A2. wait forever on users choice
>>
>> And you suggest:
>> B1. boot into bootloader
>> B2. wait 5 sec for users to choose anything special
>> B3. go into the installer (and wait there on the user)
>>
>> If a user can influcence/choose anything in A2 that they can not do
>> anymore in B3 (e.g. special kernel boot options I'd think).
>> Then we should make the timeout on server a bit more than 5 seconds IMHO.
>>
>
> There is, but it's a matter of setting custom kernel options
> (disabling ACPI, for instance) or adding command-line parameters such
> as for preseeding (which obviously needs to happen before the
> installer starts).
>
>> The reason I point this out is the (unfortunately usual) combination
>> of slow remote consoles plus 5-10 minute server initialization times.
>> I'm afraid of the admin sitting on a remote server control on a crappy
>> connection for 10 minutes and hitting "oh crap B2 just passed faster
>> than I could see it".
>
> It's always a possibility, but putting the timeout too high is also
> just waiting for no reason. We should also expect users who preseed or
> install many systems to do so via the network or other means; and the
> idea behind this is to have one common timeout value everywhere rather
> than having many different images behave differently.
>
>> Not sure what the right value would be, but 30 seconds seem safer to
>> me and it would still eventually reach B3.
>
> Does it really need to be 30 seconds though? If you're looking for
> things to be more or less automatic, and if you preseed via the initrd
> (which you may do, and we do for automatic testing AFAIK), then you're
> sitting there waiting for 30 seconds when you could have waited for
> much less.

if it's automatic via preseeding, why would anyone be sitting there
waiting for it?

>
> Remember, any keypress will cancel the timeout, you don't need to have
> done everything within that window.
>
> On trans-oceanic links, 5 seconds is maybe cutting it a bit short, but
> I wouldn't make it past 15.

IMHO the problem isn't only high RTT (but that certainly makes it much
worse), many times the serial console refresh is very slow (especially
using the IPMI api to the server BMC - which sometimes disconnects
during a reboot but doesn't let you know), so by the time you see the
grub menu starting to draw, it's too late.  15 seconds probably is
enough time if you're staring at the screen ready to press a key
immediately, but if your server takes a few minutes (or worse) to
(re)boot, it gets hard to stare at the screen waiting to press a key
fast enough.

Personally, for a server installer, I think 15 seconds is the minimum,
not maximum.

>
> --
>
> Mathieu Trudel-Lapierre 
> Freenode: cyphermox, Jabber: mathieu...@gmail.com
> 4096R/65B58DA1 818A D123 0992 275B 23C2  CF89 C67B B4D6 65B5 8DA1
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: [Cloud-init] Release of cloud-init 0.7.7

[Dan Watkins]

On 10/08/16 08:16, Scott Moser wrote:
> Yesterday I tagged and uploaded a release of cloud-init 0.7.7 "been to long".
> Source tarball is available at
>  https://launchpad.net/cloud-init/trunk/0.7.7

\o/

> The release marks the first release of cloud-init in over a year, and as such
> there are many changes and improvements.  There were 38 contributors to the
> release.

\o/ \o/

> Additionally, we would like to announce that cloud-init has moved its revision
> control from bzr to git.  The upstream master branch can be viewed via
> launchpad's web interface at
>   https://code.launchpad.net/cloud-init
> And cloned with:
>   git clone https://git.launchpad.net/cloud-init

\o/ \o/ \o/


Thanks Scott!



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

[Bug 1194074] Re: Default index.html blindly overwritten

[Dan]

I'd like to add to this, I installed nginx on my Raspberry Pi and was
using it on my internal network. I'm not an administrator, just a
tinkerer who has no knowledge that the default www share should not be
used. Because of this i've lost my index.html that i was using.

I'd assume there are a lot of users like me who are not using nginx in a
production environment, and as such i consider this to be a bug. A
pretty bad bug that can wipe out someones hard work for absolutely no
reason. Why even overwrite the standard index when you upgrade? It seems
even more ridiculous than expecting everyone to know not to use the
default www.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1194074

Title:
  Default index.html blindly overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1194074/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

[Dan Watkins]

I have tested all of the above cases with the cloud-init from -proposed
and it behaved as expected.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Dan Watkins]

On a xenial system, when enabling xenial-proposed and running "apt-get
install squid", I get the below error. Note that I have 'DAEMON=nope' in
/etc/default/squid3 to stop squid3 from starting (because it's only
installed for squid-deb-proxy).

Setting up squid (3.5.12-1ubuntu1) ...
Removing obsolete conffile /etc/squid3/msntauth.conf ...
Removing obsolete conffile /etc/init/squid3.conf ...
Failed to stop squid3.service: Unit squid3.service not loaded.
invoke-rc.d: initscript squid3, action "stop" failed.
dpkg: error processing package squid (--configure):
 subprocess installed post-installation script returned error exit status 5
Processing triggers for systemd (229-2ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for ufw (0.35-0ubuntu1) ...
Errors were encountered while processing:
 squid
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1553158] Re: [SRU] Add cloud-init data source for BigStep

[Dan Watkins]

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1553158

Title:
  [SRU] Add cloud-init data source for BigStep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1553158/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1553158] [NEW] [SRU] Add cloud-init data source for BigStep

[Dan Watkins]

Public bug reported:

[Impact]

Users on older versions of Ubuntu cannot use the BigStep cloud.

[Test Case]

1) Launch an Ubuntu image with the fixed version of cloud-init in the BigStep 
cloud
2) Successfully SSH in to it

[Regression Potential]

Low; this adds a new file which is only read on instances that are
explicitly configured to read from the BigStep data source.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1553158

Title:
  [SRU] Add cloud-init data source for BigStep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1553158/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Invalid

** Changed in: cloud-init (Ubuntu)
 Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)

** Changed in: cloud-init (Ubuntu Vivid)
   Status: New => Invalid

** Summary changed:

- Fix UUID endianness patch breaks cloud-init on Azure
+ [SRU] Fix UUID endianness patch breaks cloud-init on Azure

** Summary changed:

- [SRU] Fix UUID endianness patch breaks cloud-init on Azure
+ [SRU] Handle changing UUID endian-ness on Azure in cloud-init

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

Attached is a debdiff for trusty (the only affected version).

** Patch added: "lp1551419.debdiff"
   
https://bugs.launchpad.net/ubuntu/vivid/+source/cloud-init/+bug/1551419/+attachment/4587505/+files/lp1551419.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

** Description changed:

  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.
  
  This recent kernel patch in the Ubuntu kernel incorrectly modifies the
  endianness for some SMBIOS fields, which has the effect causing cloud-
  init to think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e
  
  cloud-init needs to consider both the reported UUID and the "first three
  fields endian-reversed" UUID as the same, so that users shifting between
  unaffected kernels and affected kernels, or affected kernels and fixed
  kernels do not see their instances reprovisioned.
  
  [Impact]
  
  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose access
  to their VM.
  
  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.
  
  [Test Case]
  
  Failure:
  
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.
  
  Success (upgrade from not broken->broken):
  
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
+ 5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
+ 6) Reboot again.
+ 7) Observe that the instance ID has not changed.
  
  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  
  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  
  [Regression Potential]
  
  The change is limited to the Azure data source.  It affects how instance
  IDs are determined, but the change does so in a limited way.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

** Description changed:

  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.
  
- This recent kernel patch in the Ubuntu kernel corrects the endianness
- for some SMBIOS fields, but also has the effect causing cloud-init to
- think that the system-uuid has changed:
+ This recent kernel patch in the Ubuntu kernel incorrectly modifies the
+ endianness for some SMBIOS fields, which has the effect causing cloud-
+ init to think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e
  
- The impact is that cloud-init attempts to reprovision the VM, often
- causing the customer to lose access to their VM.
+ cloud-init needs to consider both the reported UUID and the "first three
+ fields endian-reversed" UUID as the same, so that users shifting between
+ unaffected kernels and affected kernels, or affected kernels and fixed
+ kernels do not see their instances reprovisioned.
+ 
+ [Impact]
+ 
+ The impact is that cloud-init attempts to reprovision VMs when they
+ reboot to use the new kernel, often causing the customer to lose access
+ to their VM.
+ 
+ Once the kernel is fixed, rebooting from an affected kernel to the new
+ kernel will have the same effect.
+ 
+ [Test Case]
+ 
+ Failure:
+ 
+ 1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
+ 2) Upgrade the kernel and reboot.
+ 3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.
+ 
+ Success:
+ 
+ 1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
+ 2) Install the new version of cloud-init.
+ 3) Upgrade the kernel and reboot.
+ 4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
+ 
+ [Regression Potential]
+ 
+ The change is limited to the Azure data source.  It affects how instance
+ IDs are determined, but the change does so in a limited way.

** Description changed:

  On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
  unique ID for a cloud instance.  If this ID ever changes, then cloud-
  init will attempt to reprovision the VM.
  
  This recent kernel patch in the Ubuntu kernel incorrectly modifies the
  endianness for some SMBIOS fields, which has the effect causing cloud-
  init to think that the system-uuid has changed:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e
  
  cloud-init needs to consider both the reported UUID and the "first three
  fields endian-reversed" UUID as the same, so that users shifting between
  unaffected kernels and affected kernels, or affected kernels and fixed
  kernels do not see their instances reprovisioned.
  
  [Impact]
  
  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose access
  to their VM.
  
  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.
  
  [Test Case]
  
  Failure:
  
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.
  
- Success:
+ Success (upgrade from not broken->broken):
  
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  
+ Success (upgrade from broken->fixed):
+ 1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
+ 2) Install the new version of cloud-init.
+ 3) Upgrade to the fixed kernel (once it is available) and reboot.
+ 4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
+ 
+ Success (upgrade from not broken->fixed):
+ 1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
+ 2) Install the new version of cloud-init.
+ 3) Upgrade to the fixed kernel (once it is available) and reboot.
+ 4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
+ 
  [Regression 

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

** Changed in: cloud-init (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

So in addition to a kernel fix, we will first need to release a cloud-
init that will handle the endian-ness of instance IDs changing
underneath it.

This is because the kernel is already out in the wild, so we will have
some instances that have booted with the new UUID and the kernel fix
will also trigger the behaviour seen in this bug.

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

OK, I'm shifting this back to linux, because I think that the commit
that was backported is fixing a problem in a commit that _wasn't_
backported, therefore causing the issue. Here are the details:

In 95be58df7 [0], support for SMBIOS 3 was added, which introduces a
third version field (i.e. 3.2.1 vs. 2.9); as a result, dmi_ver is
converted from a u16 and a u32, and when it's read in, it's left-shifted
8 bits. (i.e. version 2.6 goes from 0x0206 to 0x020600). The endian-ness
checks are updated to match the shifted number (i.e. if SMBIOS version
>= 0x020600, little-endian, otherwise big-endian). This patch has NOT
been backported to trusty.

In ff4319dc7 [1], it was identified that this left-shifting happened in
the wrong place, and so it was moved to happen in a different place.
Simple enough. However, this patch HAS been backported to trusty,
despite the fact it is fixing behaviour that wasn't backported.

Crucially, though, the commit containing the backport [2] introduced the
left-shifting _without_ changing the endian-ness checks. This means that
the trusty kernel _always_ detects the SMBIOS version as being greater
than 2.6, which means on older versions of SMBIOS (like the one in use
on Azure), it returns the version with incorrect endian-ness.


[0] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=95be58df74a5b21e5a78e45fddb2fd59112524c5
[1] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/firmware/dmi_scan.c?id=ff4319dc7cd58c92b389960e375038335d157a60
[2] 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

** Package changed: cloud-init (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Dan Watkins]

OK, so I've done a bit of digging.

As of SMBIOS 2.6 (released in 2008), the first three fields of the UUID
are well-defined as being encoded in little-endian. Before that, they
could be encoded in "network byte order" (i.e. big-endian) if people
felt like it.

Presumably enough people did feel like it, as dmidecode specifically has
different code paths for pre-2.6 and post-2.6 SMBIOS versions; it will
decode pre-2.6 UUIDs as big-endian and post-2.6 UUIDs as little-endian.
(The comment in the dmidecode source code at [0] explains this pretty
well.)

And, you've guessed it, Azure reports a pre-2.6 version of SMBIOS. (To
be precise, 2.3, which was released in _1999_; Azure is old skool cool).
This explains the difference between the kernel-reported UUID (always
little-endian) and the dmidecode-reported UUID (big-endian on Azure, but
little-endian on most modern systems).

[0] https://github.com/mirror/dmidecode/blob/master/dmidecode.c#L415

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522422] Re: PHP5 branch and PHP7 branch

[Dan Blows]

For what it's worth, I would really like to see PHP7 in Ubuntu 16.04. Is
there anything I could do to help it to happen?

I wouldn't exactly call PHP7 a revolution - it's faster, and it has some
nice features (particularly valuable for me are return type hinting and
scalar type hinting). I've upgraded a few applications from PHP5.3 to
PHP7.0 without any changes to the code. I did have to change
configuration like where the PHP 7.0 FPM is located, but that was it,
and the speed improvement was noticeable.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1522422

Title:
  PHP5 branch and PHP7 branch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1522422/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

[Dan Watkins]

** Changed in: cloud-init
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1500768] Re: python3.4.3 SRU break requests

[Dan Watkins]

** Also affects: python-virtualenv (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-urllib3 in Ubuntu.
https://bugs.launchpad.net/bugs/1500768

Title:
  python3.4.3 SRU break requests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1500768/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1436417] Re: Update cloud-init to use SmartOS v2 metadata format

[Dan Watkins]

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1436417

Title:
  Update cloud-init to use SmartOS v2 metadata format

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1403617] Re: gce datasource does not handle instance ssh keys

[Dan Watkins]

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1403617

Title:
  gce datasource does not handle instance ssh keys

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Dan Watkins]

** Changed in: docker.io (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1311463] Re: disk-setup unable to partition disks

[Dan Watkins]

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1311463

Title:
  disk-setup unable to partition disks

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1398997] Re: cloud-init does not have the SmartOS data source as a configuration option

[Dan Watkins]

** Changed in: cloud-init
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1398997

Title:
  cloud-init does not have the SmartOS data source as a configuration
  option

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1464253] Re: [SRU] CloudStack data source will always set password to "HTTP/1.0 200 OK" on CloudStack 4.5.1 and later

[Dan Watkins]

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1464253

Title:
  [SRU] CloudStack data source will always set password to "HTTP/1.0 200
  OK" on CloudStack 4.5.1 and later

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

[Dan Watkins]

** Branch linked: lp:~daniel-thewatkins/cloud-init/lp1506187

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

[Dan Watkins]

** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-init
   Status: New => In Progress

** Changed in: cloud-init
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Xenial)
 Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: Azure: cloud-init should use VM unique ID

[Dan Watkins]

Hi Steve,

Thanks for letting us know! Before I get started, can you confirm that
we can safely remove all retrieval of instance ID from SharedConfig.xml?
(That is to say, are there any Azure platforms etc. where we might not
have the DMI value available?)


Thanks,

Dan

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187

Title:
  Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Dan Watkins]

For avoidance of doubt, this problem was caused by the actions taken to
remedy bug 1500768. Workarounds to get an instance unstuck can be found
there.


Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Dan Watkins]

Hi Mark, all,

At some point, Python 3.4.3 was released to the trusty archive. However,
a (serious) regression was found, and it was removed from the archive.
This image was built after the release, but before the removal, which
means it has ended up in a state that apt-get doesn't understand.

The fix for this is simply to release a new image; I have pinged Tianon,
the awesome community member who handles the Docker Ubuntu images, on
IRC (and subscribed him to this bug) to make that happen. He's based on
the West Coast, so the earliest we'll see this happen is in a few hours.

Apologies for the broken state that things ended up in; we strive to
produce images of the highest quality, and don't like it when we fall
short of that.


Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1505164] Re: Ubuntu Docker images incorrectly include packages from trusty-proposed

[Dan Watkins]

** Changed in: docker.io (Ubuntu)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: docker.io (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1505164

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1387244] Re: Increasing number of InstancePCIRequests.get_by_instance_uuid RPC calls during compute host auditing

[Dan Smith]

** Changed in: nova
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1387244

Title:
  Increasing number of InstancePCIRequests.get_by_instance_uuid RPC
  calls during compute host auditing

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1387244/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470890] Re: [SRU] cc_apt_configure does not understand regions

[Dan Watkins]

** Changed in: cloud-init
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470890

Title:
  [SRU] cc_apt_configure does not understand regions

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470880] Re: [SRU] GCE datasource reports availability zones incorrectly

[Dan Watkins]

** Changed in: cloud-init
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470880

Title:
  [SRU] GCE datasource reports availability zones incorrectly

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1492705] [NEW] open-vm-dkms 2011.12.20-562307-0ubuntu1.1: open-vm-tools kernel module failed to build

[Dan Rau]

Public bug reported:

open-vm-dkms 2011.12.20-562307-0ubuntu1.1: open-vm-tools kernel module
failed to build

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: open-vm-dkms 2011.12.20-562307-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-62.102~precise1-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.9
Architecture: amd64
DKMSKernelVersion: 3.13.0-63-generic
Date: Sun Sep  6 12:09:48 2015
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 2011.12.20-562307-0ubuntu1.1
SourcePackage: open-vm-tools
Title: open-vm-dkms 2011.12.20-562307-0ubuntu1.1: open-vm-tools kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: open-vm-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check precise

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1492705

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1.1: open-vm-tools kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1492705/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1492267] [NEW] Python 3 supported upstream but not packaged

[Dan Watkins]

Public bug reported:

It would be good to be able to use taskflow in Python 3 projects. This
is, presumably, also required for porting stuff that already uses
taskflow to Python 3.

** Affects: python-taskflow (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-taskflow in Ubuntu.
https://bugs.launchpad.net/bugs/1492267

Title:
  Python 3 supported upstream but not packaged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-taskflow/+bug/1492267/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1492267] Re: Python 3 supported upstream but not packaged

[Dan Watkins]

** Bug watch added: Debian Bug tracker #798018
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798018

** Also affects: python-taskflow (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798018
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-taskflow in Ubuntu.
https://bugs.launchpad.net/bugs/1492267

Title:
  Python 3 supported upstream but not packaged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-taskflow/+bug/1492267/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

I've refreshed the patches for trusty and vivid to include the changes
that hit -proposed earlier today. precise-proposed didn't have a change,
so that debdiff remains unchanged.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Attachment removed: "trusty.debdiff"
   
https://bugs.launchpad.net/cloud-init/+bug/1490796/+attachment/4456141/+files/trusty.debdiff

** Attachment removed: "vivid.debdiff"
   
https://bugs.launchpad.net/cloud-init/+bug/1490796/+attachment/4456142/+files/vivid.debdiff

** Patch added: "New trusty debdiff, including the changes already in 
-proposed."
   
https://bugs.launchpad.net/cloud-init/+bug/1490796/+attachment/4456217/+files/trusty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Patch added: "New vivid debdiff, including the changes already in -proposed."
   
https://bugs.launchpad.net/cloud-init/+bug/1490796/+attachment/4456218/+files/vivid.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1491532] [NEW] ssh-keygen invocation difficult to copy-paste

[Dan Watkins]

Public bug reported:

When connecting to a host whose host keys have changed (e.g. when
connecting to a new instance in a cloud), something like the below
message is displayed. The ssh-keygen invocation is harder to copy-paste
than it could be if it were on a separate line.

@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
.
Please contact your system administrator.
Add correct host key in /home//.ssh/known_hosts to get rid of this 
message.
Offending ECDSA key in /home//.ssh/known_hosts:408
  remove with: ssh-keygen -f "/home//.ssh/known_hosts" -R 
ECDSA host key for  has changed and you have requested strict 
checking.
Host key verification failed.

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1491532

Title:
  ssh-keygen invocation difficult to copy-paste

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1491532/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Description changed:

- Ubuntu 14.04.3 (20150805) on Azure with cloud-init package
- 0.7.5-0ubuntu1.8.
+ 
+ [Impact]
+ Sometimes when rebooting an instance in Azure, a different ephemeral disk 
will be presented. Azure ephemeral disks are presented as NTFS disks, but we 
reformat them to ext4.  With the last cloud-init upload, we shifted to using 
/dev/disk symlinks to mount these disks (in case they are not presented as the 
same physical device).  Unfortunately, the code that determines if we have a 
new ephemeral disk was not updated to handle symlinks, so never detects a new 
disk.
+ 
+ [Test Case]
+ 1) Boot an Azure instance and install the new cloud-init.
+ 2) Change the size of the instance using the Azure web interface (as this 
near-guarantees that the ephemeral disk will be replaced with a new one). This 
will reboot the instance.
+ 3) Once the instance is rebooted, SSH in and confirm that:
+  a) An ext4 ephemeral disk is mounted at /mnt, and
+  b) cloud-init.log indicates that a fabric formatted ephemeral disk was found 
on this boot.
+ 
+ [Regression Potential]
+ Limited; two LOCs change, to dereference symlinks instead of using paths 
verbatim.
+ 
+ [Original Report]
+ Ubuntu 14.04.3 (20150805) on Azure with cloud-init package 0.7.5-0ubuntu1.8.
  
  On Azure cloud-init prepares the ephemeral device as ext4 for the first
  boot.  However, if the VM is ever moved to another Host for any reason,
  then a new ephemeral disk might be provided to the VM.  This ephemeral
  disk is NTFS formatted, so for subsequent reboots cloud-init must detect
  and reformat the new disk as ext4.  However, with cloud-init
  0.7.5-0ubuntu1.8 subsequent boots may result in fuse mounted NTFS file
  system.
  
  This issue occurred in earlier versions of cloud-init, but was fixed
  with bug 1292648 (https://bugs.launchpad.net/ubuntu/+source/cloud-
  init/+bug/1292648).  So this appears to be a regression.
  
  Repro:
-   - Create an Ubuntu 14.04.3 VM on Azure
-   - Resize the VM to a larger size (this typically moves the VM)
-   - Log in and run 'blkid' to show an ntfs formatted ephemeral disk:
+   - Create an Ubuntu 14.04.3 VM on Azure
+   - Resize the VM to a larger size (this typically moves the VM)
+   - Log in and run 'blkid' to show an ntfs formatted ephemeral disk:
  
- # blkid
- /dev/sdb1: LABEL="Temporary Storage" UUID="A43C43DD3C43A95E" TYPE="ntfs"
- 
+ # blkid
+ /dev/sdb1: LABEL="Temporary Storage" UUID="A43C43DD3C43A95E" TYPE="ntfs"
  
  Expected results:
-   - After resizing the ephemeral disk should be formatted as ext4.
+   - After resizing the ephemeral disk should be formatted as ext4.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Summary changed:

- cloud-init must check/format Azure ephemeral disks each boot
+ [SRU] cloud-init must check/format Azure ephemeral disks each boot

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Summary changed:

- cloud-init must check/format Azure empheral disks each boot
+ cloud-init must check/format Azure ephemeral disks each boot

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  cloud-init must check/format Azure ephemeral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Patch added: "vivid.debdiff"
   
https://bugs.launchpad.net/cloud-init/+bug/1490796/+attachment/4456142/+files/vivid.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Patch added: "precise.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+attachment/4456140/+files/precise.debdiff

** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-init
   Status: New => Fix Committed

** Changed in: cloud-init
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Dan Watkins]

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/cloud-init/+bug/1490796/+attachment/4456141/+files/trusty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: cloud-init must check/format Azure empheral disks each boot

[Dan Watkins]

I've worked this out: we check if a disk is mounted (in order to unmount
it) using the /dev/disk symlink, but it's the dereferenced device that
appears in the mount table. If we dereference the symlink before
checking the mount table, this goes away.

This is what the attached branch does.

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~daniel-thewatkins/cloud-init/fix_mount_cb_symlink

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  cloud-init must check/format Azure empheral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: cloud-init must check/format Azure empheral disks each boot

[Dan Watkins]

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  cloud-init must check/format Azure empheral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1411582] Re: [SRU] Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

Confirmed fixed on trusty; the vivid image build failed for unrelated
reasons, which I'm addressing.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  [SRU] Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: [SRU] Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

Verified on vivid; marked as verification-done.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  [SRU] Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: [SRU] Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

Confirmed fixed on precise; trusty and vivid images are still building
(or queued for building).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  [SRU] Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470890] Re: [SRU] cc_apt_configure does not understand regions

[Dan Watkins]

Confirmed fixed in precise; trusty and vivid images building for
validation.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470890

Title:
  [SRU] cc_apt_configure does not understand regions

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470880] Re: [SRU] GCE datasource reports availability zones incorrectly

[Dan Watkins]

Confirmed fixed in precise; trusty and vivid images building for
validation.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470880

Title:
  [SRU] GCE datasource reports availability zones incorrectly

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470890] Re: [SRU] cc_apt_configure does not understand regions

[Dan Watkins]

Confirmed fixed in vivid; trusty image still building for validation.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470890

Title:
  [SRU] cc_apt_configure does not understand regions

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470880] Re: [SRU] GCE datasource reports availability zones incorrectly

[Dan Watkins]

Confirmed fixed in vivid; trusty image still building for validation.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470880

Title:
  [SRU] GCE datasource reports availability zones incorrectly

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470880] Re: [SRU] GCE datasource reports availability zones incorrectly

[Dan Watkins]

Verified on trusty; marked as verification-done.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470880

Title:
  [SRU] GCE datasource reports availability zones incorrectly

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470890] Re: [SRU] cc_apt_configure does not understand regions

[Dan Watkins]

Verified on trusty; marked as verification-done.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1470890

Title:
  [SRU] cc_apt_configure does not understand regions

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1475215] Re: [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3

[Dan Watkins]

** Changed in: cloud-init
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1475215

Title:
  [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: [SRU] Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

** Summary changed:

- Azure data source should auto-detect ephemeral disk location
+ [SRU] Azure data source should auto-detect ephemeral disk location

** Description changed:

- Currently we assume it will be /dev/sdb, but this may change. There is
- an example of how to handle this in the Azure Linux agent.
+ [Impact]
+ The Azure ephemeral disk will not necessarily remain at the same /dev/sd* 
location between reboots.  This means the drive may not be persistently mounted 
between reboots. 
+ 
+ [Test Case]
+ 1) Boot an Azure instance with a cloud-init including this fix.
+ 2) Ensure that the ephemeral disk is mounted at /mnt and formatted as ext4
+ 3) Ensure that /etc/fstab refers to a /dev/disk/... symlink, rather than a 
/dev/sd* device.
+ 
+ [Regression Potential]
+ We now use a udev rule to discover the location of the disk; we have been 
assured by Microsoft that this rule will always work, so regression potential 
is minimal.
+ 
+ [Original Report]
+ Currently we assume it will be /dev/sdb, but this may change. There is an 
example of how to handle this in the Azure Linux agent.
  
  To quote stevez in a comment on bug 1410835:
  
  Device names are not persistent in Linux and could change, so it is not
  guaranteed that the ephemeral disk will be called /dev/sdb. Ideally this
  should be auto-detected in cloud-init at runtime (for example, see
  DeviceForIdePort() in the Azure Linux agent).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  [SRU] Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

utopic is EOL.

** Changed in: cloud-init (Ubuntu Precise)
 Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Precise)
   Status: New = In Progress

** Changed in: cloud-init (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: cloud-init (Ubuntu Trusty)
 Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Vivid)
   Status: New = In Progress

** Changed in: cloud-init (Ubuntu Vivid)
 Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1381776] Re: cloud init depends on python-serial but does not declare it

[Dan Watkins]

This change wasn't needed in trusty, but as it doesn't actually change
how the package behaves we will fix it in the next SRU (which will be
coming hot on the heels of the current version in -proposed). Marked as
verification-done.

** Tags removed: verification-done-precise verification-needed
** Tags added: verification-done

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1381776

Title:
  cloud init depends on python-serial but does not declare it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1381776/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1464253] Re: [SRU] CloudStack data source will always set password to HTTP/1.0 200 OK on CloudStack 4.5.1 and later

[Dan Watkins]

I have verified that we have not broken password on pre 4.5 versions of
CloudStack.

I haven't been able to confirm that this is fixed on 4.5+, because we
haven't been able to find such a test environment. It certainly won't
have regressed (as it was already broken), so I'm marking this as
verification-done.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1464253

Title:
  [SRU] CloudStack data source will always set password to HTTP/1.0 200
  OK on CloudStack 4.5.1 and later

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456684] Re: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones

[Dan Watkins]

** Changed in: cloud-init
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1456684

Title:
  [SRU] cloud-init does not know central (eu-central-1) is a direction
  for ec2 zones

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1422388] Re: Fetch passwords from CloudStack virtual router

[Dan Watkins]

Hi Carlos,

As I mentioned on bug 1089989, there are CloudStack environments that
the current precise CloudStack data source does work against. So this
fix was validated on one such environment, where it worked fine. :)


Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1422388

Title:
  Fetch passwords from CloudStack virtual router

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1479610] Re: [SRU] walinuxagent regression on dhcp configuration

[Dan Watkins]

I have followed the test steps and confirmed that sudo /bin/true does
not complain about hostname resolution.

** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1479610

Title:
  [SRU] walinuxagent regression on dhcp configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1479610/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1475215] Re: [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3

[Dan Watkins]

I have confirmed that this fix works by mounting an existing vivid
drive, installing the proposed cloud-init via chroot and then booting
that instance. The instance came up successfully.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1475215

Title:
  [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456684] Re: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones

[Dan Watkins]

Tested the following versions:

vivid: 0.7.7~bzr1091-0ubuntu4
trusty: 0.7.5-0ubuntu1.7
precise: 0.6.3-0ubuntu1.18

and have confirmed that this is fixed in all of those.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1456684

Title:
  [SRU] cloud-init does not know central (eu-central-1) is a direction
  for ec2 zones

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1356855] Re: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash

[Dan Watkins]

Hi Kevin,

If you're seeing problems on precise, could you file a separate bug
detailing your issues? The code path which this bug fixes doesn't exist
in precise, so you must be seeing another issue. :)


Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1356855

Title:
  Cloud-init 0.7.5 Failed to get cloudstack user-data because of
  trailing slash

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456684] Re: does not know central (eu-central-1) is a direction for ec2 zones

[Dan Watkins]

** Description changed:

  cloud-init's code that tries to determine if it is in a ec2 region is
  simply unaware of the 'central' direction.
  
- --- /usr/lib/python2.7/dist-packages/cloudinit/distros/__init__.py.dist   
2015-05-19 12:47:04.956343999 +
- +++ /usr/lib/python2.7/dist-packages/cloudinit/distros/__init__.py
2015-05-19 12:47:09.718723998 +
- @@ -535,7 +535,7 @@
-  mirror_info = {}
-  
-  ec2_az_re = (^[a-z][a-z]-(%s)-[1-9][0-9]*[a-z]$ %
- -north|northeast|east|southeast|south|southwest|west|northwest)
- +
north|northeast|east|southeast|south|southwest|west|northwest|central)
-  
-  subst = {}
-  if availability_zone:
+ [Impact]
+ Ubuntu instances launched in the eu-central-1 EC2 region will not discover 
region-local mirrors. The user will see a degraded experience as they have to 
interact with mirrors that are further away and under heavier load. They will 
also potentially have to pay for the bandwidth used this way (as will the 
default mirror admins).
+ 
+ [Test Case]
+ Launch an instance in eu-central-1 and examine the apt sources used.  They 
should be of the form eu-central-1.ec2.archive.ubuntu.com instead of 
eu-central-1a.clouds.archive.ubuntu.com.
+ 
+ [Regression Potential]
+ Limited; the changes are limited to the mirror discovery, and if mirror 
discovery fails, we have default mirrors that we will use.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1456684

Title:
  does not know central (eu-central-1) is a direction for ec2 zones

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1381776] Re: cloud init depends on python-serial but does not declare it

[Dan Watkins]

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1381776

Title:
  cloud init depends on python-serial but does not declare it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1381776/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1381776] Re: cloud init depends on python-serial but does not declare it

[Dan Watkins]

Hi Drew, Jonathan,

cloud-init dynamically loads the data source modules based on which ones
it's configured to use. If you don't need the CloudSigma data source,
then you could do 'dpkg-reconfigure cloud-init' and remove it from the
list that is configured. This just puts a file in /etc/cloud/cloud.cfg.d
(see below for an example with most data sources disabled), so you could
also look at doing this manually.

$ cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
# to update this file, run dpkg-reconfigure cloud-init
datasource_list: [ NoCloud, ConfigDrive ]

I will also look in to including python-serial in the Depends for
precise and trusty.

Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1381776

Title:
  cloud init depends on python-serial but does not declare it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1381776/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1463373] Re: cc_apt_configure does not work with python3

[Dan Watkins]

** Description changed:

  The way cc_apt_configure.py writes out the script to fetch GPG keys
  breaks when using Python 3.
  
- * There's a constant, http://bazaar.launchpad.net/~cloud-init-dev/cloud-
- init/trunk/view/head:/cloudinit/config/cc_apt_configure.py#L39 that
- contains the script.
+ [Impact]
+ GPG keys specified in cloud configuration cannot be checked.
  
- * In getkeybyid, it's written to a temporary file:
- http://bazaar.launchpad.net/~cloud-init-dev/cloud-
- init/trunk/view/head:/cloudinit/config/cc_apt_configure.py#L113
+ [Test Case]
+ Specify a key in a source in the apt_sources cloud config key, and ensure 
that there aren't warnings about it in /var/log/cloud-init.log after boot.
  
- Python 3 throws an exception: 'str' does not support the buffer
- interface when doing the write.
- 
- A very simple example:
- 
- import tempfile
- 
- fh = tempfile.NamedTemporaryFile()
- TEST_STR =  HELLO WORLD 
- fh.write(TEST_STR)
- 
- Will work with 2, but not 3.
+ [Regression Potential]
+ This part of the feature is completely broken at the moment, so very little 
chance to regress.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1463373

Title:
  cc_apt_configure does not work with python3

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1381776] Re: cloud init depends on python-serial but does not declare it

[Dan Watkins]

** Description changed:

- cloud-init 0.6.3-0ubuntu1.14 appears to depend on python-serial (due to
- the backported cloudsigma support patch), but this dependency is not
- specified in the package.
+ [Impact]
+ cloud-init will fail to run on an installation of Ubuntu which doesn't 
include python-serial. This excludes normal cloud images (as they ship with 
Landscape, which indirectly depends on it), but custom built images (or more 
minimal images) will see this.
+ 
+ [Test Case]
+ Build an image with cloud-init in its default configuration but without 
another package that depends on python-serial.  cloud-init should run 
successfully on boot.
+ 
+ [Regression Potential]
+ None; we are just adding a dependency which exists in the archive for all 
versions and which is installed already in most deployments.
+ 
+ [Original Report]
+ cloud-init 0.6.3-0ubuntu1.14 appears to depend on python-serial (due to the 
backported cloudsigma support patch), but this dependency is not specified in 
the package.
  
  I built a machine image via debootstrap and installing the cloud-init
  package, but upon boot, cloud-init doesn't perform any of the expected
  actions, and I get this backtrace in /var/log/boot.log:
  
  Traceback (most recent call last):
-   File /usr/bin/cloud-init, line 229, in module
- main()
-   File /usr/bin/cloud-init, line 166, in main
- cloud.get_data_source()
-   File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 207, in 
get_data_source
- dslist = list_sources(cfglist, self.ds_deps)
-   File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 552, in 
list_sources
- return(DataSource.list_sources(cfg_list, depends, [cloudinit, ]))
-   File /usr/lib/python2.7/dist-packages/cloudinit/DataSource.py, line 178, 
in list_sources
- mod = __import__(%sDataSource%s % (pkg, ds_coll))
-   File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceCloudSigma.py, 
line 25, in module
- from cloudinit.cs_utils import Cepko
-   File /usr/lib/python2.7/dist-packages/cloudinit/cs_utils.py, line 36, in 
module
- import serial
+   File /usr/bin/cloud-init, line 229, in module
+ main()
+   File /usr/bin/cloud-init, line 166, in main
+ cloud.get_data_source()
+   File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 207, in 
get_data_source
+ dslist = list_sources(cfglist, self.ds_deps)
+   File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 552, in 
list_sources
+ return(DataSource.list_sources(cfg_list, depends, [cloudinit, ]))
+   File /usr/lib/python2.7/dist-packages/cloudinit/DataSource.py, line 178, 
in list_sources
+ mod = __import__(%sDataSource%s % (pkg, ds_coll))
+   File /usr/lib/python2.7/dist-packages/cloudinit/DataSourceCloudSigma.py, 
line 25, in module
+ from cloudinit.cs_utils import Cepko
+   File /usr/lib/python2.7/dist-packages/cloudinit/cs_utils.py, line 36, in 
module
+ import serial
  ImportError: No module named serial
  
  The fix would appear to be adding python-serial to Depends.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1381776

Title:
  cloud init depends on python-serial but does not declare it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1381776/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

** Branch linked: lp:~daniel-thewatkins/cloud-init/lp1411582

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1463373] Re: cc_apt_configure does not work with python3

[Dan Watkins]

** Changed in: cloud-init
 Assignee: Dan Watkins (daniel-thewatkins) = (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1463373

Title:
  cc_apt_configure does not work with python3

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: Azure data source should auto-detect ephemeral disk location

[Dan Watkins]

** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-init
   Status: New = In Progress

** Changed in: cloud-init
 Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  Azure data source should auto-detect ephemeral disk location

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1440263] Re: CloudStack reset password not working

[Dan Watkins]

Thomas,

Could you test the code in the branch that is now attached to this bug
and see if that solves your problem?


Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1440263

Title:
  CloudStack reset password not working

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1375252] Re: [SRU] Hostname change is not preserved across reboot on Azure Ubuntu VMs

[Dan Watkins]

Hi Joe,

On 10/06/15 10:52, Joe Clifford wrote:
 Apologies for the tardy feedback. Many thanks to all involved,
 gratefully and much appreciated. From my perspective, this issue is now
 resolved.

Thanks for the feedback. Great to hear that we've resolved this for you!

 I've just tried this on a freshly deployed Trusty VM in Azure -  a
 change to the hostname with 'hostnamectl' is now preserved when the VM
 is rebooted.
 
 I would like to point out though that, if not editing the /etc/hostname
 file directly, the 'hostnamectl' command must be used to set the
 hostname; using the 'hostname' command doesn't work (presumably because
 the hostname command doesn't change /etc/hostname).

As per the 'hostname' manpage:

When  called  with one argument ..., the commands set the host name ...
Note,  that  this is  effective  only  until  the  next  reboot.   Edit
/etc/hostname for permanent change.

So that sounds like expected behaviour. :)


Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1375252

Title:
  [SRU] Hostname change is not preserved across reboot on Azure Ubuntu
  VMs

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1374166] Re: Document how to add swap space on Azure resource disk

[Dan Watkins]

On 01/06/15 23:55, trialotto wrote:
 You are very likely to be correct, I saw the specific code (for recent
 versions of cloud-init) and it should be able to reformat disks.
 
 Questions are:
 
 - is the swap created after or before the reformat? (Note: a reformat removes 
 the characteristic persistent from persistent swap) 

swap is created as part of the reformat; before the reformat we have a
disk with a single NTFS partition.  I'm not even sure what it would mean
to create it before the reformat.

Persistent swap is swap that continues to exist after a reboot; it
doesn't retain any data over reboots (any more than RAM does).  Unless
you have an application that immediately requires swap on boot, this is
effectively persistent swap.  (And if you have such an application, you
probably aren't using an appropriately sized VM for it)

 - is the Azure VM image running the most appropriate and/or recent
cloud-init version?

This functionality is in all supported Ubuntu images on Azure; it was
introduced for trusty and backported to precise in April 2014 (i.e.
before trusty was even released).

 It often has been the problem that cloud-init versions on Azure Ubuntu
 VMs are not really up-to-date.

Each release of Ubuntu contains the latest version of cloud-init when it
is released.  We then follow Ubuntu's Stable Release Update process[0]
to backport any important functionality (or security fixes) whilst
avoiding regression; the cloud-init versions on official Ubuntu images
in Azure _are_ up-to-date.

 However, I will try to test which issues occur (if any), after thursday
 though.

If you do find issues that aren't simply with the documentation at
https://wiki.ubuntu.com/AzureSwapPartitions, please open a new bug. :)


Thanks,

Dan

[0] https://wiki.ubuntu.com/StableReleaseUpdates

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1374166

Title:
  Document how to add swap space on Azure resource disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374166/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1374166] Re: Document how to add swap space on Azure resource disk

[Dan Watkins]

Hi David,

On 31/05/15 09:45, David Frank wrote:
 So I ended up on this page and found the conclusion is azure cloud-init
 doesn't support adding a swap through configuration, is that true?
 
 ...
 
 I have read both:
 
 - https://wiki.ubuntu.com/AzureSwapPartitions
 - 
 https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-agent-user-guide/
 
 Yet I am still not sure how could I edit my configuration to create a
 swap through cloud-init on next boot. If this is fixed and released,
 then please help point me and whoever comes next to the right doc.
 

The wiki page has a pretty comprehensive description of how you can add
a swap partition using cloud-init configuration, including a full
configuration that will actually do it at the bottom of the page, so I'm
not really sure how you're drawing that conclusion.

That said, if that documentation doesn't apply to your case or is in
some way unclear, please let me know and I'll do my best to amend it. :)


Thanks,

Dan

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1374166

Title:
  Document how to add swap space on Azure resource disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374166/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs