[Bug 1559307] Re: [SRU] update walinuxagent to 2.1.3 in Wily

2016-03-21 Thread Robert C Jennings
** Changed in: walinuxagent (Ubuntu)
Milestone: wily-updates => ubuntu-16.04

-- 
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/1559307

Title:
  [SRU] update walinuxagent to 2.1.3 in Wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1559307/+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 1559307] Re: [SRU] update walinuxagent to 2.1.3 in Wily

2016-03-21 Thread Robert C Jennings
** Changed in: walinuxagent (Ubuntu)
   Status: In Progress => Fix Released

-- 
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/1559307

Title:
  [SRU] update walinuxagent to 2.1.3 in Wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1559307/+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 1559307] [NEW] [SRU] update walinuxagent to 2.1.3 in Wily

2016-03-19 Thread Robert C Jennings
Public bug reported:

SRU Justification

[IMPACT] Version 2.1.2 was promoted for Wily as part of bug #1523715 but
failures were seen during further testing of the proposed Trusty
package; promotion was halted and work on bug fixes was started.  Those
fixes were released as 2.1.3.

[FIX] Update to version 2.1.3 for Wily (already in Xenial)

[Test case 1]: Upgrade testing
1.) Launch instance on Azure
2.) Upgrade walinuxagent from -proposed
3.) Confirm that "waagent" is running, check /var/log/waagent.log
4.) Reboot, repeat step 3
5.) Capture instance and provsion new instances; repeat step 3

[Test Case 2]: New instance
1.) Build new cloud image from -proposed
2.) Boot instance
3.) Confirm that instance provisioned
4.) Boot instance and confirm that it works with Docker Extension

[UPSTREAM TESTING]: The Canonical Cloud Image team has been working with
Microsoft to ensure that this package is well tested. Validation will be
performed by both Microsoft and the Canonical Cloud Image team.

[ORIGINAL REQUEST]

Github Release: https://github.com/Azure/WALinuxAgent/releases/tag/v2.1.3
Changelog:
 - Refactor distro class
 - Fixed protocol detection on Azure Stack
 - Fix extension handling issue
 - Allow overwrite existing user
 - Decode and execute custom data

Impact for 15.10 in Azure if not picked up:
 - Bugs were found during validation of 2.1.2 after promotion of the package to 
Wily.  2.1.3 includes fixes for these issues.

** Affects: walinuxagent (Ubuntu)
 Importance: Critical
 Assignee: Robert C Jennings (rcj)
 Status: In Progress

-- 
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/1559307

Title:
  [SRU] update walinuxagent to 2.1.3 in Wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1559307/+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 1546312] Re: Please update to open-vm-tools 10.0.7

2016-03-15 Thread Robert C Jennings
>From 10.0.5 to 10.0.7 the only substantive change is the addition of
'the namespace command line utility "vmware-namespace-cmd"'.  The
'vmware-namespace-cmd' tool comes without documentation beyond the
cmdline usage text and I have been unable to find documentation online
for this tools on VMWare's site.   In the past Debian developers have
been kind enough to provide man pages for other tools in this package
but I don't see much to go on.

Oliver, can you document the importance, and usage, of the new "vmware-
namespace-cmd" executable in this bug?   Thank you.

-- 
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/1546312

Title:
  Please update to open-vm-tools 10.0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1546312/+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 1539317] Re: default user should be in the lxd group

2016-03-09 Thread Robert C Jennings
smoser, I tested this with cloud-init
0.7.7~bzr1176+1179+441~ubuntu16.04.1 from ppa:cloud-init-dev/daily and
it added the group for the ubuntu user.  I tested with and without
LX[CD] installed (installing LXD after the default user and lxd group
were created).

-- 
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/1539317

Title:
  default user should be in the lxd group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1539317/+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 1539317] Re: default user should be in the lxd group

2016-03-09 Thread Robert C Jennings
** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Robert C Jennings (rcj)

-- 
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/1539317

Title:
  default user should be in the lxd group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1539317/+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 1539317] Re: default user should be in the lxd group

2016-03-09 Thread Robert C Jennings
Requesting this for 16.04 and raising priority for visibility.

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Critical

** Changed in: cloud-init (Ubuntu)
Milestone: None => ubuntu-16.04

-- 
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/1539317

Title:
  default user should be in the lxd group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1539317/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-03-02 Thread Robert C Jennings
** 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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1546312] Re: Please update to open-vm-tools 10.0.7

2016-02-18 Thread Robert C Jennings
Oliver, we would like to keep in step with Debian.  Would you mind
filing a debian bug for 10.0.7?  I don't see one already.  Thanks.

-- 
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/1546312

Title:
  Please update to open-vm-tools 10.0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1546312/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-05 Thread Robert C Jennings
New trusty.debdiff based on feedback from Ben.  I have cleaned up the
changelog (version and path to patch), fixed the diff to have the
correct from address, and changed dmi_data() to call
util.read_dmi_data() rather than use a local implementation of that util
function.

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564774/+files/trusty.debdiff

** Patch removed: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564773/+files/trusty.debdiff

** Patch removed: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564237/+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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-05 Thread Robert C Jennings
New trusty.debdiff based on feedback from Ben.  I have cleaned up the
changelog (version and path to patch), fixed the diff to have the
correct from address, and changed dmi_data() to call
util.read_dmi_data() rather than use a local implementation of that util
function.

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564773/+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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-05 Thread Robert C Jennings
New wily.debdiff based on feedback from Ben. I have cleaned up the
changelog (version and path to patch).

** Patch added: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564782/+files/wily.debdiff

** Patch removed: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564236/+files/wily.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
I am going to delete the patches and post them again.  I need to update
them from the final patch that was merged upstream.  They were here
prematurely.

** Patch removed: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563911/+files/trusty.debdiff

** Patch removed: "vivid.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564068/+files/vivid.debdiff

** Patch removed: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564069/+files/wily.debdiff

** Patch removed: "xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564070/+files/xenial.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
SRU templated added and ready for upload/sponsorship.

