** Changed in: euca2ools
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551847
Title:
Rebundled uec instance boot fail
To manage notifications about this
fixed upstream in r316 http://bazaar.launchpad.net/~eucalyptus-
maintainers/euca2ools/euca2ools-main/revision/316
** Also affects: euca2ools
Importance: Undecided
Status: New
** Changed in: euca2ools
Status: New => Fix Committed
--
Rebundled uec instance boot fail
https://bugs.
This bug was fixed in the package euca2ools - 1.2-0ubuntu10
---
euca2ools (1.2-0ubuntu10) lucid; urgency=low
* euca-bundle-vol: exclude persistent udev net device rules LP: #551847
-- Scott MoserWed, 14 Apr 2010 16:42:22 -0400
** Changed in: euca2ools (Ubuntu Lucid)
Sta
** Changed in: euca2ools (Ubuntu Lucid)
Assignee: Scott Moser (smoser) => (unassigned)
** Changed in: euca2ools (Ubuntu Lucid)
Status: Confirmed => In Progress
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you ar
Quoting nurmi:
| As discussed this morning, we don't foresee any problem that would
| come up if this patch were put in place. Neil has looked at the
| patch, and agrees that it will solve this specific problem. In the
| future, several options will likely be explored, ranging from
| modificatio
This is basically bug 308548 fix moved to euca2ools. I've added a
environment variable hack-around in the unlikely event that the user
wishes for /etc/udev/rules.d/70-persistent-net.rules and
/etc/udev/rules.d/z25_persistent-net.rules to be copied to the target.
If thats the case , setting 'EUCA_
I just realized that this same issue was fixed in ec2-bundle-vol in bug
308548 .
As such, it would be in keeping with that to make the same fix to euca-
bundle-vol.
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a mem
The current cloud-init expects that 'eth0' will come up and have the
metadata service on it.
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Just for reference, http://forum.eucalyptus.com/forum/multiple-network-
interface-configuration discusses multiple network interfaces in a
eucalyptus instance. So, simple blacklisting there would possibly,
though unlikely could lead to inconsistent naming (kernel change isn't
going to occur in Euc
** Changed in: euca2ools (Ubuntu Lucid)
Assignee: (unassigned) => Scott Moser (smoser)
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Also affects: euca2ools (Ubuntu Lucid)
Importance: Low
Status: Confirmed
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Fri, 9 Apr 2010, Mathias Gug wrote:
> Kvm uses the same vendor id for mac addresses. Does EC2 use something
> similar? If so we could just blacklist mac addresses to not be written
> to /etc/udev/rules.d/70-persistent-net.rules.
Read the mentioned bug for more information.
--
Rebundled uec i
On Thu, Apr 08, 2010 at 09:08:43PM -, Scott Moser wrote:
>
> a.) cloud-init (or some other package) could possibly add some rules or black
> lists so the persistent-net rules were not written in images where it was
> installed. (I'd have to see if this would be possible)
Kvm uses the same v
I'm changing the importance of this to 'low' given the easy work around
of 'rm etc/udev/rules.d/70-persistent-net.rules'
** Changed in: euca2ools (Ubuntu)
Importance: High => Low
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification beca
Ok, I found the source of this problem. Its really a dupe of bug 341006
, or at very least, a fix to that bug that addressed the MAC addresses
used by UEC would make this problem go away.
The reason there is no output after the kernel in the console above is
that upstart is quietly waiting for et
I can confirm this on beta2 image (20100407.1).
** Changed in: euca2ools (Ubuntu)
Status: New => Confirmed
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this still an issue? Any updates?
How do we reproduce this on the upstream side?
thanks.
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Summary changed:
- uec instance boot fail
+ Rebundled uec instance boot fail
** Changed in: euca2ools (Ubuntu)
Importance: Undecided => High
--
Rebundled uec instance boot fail
https://bugs.launchpad.net/bugs/551847
You received this bug notification because you are a member of Ubuntu
Bug
18 matches
Mail list logo
