[Bug 934534] Re: metadata ami-launch-index always returning 1

2012-03-14 Thread Mike Milner
** Tags added: canonistack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/934534 Title: metadata ami-launch-index always returning 1 To manage notifications about this bug go to:

[Bug 934534] Re: metadata ami-launch-index always returning 1

2012-03-14 Thread Mike Milner
** Tags added: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934534 Title: metadata ami-launch-index always returning 1 To manage notifications about this bug go to:

[Bug 934534] Re: metadata ami-launch-index always returning 1

2012-02-22 Thread Mike Milner
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) = Mike Milner (milner) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs

[Bug 934534] Re: metadata ami-launch-index always returning 1

2012-02-22 Thread Mike Milner
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) = Mike Milner (milner) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934534 Title

[Bug 934534] Re: metadata ami-launch-index coming back off-by-one

2012-02-20 Thread Mike Milner
I've confirmed this also affects launching multiple instances in one call. Every instance will have an ami-launch index of 1. Looking through the code I believe this comes from the following function in nova/compute/api.py : def create_db_entry_for_new_instance(self, context, instance_type,

[Bug 934534] Re: metadata ami-launch-index coming back off-by-one

2012-02-20 Thread Mike Milner
I've confirmed this also affects launching multiple instances in one call. Every instance will have an ami-launch index of 1. Looking through the code I believe this comes from the following function in nova/compute/api.py : def create_db_entry_for_new_instance(self, context, instance_type,

[Bug 730047] Re: landscape-sysinfo crashed with IOError in _open(): [Errno 30] Read-only file system: '/var/log/landscape/sysinfo.log'

2011-11-09 Thread Mike Milner
** Changed in: landscape-client Assignee: Kevin McDermott (bigkevmcd) = (unassigned) ** Changed in: landscape-client Milestone: None = backlog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 268348] Re: reconfiguring the landscape-client package does not register the client

2011-10-04 Thread Mike Milner
** Changed in: landscape-client Milestone: None = backlog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/268348 Title: reconfiguring the landscape-client package does not register the client

[Bug 268351] Re: reconfiguring landscape-client should ask if it should reregister

2011-10-04 Thread Mike Milner
** Changed in: landscape-client Milestone: None = backlog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/268351 Title: reconfiguring landscape-client should ask if it should reregister To