Scott, can you ack the upload?
Ben, can you sponsor this?

Thanks.

** Description changed:

+ [Impact]
+ 
+  * Cloud-init does not support the datasource presented to LX-Brand
+zones in SmartOS.  Without this support cloud-init does not work
+on the Joyent cloud platform's container service.
+ 
+  * The metadata is provided in the same format as already supported
+for KVM-based instances for the SmartOS datasource (with
+communication over a serial port).  For LX-Brand zones the
+metadata is accessed via a socket file.
+ 
+ [Test Case]
+ 
+  * Install cloud-init on an lx-brand zone image and
+run 'cloud-init init'.  No metadata will be found without
+this patch.
+ 
+  * With the patched cloud-init, run 'cloud-init init' on the
+new lx-brand zones images.  The metadata should be discovered
+and the instance should be recognized as being provisioned.
+Perform the same testing on existing KVM-based SmartOS instances
+to ensure there is no regression.
+ 
+ [Regression Potential]
+ 
+  * [Trusty only] This SRU backports support for the V2 metadata format
+that has been present since the Vivid release.  This is well tested
+code and has no user-facing impact.  This was done because the
+V2 datasource allows for serial or socket communication. The existing
+Joyent datasource uses the serial port provided in KVM instances,
+however LX-brand zones have a socket instead @
+/native/.zonecontrol/metadata.sock.  Additionally the V2 datasource
+provides checksums and response length fields that allow for
+validation of results.  Additional testing was performed on Trusty
+SmartOS and KVM instances to validate these changes.
+ 
+  * To keep code common for KVM (serial) and LX-Brand (socket)
+communication the code had to switch to read byte-by-byte from
+the metadata source file object to avoid reading past the end of
+input on the socket which would block indefinitely.  This is a change
+from using readline and will be slower but not significantly so.
+ 
+  * This builds on the existing SmartOS datasource to enable LX-Brand.
+There is risk that this will break the datasouce on existing KVM
+instances. To mitigate this risk testing has been performed on
+both environments with Trusty, Vivid (out of support today),
+Wily, and Xenial.
+ 
+ [Other Info]
+ 
+  * This is python 2/3 byte/string safe on Vivid, Wily, and Trusty
+where cloud-init supports python 3.
+ 
+  Original Description 
+ 
  The Joyent Metadata Protocol Specification (Version 2)[1] allows for
  serial or socket communication. The existing Joyent datasource uses the
  serial port provided in KVM instances, however LX-brand zones have a
  socket instead @ /native/.zonecontrol/metadata.sock.
  
  Detecting we are in a Joyent LX-brand zone is possible by looking at 
'/bin/uname -v' which will report "BrandZ virtual linux" or checking for the 
existence of a /native mount where '/native/usr/bin/uname -s' reports
  SunOS.

-- 
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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Replacement patch for trusty attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Ftrusty%2Fsdc-lxbrand

I didn't need to delete this one earlier, but I did.

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564237/+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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
The code was accepted upstream and published for Xenial in cloud-init
0.7.7~bzr1160-0ubuntu1 .

-- 
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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Replacement patch for wily attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fwily%2Fsdc-lxbrand

Fixed python 2 testing w.r.t. strings/bytes.

** Patch added: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564236/+files/wily.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Patch for trusty attached, branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Ftrusty%2Fsdc-lxbrand

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563911/+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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
SmartOS: Add support for Joyent LX-Brand Zones

LX-brand zones on Joyent's SmartOS use a different metadata source
(socket file) than the KVM-based SmartOS virtualization (serial port).
This patch adds support for recognizing the different flavors of
virtualization on SmartOS and setting up a metadata source file object.
After the file object is created, the rest of the code for the datasource
can remain common.

This patch reads the metadata byte-by-byte rather than using readline
because we can not perform a readline on the file-like object for the
socket as this block indefintely waiting for an EOF that is will not be
sent by the host platform.  This patch also moves to V2 metadata as it
provides checksum validation and makes reading the metadata much more
reliable.

-- 
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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Patch for vivid attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fvivid%2Fsdc-lxbrand


** Patch added: "vivid.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563912/+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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Patch for xenial attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fmaster%2Fsdc-lxbrand


** Patch added: "xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563914/+files/xenial.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Patch for wily attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fwily%2Fsdc-lxbrand

** Patch added: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563913/+files/wily.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Assigning to Scott for patch review.  I will update the description with
SRU template.

** Changed in: cloud-init (Ubuntu)
 Assignee: Robert C Jennings (rcj) => Scott Moser (smoser)

-- 
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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
** Branch linked: lp:~rcj/cloud-init/lp1540965

-- 
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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Patch for vivid attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fvivid%2Fsdc-lxbrand

** Patch removed: "vivid.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563912/+files/vivid.debdiff

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

** Patch removed: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563913/+files/wily.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Replacement patch for xenial attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fmaster%2Fsdc-lxbrand

Dropped changes to test-requirements.txt

** Patch added: "xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564070/+files/xenial.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] Re: Support Joyent lx-brand environment in smartos datasource

2016-02-04 Thread Robert C Jennings
Replacement patch for wily attached, git branch @
https://git.launchpad.net/~rcj/ubuntu/+source/cloud-init?h=features%2Fwily%2Fsdc-lxbrand

Dropped changes to test-requirements.txt

** Patch added: "wily.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4564069/+files/wily.debdiff

** Patch removed: "xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+attachment/4563914/+files/xenial.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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1540965] [NEW] Support Joyent lx-brand environment in smartos datasource

2016-02-02 Thread Robert C Jennings
Public bug reported:

The Joyent Metadata Protocol Specification (Version 2)[1] allows for
serial or socket communication. The existing Joyent datasource uses the
serial port provided in KVM instances, however LX-brand zones have a
socket instead @ /native/.zonecontrol/metadata.sock.

Detecting we are in a Joyent LX-brand zone is possible by looking at 
'/bin/uname -v' which will report "BrandZ virtual linux" or checking for the 
existence of a /native mount where '/native/usr/bin/uname -s' reports
SunOS.

** Affects: cloud-init (Ubuntu)
 Importance: High
 Assignee: Robert C Jennings (rcj)
 Status: 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/1540965

Title:
  Support Joyent lx-brand environment in smartos datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1540965/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-11-05 Thread Robert C Jennings
** Changed in: open-vm-tools (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-11-05 Thread Robert C Jennings
Fixed changelog mistake in commit
3595280d8803319f71b53a22e39c386fab1577bf of the tree.

The changelog in the merge of 9.10.3-3167576 accidentally dropped
history and pulled in content from a dead development branch.  This
patch fixes the changelog to reflect actual changes.

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1492429] Re: please update open-vm-tools to version 10.0.0

2015-11-04 Thread Robert C Jennings
While bug #1482777 is being worked ([MIR] open-vm-tools 9.10.2 build
dependencies: xml-security-c and xerces-c) we will build 10.0 without
SAML-based guest authentication.

-- 
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/1492429

Title:
  please update open-vm-tools to version 10.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1492429/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-11-04 Thread Robert C Jennings
Merging upstream 9.10.3-3167576:
https://git.launchpad.net/~rcj/ubuntu/+source/open-vm-tools/commit/?id=641279a0debd198005d53de8e494a09207e2f16a

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-11-04 Thread Robert C Jennings
Package @ ppa:rcj/open-vm-tools

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1492429] Re: please update open-vm-tools to version 10.0.0

2015-11-04 Thread Robert C Jennings
Merge from Debian 2:10.0.0-3000743-3-ubuntu-1:
https://git.launchpad.net/~rcj/ubuntu/+source/open-vm-tools/commit/?id=769eeb593ce62eec332f13db653785429a942f39

-- 
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/1492429

Title:
  please update open-vm-tools to version 10.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1492429/+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 1492429] Re: please update open-vm-tools to version 10.0.0

2015-11-04 Thread Robert C Jennings
Package @ ppa:rcj/open-vm-tools

-- 
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/1492429

Title:
  please update open-vm-tools to version 10.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1492429/+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 1492429] Re: please update open-vm-tools to version 10.0.0

2015-10-26 Thread Robert C Jennings
We will sync 10.0.0 for xenial

-- 
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/1492429

Title:
  please update open-vm-tools to version 10.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1492429/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-10-26 Thread Robert C Jennings
Debian has moved to 10.0.0.  Ubuntu will update 9.10.2 to 9.10.3 for
Wily and pull in 10.0.0 for Xenial.

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-25 Thread Robert C Jennings
I agree that this shuffling around is not pretty, but we need a solution
that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in
use as had prior to http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/ubuntu.wily/revision/2360

The current situation conflicts with how clouds are instructing users to
set up private networks. [1] [2]

[1] http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html
[2] 
https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-private-ip/

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-25 Thread Robert C Jennings
Séphane,

When this was added to the cloud seed we changed this from "users that
install LXC will loose connectivity to a 10.0.x.0/24 network" to "all
cloud users do not have connectivity to a 10.0.x.0/24 network at boot"
and the cause/effect will not be as clear to an end user.  This had come
up in conversation but had not been documented in the bug.   So let us
continue to search for a solution like what you have outlined in the
last paragraph of comment #29.

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-24 Thread Robert C Jennings
Cloud images build from proposed are available.

Next action:

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-24 Thread Robert C Jennings
Cloud image downloads for amd64, i386, and ppc64el are available @ http
://cloud-images.ubuntu.com/proposed/wily/20151024/

The amd64 image is also available in canonistack lcy02 region as
lp1509414/wily-proposed

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-24 Thread Robert C Jennings
Be aware in your testing that the lxd-net's service can come up slowly
depending on the speed of your cloud instance. Without the bridge
(lxcbr0) the container's networking will function prior to that service
starting; watch out for this false positive in your testing.

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-24 Thread Robert C Jennings
Cloud images build from proposed are available.

Next action:
 - Verification of proposed package.

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-24 Thread Robert C Jennings
My testing with the cloud image containing the proposed package has been
successful.

Just a note again that the test case detailed in the description is fine
with the understanding that network testing needs to ensure the lxc-net
service has started lxcbr0 or a false positive is possible (per comment
#18).

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-24 Thread Robert C Jennings
The cloud-image builder picked up the change and is building images.
They are with the LP buildds now.  I will update this bug once
publication completes.

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

2015-10-23 Thread Robert C Jennings
Action plan:
Stage 1 - Configure lxc-net at boot rather than at install.
 * This addresses the network failure for 15.10 containers started on 15.10 
hosts (patch  above in comment #6)
Stage 2 - Start lxc-net through systemd on the first launch of an LXC container.
 * This mitigates the unroutable 10.0.x.0/16 network issue for general cloud 
image users.  With this step we’re back to Trusty function.
 * This will work for privileged users, like Juju, without any interaction.  
Unprivileged users will be directed to start the service on the first container 
launch.

Next action:
 - serge-hallyn working on patch (last update in comment #7) and code in 
ppa:serge-hallyn/lxc-natty.  Patch is not yet ready for upload and serge will 
update as he progresses.
 - Once ready, uploaded, and published in -proposed, email ring rcj/utlemming 
and we'll ensure cloud image builder picks this up ASAP to build -proposed 
images

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1489675] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build [error: ‘new_sync_read’ undeclared here (not in a function)]

2015-10-22 Thread Robert C Jennings
*** This bug is a duplicate of bug 1500581 ***
https://bugs.launchpad.net/bugs/1500581

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

** Also affects: open-vm-tools (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
   Importance: Unknown
   Status: Unknown

** This bug has been marked a duplicate of bug 1500581
   open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: 
implicit declaration of function ‘nd_set_link’]

-- 
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/1489675

Title:
  open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel
  module failed to build [error: ‘new_sync_read’ undeclared here (not in
  a function)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1489675/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-10-22 Thread Robert C Jennings
** Changed in: open-vm-tools (Ubuntu)
 Assignee: (unassigned) => Robert C Jennings (rcj)

** Changed in: open-vm-tools (Ubuntu)
Milestone: None => wily-updates

** Patch removed: "0001-vmhgfs-support-linux-4.2.x-kernel.patch"
   
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1500581/+attachment/4480293/+files/0001-vmhgfs-support-linux-4.2.x-kernel.patch

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-10-22 Thread Robert C Jennings
I have removed the patch from comment #4.  Running with the vmhgfs
driver from the 9.10.2 code can result in data corruption.  The backport
of the driver from 10.0.0 to 9.10.3 resolves the data corruption issue
as well as addressing the kernel compilation failures for 4.1 and 4.2
kernels.

As noted in comment #7, the 9.10.3 code has been tested by VMWare
against 15.10 with the 4.2.0-16 kernel.

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1492429] Re: please update open-vm-tools to version 10.0.0

2015-10-22 Thread Robert C Jennings
** Changed in: open-vm-tools (Ubuntu)
 Assignee: (unassigned) => Robert C Jennings (rcj)

** Changed in: open-vm-tools (Ubuntu)
Milestone: None => ubuntu-16.04

-- 
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/1492429

Title:
  please update open-vm-tools to version 10.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1492429/+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 1500581] Re: open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’]

2015-09-30 Thread Robert C Jennings
** Bug watch added: Debian Bug tracker #800322
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322

** Also affects: open-vm-tools (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
   Importance: Unknown
   Status: Unknown

-- 
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/1500581

Title:
  open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
  [error: implicit declaration of function ‘nd_set_link’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1500581/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-20 Thread Robert C Jennings
Robie, can you review the patch in comment #10 for this fix?  Thanks.

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1485685] Re: Users are prompted on upgrade of cloud images

2015-08-20 Thread Robert C Jennings
** Changed in: cloud-init (Ubuntu)
   Importance: Undecided = Medium

** Changed in: cloud-init (Ubuntu)
 Assignee: Robert C Jennings (rcj) = (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/1485685

Title:
  Users are prompted on upgrade of cloud images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1485685/+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 1485685] Re: Users are prompted on upgrade of cloud images

2015-08-18 Thread Robert C Jennings
To add clarity, the debconf proposal in comment #5 is the long-term
solution.  In the interim, the workaround in comment #4 to remove the
ucf registry entry is needed.  For existing users, this will need to be
done by hand.  For future cloud images the ufc entry will be removed
(in the short-term) with debconf-ized grub-legacy-ec2 as a long-term
solution.

** Changed in: ubuntu
   Status: Confirmed = Triaged

** Package changed: ubuntu = cloud-init (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/1485685

Title:
  Users are prompted on upgrade of cloud images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1485685/+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 315896] Re: freeradius upgrade broken in hardy backports

2015-08-05 Thread Robert C Jennings
Marking as won't fix due to hardy EOL.

** Changed in: freeradius (Ubuntu)
   Status: Triaged = Won't Fix

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

Title:
  freeradius upgrade broken in hardy backports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/315896/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-05 Thread Robert C Jennings
Updated the patch.   The post-install scripts will restart the daemon so
that an upgrade will restart the daemon so that future reloads do work.
This addresses the 3rd scenario in comment #7.  There would be no
regression for users on upgrade.  If the service has been reloaded prior
to the upgrade such that upstart can't manage the daemon then this won't
fix things but won't regress the user either.  In that case, the user
will need to kill the running, unmanaged freeradius process and then
start from upstart again.

** Patch added: trusty_freeradius_lp1406105.patch
   
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4439874/+files/trusty_freeradius_lp1406105.patch

** Changed in: freeradius (Ubuntu)
   Status: Confirmed = In Progress

** Description changed:

  The freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS (Trusty Tahr)
  has a bug in the logrotate script (/etc/logrotate.d/freeradius):
  
  The command /etc/init.d/freeradius reload is used for reloading
  freeradius after its logfile(s) have been rotated. However, in Ubuntu
  14.04 LTS freeradius is managed by Upstart, so that the script cannot
  work (the PID file does not exist).
  
  Therefore, the logrotate script should use initctl reload freeradius
  instead. Please note that this might not work either at the moment, due
  to bug #1282683. However, when this bug is finally fixed, the command
  mentioned earlier should work.
+ 
+ WORKAROUND:
+ 
+ Add an 'exec' in /etc/init/freeradius.conf per the patch in comment #8
+ and change /etc/logrotate.d/freeradius to use 'service freeradius
+ reload' rather then '/etc/init.d/freeradius reload' as per the same
+ patch in comment #8.  Attempt a 'service freeradius stop' and check that
+ the freeradius process is not running (or manually kill it).  From there
+ the service can now be started with 'service freeradius start'

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-05 Thread Robert C Jennings
** Changed in: freeradius (Ubuntu Vivid)
   Status: New = Invalid

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-05 Thread Robert C Jennings
Marking vivid as invalid as the this affects trusty (upstart) only not
systemd based releases (vivid/wily)

** Changed in: freeradius (Ubuntu)
   Status: In Progress = Invalid

** Changed in: freeradius (Ubuntu Trusty)
   Status: Triaged = In Progress

** Changed in: freeradius (Ubuntu Trusty)
 Assignee: (unassigned) = Robert C Jennings (rcj)

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-05 Thread Robert C Jennings
** Description changed:

+ [Impact]
+ 
+  * freeradius can not be reloaded, upstart will lose track of the
+ process and leave the original process running (blocking future service
+ starts)
+ 
+  * log rotation will not function as intended. The service is not
+ reloaded and the file handles for the rotated logs will not be dropped.
+ Logging after rotation occurs will consume storage but be inaccessible
+ to the user for review.
+ 
+ 
+ [Test Case]
+ 
+  * 'service freeradius start'
+  * 'service freeradius reload'
+  * 'service freeradius status' Result stop/waiting
+  * 'ps -ef|grep freeradius' Result: prior freeradius process still running, 
new process can not be started.  Existing process can not be stopped
+  * 'service freeradius stop' Result: process does not stop, not tracked up 
upstart
+ 
+ OR
+  * 'service freeradius start' Result: PID displayed is for 'sh' not 
'freeradius'
+  * logrotate --verbose --force /etc/logrotate.d/freeradius
+  * 'service freeradius status' Result: stop/waiting
+  * 'ps -ef | grep freeradius' Result: freeradius still running (never 
received HUP)
+  
+ 
+ [Regression Potential]
+ 
+  * Upgrade testing needs to ensure that upgrade does not make a system
+ which still could stop/restart freeradius no longer able to stop/restart
+ without manually killing the freeradius process.  Mitigated because the
+ postinst for freeradius will restart the service.  The postinst for
+ freeradius-* will reload but will be run after the freeradius postinst
+ has restarted to use our fixed upstart configuration.
+ 
+  * If the user has attempted to reload the service prior to upgrade,
+ which results in freeradius running but no longer managed by upstart,
+ the upgrade will not regress nor fix this environment.  In that case the
+ workaround, below, will need to be run (or server restarted) so that
+ upstart can manage freeradius.
+ 
+ [Other Info]
+  
+  * None
+ 
+ ORIGINAL DESCRIPTION:
+ 
  The freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS (Trusty Tahr)
  has a bug in the logrotate script (/etc/logrotate.d/freeradius):
  
  The command /etc/init.d/freeradius reload is used for reloading
  freeradius after its logfile(s) have been rotated. However, in Ubuntu
  14.04 LTS freeradius is managed by Upstart, so that the script cannot
  work (the PID file does not exist).
  
  Therefore, the logrotate script should use initctl reload freeradius
  instead. Please note that this might not work either at the moment, due
  to bug #1282683. However, when this bug is finally fixed, the command
  mentioned earlier should work.
  
+ In this case, freeradius is not reloaded so the file handles for the
+ rotated logs will remain open.  Logging will cause the disk utilization
+ to increase (log rotation is ineffective) and due to rotation the user
+ can not view the logs from that point forward.
+ 
+ Additionally, if 'service freeradius reload' is run, the service will
+ not be HUP'ed and upstart will lose track of the service, leaving the
+ process running.
+ 
  WORKAROUND:
  
  Add an 'exec' in /etc/init/freeradius.conf per the patch in comment #8
  and change /etc/logrotate.d/freeradius to use 'service freeradius
  reload' rather then '/etc/init.d/freeradius reload' as per the same
  patch in comment #8.  Attempt a 'service freeradius stop' and check that
  the freeradius process is not running (or manually kill it).  From there
  the service can now be started with 'service freeradius start'

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-05 Thread Robert C Jennings
Back to the prior patch to reduce scope by removing changes for 'init.d'
- 'service' for force-reload operations in postinst scripts if invoke-
rc.d is not available.  This is not changed as we can assume invoke-rc.d
is installed and the SRU change needs to be minimal.

** Patch added: trusty_freeradius_lp1406105.patch
   
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4439936/+files/trusty_freeradius_lp1406105.patch

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-04 Thread Robert C Jennings
Here is a debdiff to show how we can manage the process properly in an
upstart job (missing exec) so that a restart or reload works as we would
expect.  The patch also fixes the logrotate script to use the upstart
controls rather than the systemv init script (which should not have been
shipped because it isn't used on Trusty).

Prior to this patch you can't restart/reload the process because the
process isn't properly managed by upstart and logrotate's reload of
freeradius was a no-op.  With this patch, logstart will properly call
'service freeradius reload', ignoring failure due to the service not
running.

Package upgrade is a problem Is there a way  to fix the management
of a running freeradius process on a user's system when this package is
updated?  We would not want to perform an unexpected restart of the
service and without this fix reloading the service won't work (nor will
the restart because it kills the shell that start the freeradius process
but not the freeradius process itself).  However, having the upgraded
package on the system won't make the current situation any worse and
will resolve the issue on the first reboot (or manually killing
freeradius and starting again).

Best I know that we can do is put the fix in place and it will be
available after a restart; having the upgraded package on the system
won't make the current situation any worse but it won't fix the issue
prior to a restart or some manual intervention to clean up the unmanaged
freeradius process.

To illustrate the current process problem:
 1 - Install freeradius on trusty
 2 - Run 'start freeradius'
 3 - Get the PID upstart is using for freeradius with 'status freeradius'
 4 - Check ps for that PID
(e.g. if PID is 1023 run 'ps -ef | grep 1023 | grep -v grep'.  Upstart job 
PID will map to /bin/sh, the parent of freeradius)
 5 - Run 'reload freeradius'. 
  Expect success, exit 0 and freeradius is still running (SIGHUP was not 
delivered, check with a shim if you like)
 6 -  Run 'status freeradius' .
  Results in freeradius stop/waiting because the parent shell script died 
when it received HUP but freeradius is still running.
 7 - Run 'ps -ef |grep freeradius'.
  Expect freeradius still running (same PID as step 4 but PPID is now init)
  This process isn't tracked by upstart now.  You can't 'start freeradius' 
because the new process will exit upon failing to open the port already opened 
by the untracked freeradius.


** Patch added: trusty_freeradius_lp1406105.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4439415/+files/trusty_freeradius_lp1406105.debdiff

** Changed in: freeradius (Ubuntu)
 Assignee: (unassigned) = Robert C Jennings (rcj)

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-04 Thread Robert C Jennings
Wily is using the systemV init scripts and is not affected by this bug.

Trusty is using upstart which lacks a reload function currently.

Changing the logrotate postrotate script on trusty to call 'service
freeradius reload' will not work without explicitly creating a reload
function in the upstart job.  The patch as included in comment #2 will
kill the parent of freeradius (which is the upstart shell script) and
will attempt to restart it but the original freeradius process is still
running and no longer managed by upstart.  When this occurs, upstart
will show that the freeradius service is not running and will not be
able to start it because the port is in use by the un-managed freeradius
process.

Next action:
 - Investigate adding a reload handler for the upstart job.  This will need the 
PID for the freeradius process that was started so that it can send a HUP 
signal as seen in the systemV init job.  In the case that the PID file is 
missing then the reload should do nothing and exit cleanly as the lack of PID 
file would indicate that freeradius is not running; we would not want to 
restart the service as this would have the affect of starting a stopped 
service.  Then change logrotate script in trusty to call 'service freeradius 
reload'  and consider removing the redirect to /dev/null.

I have run out of time today but have left these notes so that we can
pursue it further.

** Changed in: freeradius (Ubuntu)
 Assignee: Robert C Jennings (rcj) = (unassigned)

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-04 Thread Robert C Jennings
** Changed in: freeradius (Ubuntu)
 Assignee: (unassigned) = Robert C Jennings (rcj)

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1406105] Re: Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS

2015-08-04 Thread Robert C Jennings
Robie / Chris,

Can you review comment #6 for the proposed patch and upgrade
issue/strategy?

The upstart config for freeradius is bad; reload(8) or restart(8) will
lose track of the process.  A reload won't send SIGHUP to the right
process and a restart(8) will  not stop the existing freeradius process;
in either case upstart loses track of the process and thinks the service
has stopped, further attempts to start the service will fail because of
the existing process holding the port open.  The patch fixes this for
new, clean starts of the service but on a running system I don't think
we have a way to make things better without manual intervention ('pkill
freeradius' when the user can afford to take the process down) or a
reboot.

I might be missing something clever, but I doubt there is a good way to
fix this for the different states we might find things in during
upgrade.

Scenarios:
1 - freeradius is not running.  Upgrading the package is great.
2 - freeradius is runing and 'reload/restart' has been called previously (i.e. 
upstart can't manage the freeradius process).  Upgrading will not regress the 
system because upstart could not manage the service prior to package upgrade.
3 - freeradius is running and 'reload/restart' has never been called  (i.e. 
upstart can still stop the process properly).  Upgrading will fix logrotate and 
the next rotation will call 'reload freeradius' causing upstart to lose track 
of the process.  It can no longer be stopped by upstart.

The only issue is scenario #3 which regresses the user's ability to stop
freeradius *if* they have not tried to reload or restart the service.  I
don't think that we can take the action to restart the service on
package upgrade if upstart can still manage the service due to service
interruption.  The next logrotation attempt will ensure that the user
can not manage freeradius from upstart.

-- 
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/1406105

Title:
  Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu
  14.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+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 1442392] Re: [SRU][FFE] update walinuxagent to 2.0.12

2015-04-30 Thread Robert C Jennings
Test case #3 completed for Trusty.

** Tags added: verification-done-trusty

-- 
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/1442392

Title:
  [SRU][FFE] update walinuxagent to 2.0.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1442392/+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 1442392] Re: [SRU][FFE] update walinuxagent to 2.0.12

2015-04-30 Thread Robert C Jennings
Verification of proposed walinuxagent completed on Utopic.  Tests
passed.

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

** Changed in: walinuxagent (Ubuntu Utopic)
 Assignee: (unassigned) = Robert C Jennings (rcj)

** Changed in: walinuxagent (Ubuntu Trusty)
 Assignee: (unassigned) = Robert C Jennings (rcj)

-- 
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/1442392

Title:
  [SRU][FFE] update walinuxagent to 2.0.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1442392/+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 1442392] Re: [SRU][FFE] update walinuxagent to 2.0.12

2015-04-29 Thread Robert C Jennings
Test cases #1 and #2 completed successfully for Trusty.  Building
proposed image now and will test when available.

-- 
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/1442392

Title:
  [SRU][FFE] update walinuxagent to 2.0.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1442392/+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 1336855] Re: [SRU] non-interactive grub updates for 12.04 break on AWS

2014-07-03 Thread Robert C Jennings
I have reviewed the patch (lp:~utlemming/ubuntu/precise/cloud-
init/lp1336855 through r211) and tested it on EC2 and an OpenStack cloud
and it performed well.  The upgrade of cloud-init forced a grub-install
and it ran with the correct root device.

-- 
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/1336855

Title:
  [SRU] non-interactive grub updates for 12.04 break on AWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+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 1336855] Re: [SRU] non-interactive grub updates for 12.04 break on AWS

2014-07-03 Thread Robert C Jennings
That should have been with the correct *boot* device

-- 
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/1336855

Title:
  [SRU] non-interactive grub updates for 12.04 break on AWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+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 1336855] Re: non-interactive grub updates for 12.04 break on AWS

2014-07-02 Thread Robert C Jennings
Confirmed your fix Ben.  Changed /usr/lib/python2.7/dist-
packages/cloudinit/CloudConfig/cc_grub_dpkg.py, removed
/var/lib/cloud/instance/sem/config-grub-dpkg, and ran cloud-init-cfg
grub-dpkg.  The cloud-init log confirmed xvda was selected and an
upgrade of grub worked.

-- 
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/1336855

Title:
  non-interactive grub updates for 12.04 break on AWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-17 Thread Robert C Jennings
Attaching a debdiff to update open-vm-tools in trusty so that it
replaces open-vm-tools-hwe upon upgrade from precise.

v4 changes:
 Fix up Breaks/Replaces for transitional packages


v3 changes:
 Rename prior package from *-hwe to *-lts-trusty

v2 changes:
 Add missing Conflicts directive for precise HWE packages

** Patch added: open-vm-tools update for trusty to upgrade from 
open-vm-tools-hwe [v4]
   
https://bugs.launchpad.net/ubuntu/trusty/+source/open-vm-tools/+bug/1275656/+attachment/4133297/+files/trusty%5Bv4%5D.debdiff

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-17 Thread Robert C Jennings
** Tags added: verification-done-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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-17 Thread Robert C Jennings
I have verified the trusty package in proposed (open-vm-tools
2:9.4.0-1280544-5ubuntu6.2).

Package upgrades:
* Upgrade from the precise-proposed packages worked correctly.
* Upgrade from the trusty 2:9.4.0-1280544-5ubuntu6 version worked as well.

Trusty functionality:
 * Copied text on the host desktop and pasted into a terminal on the trusty 
guest. (Reverse also worked)
 * Dragged a file from the file manager on the host to the file manager on the 
trusty guest. (Reverse also worked)
 * Resize of the vmware workstation window resized the trusty vm's desktop

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

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-16 Thread Robert C Jennings
** Changed in: open-vm-tools (Ubuntu Trusty)
   Status: Fix Committed = In Progress

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-16 Thread Robert C Jennings
I have fixed an issue infinity found in the trusty-proposed package.
There was a problem with the package relationships between the new and
transitional packages. The latest revision in this branch has a fix for
those relationships; namely the transitional package depends on the new
package, while the new package Breaks/Replaces the transitional package
with a version less than this trusty branch.  The tree has been posted
and a merge request made @ https://code.launchpad.net/~rcj/ubuntu/trusty
/open-vm-tools/trusty-proposed/+merge/223331 or debdiff @
http://paste.ubuntu.com/7656026/

Next actions:
 Patch needs review and upload
 Need review for trusty SRU for -proposed

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-12 Thread Robert C Jennings
Alex Bligh,
The description text was not up to date and I am correcting it.  When the 
kernel modules from the dkms package were taken to the Linux kernel community 
the vmhgfs module was not accepted and vmhgfs is no longer supported.  The 
current options for file access between the host and guest would be standard 
remote file systems such as CIFS or NFS.  Additionally, file drag-and-drop is 
functional and provided by open-vm-tools-lts-trusty-desktop.

** Description changed:

  [Impact]
  
-  * Failure to build the kernel modules in open-vm-dkms for HWE kernels 
impedes guest configuration, host/guest file system, desktop copy buffer 
sharing, etc when running a Precise VM on a VMWare host.
-  * This SRU focuses on HWE support for VMWare's vCloud Hybrid Service (vCHS) 
which requires open-vm-tools from the upstream stable stream (in Trusty) and 
the 3.9 kernel.
-  * These kernel modules from open-vm-dkms have been merged with the upstream 
kernel as of 3.9
-  * Upstream changes only available in the mainline kernel modules and the 
9.4.x stable series of open-vm-tools are required to support VMWare's vCloud 
Hybrid Service (vCHS).
+  * Failure to build the kernel modules in open-vm-dkms for HWE kernels 
impedes guest configuration, host/guest file system, desktop copy buffer 
sharing, etc when running a Precise VM on a VMWare host.
+  * This SRU focuses on HWE support for VMWare's vCloud Hybrid Service (vCHS) 
which requires open-vm-tools from the upstream stable stream (in Trusty) and 
the 3.9 kernel.
+  * These kernel modules from open-vm-dkms have been merged with the upstream 
kernel as of 3.9
+  * Upstream changes only available in the mainline kernel modules and the 
9.4.x stable series of open-vm-tools are required to support VMWare's vCloud 
Hybrid Service (vCHS).
  
-  State of Precise
-  * open-vm-tools in Precise is based on an unsupported development snapshot 
from upstream (http://open-vm-tools.sourceforge.net/)
-   * open-vm-dkms fails to build its kernel modules for open-vm-tools on 
Precise.
-   * Kernel modules affected include vmc_vmci and vmc_vsock both of which are 
host/guest communication.  They are used for guest configuration, host/guest 
file system, desktop copy buffer sharing, etc.
-   * This version of open-vm-tools is not supported by upstream or Debian.
-   * The modules which fail to build have been merged upstream, with the 
exception of the host-guest file system (hgfs) module which has been replaced 
with an hgfs FUSE helper.  These modules are available in v3.9 of the kernel 
and later (Saucy and later). This vmware knowlegebase article (2073804 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=2073804)
 maps out when each driver landed upstream but kernel 3.9 includes everything.
-  
-  State of Trusty/Upstream
-  * open-vm-tools in Debian testing/unstable and Trusty are based on the 
stable 9.4.x release from upstream.
-   * The kernel modules previously shipped by open-vm-dkms are now supported 
in the upstream kernel (v3.9 and later)
-   * The upstream kernel modules and open-vm-tools have received enhancements 
to support vmware's vCloud Hybrid Service (vCHS) which are not available 
downstream.
+  State of Precise
+  * open-vm-tools in Precise is based on an unsupported development snapshot 
from upstream (http://open-vm-tools.sourceforge.net/)
+   * open-vm-dkms fails to build its kernel modules for open-vm-tools on 
Precise.
+   * Kernel modules affected include vmc_vmci and vmc_vsock both of which are 
host/guest communication.  They are used for guest configuration, host/guest 
file system, desktop copy buffer sharing, etc.
+   * This version of open-vm-tools is not supported by upstream or Debian.
+   * The modules which fail to build have been merged upstream, with the 
exception of the host-guest file system (hgfs) module (host - guest access 
must be provided with a remote FS such as CIFS or NFS).  These modules are 
available in v3.9 of the kernel and later (Saucy and later). This vmware 
knowlegebase article (2073804 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=2073804)
 maps out when each driver landed upstream but kernel 3.9 includes everything.
  
-  Changes
-  1) back-ported the version of open-vm-tools in Trusty as a separate HWE 
package (open-vm-tools-hwe).
-* It will not be an upgrade target (does not contain provides: 
open-vm-tools) but would require manual installation along with an HWE kernel 
from Saucy or later.  The newer package will not regress open-vm-tools as it 
exists in Precise.
-* The open-vm-tools for Precise based on the 2011.12.20-562307 development 
snapshot can still be maintained by the community to support Precise with the 
stock kernel.
-  2) updated the open-vm-tools package in Trusty to replace the 
open-vm-tools-hwe packages created by this change.
+  State of Trusty/Upstream
+  * open-vm-tools in Debian 

[Bug 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-10 Thread Robert C Jennings
Marking as verification done.  I had failed verification erroneously and
I have re-verified to make sure this is correct.

I had previously failed this due to an install failure for a 3rd party
package from VMWare, thinking that the problem was in the control file
for this new package in precise.  After a bit of testing and education I
have learned that the 3rd party package is requiring open-vm-tools and
specifying a particular version range.  The virtual package in the
backport can't satisfy specific version requirements so the 3rd party
package must be updated with knowledge of the new open-vm-tools-lts-
trus-needed-trusty package.  With that resolved and the packages re-
verified I have set the tags and distribution/package status so that
these can be promoted from -proposed.

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

** Changed in: open-vm-tools (Ubuntu Precise)
   Status: In Progress = Fix Committed

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1269985] Re: Revert package back to Devel release

2014-06-09 Thread Robert C Jennings
With the stable package in trusty/utopic I am going to close this bug.

** Changed in: open-vm-tools (Ubuntu)
   Status: New = Won't Fix

-- 
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/1269985

Title:
  Revert package back to Devel release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1269985/+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 1328132] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-09 Thread Robert C Jennings
*** This bug is a duplicate of bug 1275656 ***
https://bugs.launchpad.net/bugs/1275656

Marking this as a duplicate of bug #1275656 which is in the process of
bringing the open-vm-tools from trusty back to precise for HWE kernels
such as this.

** This bug has been marked a duplicate of bug 1275656
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build

** Tags removed: need-duplicate-check

-- 
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/1328132

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1328132/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-09 Thread Robert C Jennings
** Tags removed: verification-failed
** Tags added: verification-failed-precise verification-needed

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

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-06 Thread Robert C Jennings
Verified functionality with open-vm-tools-lts-trusty on precise.
Upgrade from open-vm-tools to open-vm-tools-lts-trusty on precise worked
fine.  Copy/Paste buffer sharing and file drag-and-drop between host and
guest work.

Verified upgrade from open-vm-tools-lts-trusty to open-vm-tools when
moving from precise to trusty.  I started with a clean trusty
installation, removed its open-vm-tools package, changed the apt sources
to point to precise with -proposed, installed open-vm-tools-lts-trusty,
then switched apt sources back to trusty and performed a dist-upgrade.

** 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 open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-06 Thread Robert C Jennings
Marking as verification failed.  The open-vm-tools-lts-trusty package
does not have a provides for open-vm-tools which broke a package which
depends on open-vm-tools

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

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-06 Thread Robert C Jennings
The trusty package is fine, but I'll update the precise package

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-06 Thread Robert C Jennings
** Branch linked: lp:~rcj/ubuntu/trusty/open-vm-tools-lts-
trusty/lp1275656

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-06 Thread Robert C Jennings
** Changed in: open-vm-tools (Ubuntu Precise)
   Status: Fix Committed = In Progress

** Changed in: open-vm-tools (Ubuntu Trusty)
 Assignee: (unassigned) = Robert C Jennings (rcj)

** Changed in: cunit (Ubuntu Precise)
 Assignee: (unassigned) = Robert C Jennings (rcj)

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-06 Thread Robert C Jennings
 The other piece that is missing is that zerofree needs to be SRU'd to
 main as well. Otherwise, open-vm-tools-lts-trusty won't install purely
 from main.

Not sure that promotion to main is required for that.  The zerofree
package is recommended but not required.

That recommendation came from debian bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472799 because someone
thought it would be useful to VMWare users looking to shrink their disk
images.  I'd argue that 'Suggests:' is a better choice as the
relationship is weak; maybe we can do that if the 'Recommends:' is
causing problems.  Or just promote zerofree is no one cares.


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

-- 
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/1275656

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cunit/+bug/1275656/+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 1275656] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
Regarding the missing build dependency, libdumbnet-dev, in main.  This
package was promoted from universe to main for Trusty, the MIR is in bug
#1220950.  The only dependency for libdumbnet-dev or libdumbnet1 is
libc6 which is already in main.

** Attachment added: libdumbnet-dev_deps.png
   
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1275656/+attachment/4124789/+files/libdumbnet-dev_deps.png

-- 
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/1275656

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1275656/+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 1313203] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1313203

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1313203/+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 1300826] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1300826

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1300826/+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 1311453] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1311453

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1311453/+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 1288984] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1288984

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1288984/+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 1318858] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1318858

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1318858/+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 1244855] Re: package open-vm-tools-dkms 2013.09.16-1328054-0ubuntu1 failed to install/upgrade: ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 7

2014-06-03 Thread Robert C Jennings
Oneiric Ocelot reached End-of-Life on May 9th, 2013.  Closing this bug.

** Changed in: open-vm-tools (Ubuntu)
   Status: New = Won't Fix

-- 
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/1244855

Title:
  package open-vm-tools-dkms 2013.09.16-1328054-0ubuntu1 failed to
  install/upgrade: ErrorMessage: podproces zainstalowany skrypt post-
  installation zwrócił kod błędu 7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1244855/+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 1247531] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build. [error: implicit declaration of function ‘d_alloc_root’]

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1247531

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module
  failed to build. [error: implicit declaration of function
  ‘d_alloc_root’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1247531/+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 1268442] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1268442

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1268442/+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 1282078] Re: using update manager opperation stoped during install open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1282078

Title:
  using update manager opperation stoped during install open-vm-dkms
  2011.12.20-562307-0ubuntu1: 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/1282078/+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 1265280] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1265280

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1265280/+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 1289449] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1289449

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1289449/+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 1275523] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1275523

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1275523/+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 1289199] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build

2014-06-03 Thread Robert C Jennings
*** This bug is a duplicate of bug 1083719 ***
https://bugs.launchpad.net/bugs/1083719

** This bug is no longer a duplicate of bug 1247531
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build. [error: implicit declaration of function ‘d_alloc_root’]
** This bug has been marked a duplicate of bug 1083719
   open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed 
to build [error: implicit declaration of function ‘d_alloc_root’]

-- 
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/1289199

Title:
  open-vm-dkms 2011.12.20-562307-0ubuntu1: 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/1289199/+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


  1   2   >