I upgraded to Ubuntu 15.10 (wily) with the default kernel 4.2.0-22 and
this problem disappeared. Let me know if any other information would be
helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: main.log
https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+attachment/3752861/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205751
** Attachment added: apt.log
https://bugs.launchpad.net/ubuntu/+source/libxml-sax-perl/+bug/1205751/+attachment/3751710/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205751
Title:
Public bug reported:
Failure upgrading Ubuntu 10.04 to 12.04 with do-release-upgrade
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libxml-sax-perl 0.99+dfsg-1ubuntu0.1
ProcVersionSignature: Ubuntu 2.6.32-46.107-server 2.6.32.60+drm33.26
Uname: Linux 2.6.32-46-server x86_64
I think you mean region and not availability-zone since availability
zone names mean different things for different AWS accounts.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I think you mean region and not availability-zone since availability
zone names mean different things for different AWS accounts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037727
Title:
I get the same mtp-detect output as acunningham on Samsung Galaxy S3,
Ubuntu 12.04.
I followed the instructions in the howto in the bug description above.
When I attempt to access the mounted directory, it hangs a long time
then reports:
ls: cannot access /mnt/android: Transport endpoint is
evfool: Agreed. deb-src is not critical for the most common uses.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997371
Title:
Create command to add multiverse and -backports to apt sources
To
Robert: The program works for multiverse on Lucid, Oneiric, Precise,
though it only adds deb and not deb-src on Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997371
Title:
Create command to
Thanks for the tip!
software-properties-gtk is nice for a desktop system, but on an Ubuntu
server (e.g., EC2 instances) it is not installed by default.
On a fresh Ubuntu 12.04 LTS Precise server I would need to give the
following extra instructions:
sudo apt-get update
sudo apt-get install
Public bug reported:
Based on a discussion at UDS-Q a simple command is desired to be able to
add/enable multiverse and/or -backports in the apt repositories on a
system.
Background: Right now, it is trivial to add a PPA to the apt sources
using the apt-add-repository command. For example, I
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997371
Title:
Create command to add multiverse and -backports to apt sources
To manage notifications about this bug go to:
** Description changed:
Based on a discussion at UDS-Q a simple command is desired to be able to
add/enable multiverse and/or -backports in the apt repositories on a
system.
Background: Right now, it is trivial to add a PPA to the apt sources
using the apt-add-repository command.
Blueprint changed by Eric Hammond:
Whiteboard changed:
Blueprint:https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-awstools
Etherpad: http://pad.ubuntu.com/uds-q-servercloud-awstools
-
- content below copied to Etherpad 2012-04-30, please make updates to
- etherpad
Blueprint changed by Eric Hammond:
Whiteboard changed:
- Ubuntu has packages for only two sets of AWS tools:
+ Ubuntu has packages for some AWS tools:
* EC2 API Tools [package: ec2-api-tools]
* EC2 AMI Tools [package: ec2-ami-tools]
* RDS - Relational Database Service [package
This is the key error:
ALERT! /dev/disk/by-label/cloudimg-rootfs does not exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939212
Title:
AMI created from latest i386 Lucid image fails to
Chetan: Can you provide the commands you are using to bundle the AMI?
ec2-bundle-vol or ec2-bundle-image?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939212
Title:
AMI created from latest i386
Here are a couple posts that reference the issue. It looks like smoser
provided a fixed ec2-bundle-vol:
https://forums.aws.amazon.com/thread.jspa?threadID=58232
https://lists.ubuntu.com/archives/ubuntu-
cloud/2011-January/000477.html
It isn't clear if the patch has made it into the
Scott:
- With the CNAME solution, the requests still go to the internal IP
address for standard EC2 instances.
- I don't imagine that many non-EC2 people would try to configure their
Ubuntu systems to use the EC2 repositories.
- Canonical would get charged the same network fees for people
Scott:
- With the CNAME solution, the requests still go to the internal IP
address for standard EC2 instances.
- I don't imagine that many non-EC2 people would try to configure their
Ubuntu systems to use the EC2 repositories.
- Canonical would get charged the same network fees for people
+1 for cloudcontrol's recommendation to use CNAMEs. I've been
recommending this to Canonical since we were discussing the initial
setup of EC2 dedicated repositories. It would have avoided a couple
issues that have happened since and would help prevent future problems
as AWS releases new
+1 for cloudcontrol's recommendation to use CNAMEs. I've been
recommending this to Canonical since we were discussing the initial
setup of EC2 dedicated repositories. It would have avoided a couple
issues that have happened since and would help prevent future problems
as AWS releases new
Though I don't like the current way Oneiric manages /etc/hosts (and
submitted related bug #890501) I agree with Scott that it is how Oneiric
works on EC2 and changes could cause existing installations to break.
In fact, I have automated system code that works around the bug which
would break if
Though I don't like the current way Oneiric manages /etc/hosts (and
submitted related bug #890501) I agree with Scott that it is how Oneiric
works on EC2 and changes could cause existing installations to break.
In fact, I have automated system code that works around the bug which
would break if
*** This bug is a duplicate of bug 854050 ***
https://bugs.launchpad.net/bugs/854050
Stefan: Thanks for the clarification. It looks like I've been running
3.0.0-14.23 for 16 days and I haven't seen any further issues.
Based on your comment, I'll mark this bug a duplicate of bug #854050.
**
I am unable to reproduce the issue, but haven't been running many
Oneiric AMIs so it may be something that doesn't happen a high
percentage of the time.
If you have found a bug in the code and have created a fix for it, it
seems a shame to not release it.
If you want me to run the new kernel to
Is this bug still on track to be fixed? What is the next step required?
Should it have somebody assigned?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884320
Title:
EC2 oneiric BUG: unable to
Public bug reported:
In bug #892554, Kees Cook (kees) makes a great suggestion that cloud-
init could output the public ssh host keys to the console output. This
could then be read by automated software outside of the instance and
added to a known_hosts file using the IP address and/or hostname
--
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/893400
Title:
cloud-init: Output machine usable public ssh host key (for
known_hosts)
To manage notifications about this bug go
Love the known_hosts suitable output format idea! It doesn't even need
to be an option. Split that off into bug #893400.
The current ticket can remain for adding the ECDSA ssh key fingerprint.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I've ammended the original example to use cat instead of cut as it
looks like the specific number of fields in the key may vary for some
older formats (rsa1) and it removes the objection that I invented
anything. I had been hoping to exclude the comment field, but agree
it's not worth the
** Description changed:
In bug #892554, Kees Cook (kees) makes a great suggestion that cloud-
init could output the public ssh host keys to the console output. This
could then be read by automated software outside of the instance and
added to a known_hosts file using the IP address
Public bug reported:
In bug #892554, Kees Cook (kees) makes a great suggestion that cloud-
init could output the public ssh host keys to the console output. This
could then be read by automated software outside of the instance and
added to a known_hosts file using the IP address and/or hostname
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893400
Title:
cloud-init: Output machine usable public ssh host key (for
known_hosts)
To manage notifications about this bug go to:
Love the known_hosts suitable output format idea! It doesn't even need
to be an option. Split that off into bug #893400.
The current ticket can remain for adding the ECDSA ssh key fingerprint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've ammended the original example to use cat instead of cut as it
looks like the specific number of fields in the key may vary for some
older formats (rsa1) and it removes the objection that I invented
anything. I had been hoping to exclude the comment field, but agree
it's not worth the
** Description changed:
In bug #892554, Kees Cook (kees) makes a great suggestion that cloud-
init could output the public ssh host keys to the console output. This
could then be read by automated software outside of the instance and
added to a known_hosts file using the IP address
** Description changed:
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking
something like:
- 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
+ 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this
--
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/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
To manage notifications about this bug go to:
Public bug reported:
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking
something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more
sense to my internal software (e.g., Apache), say:
Scott: Learn something new every day. I will give this a try.
** Changed in: cloud-init (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in
Scott: Your suggested approach works for me even though I can't find any
documentation on how this is supposed to work. Everything I read says
that 127.0.1.1 should be the canonical hostname of the instance. Do you
happen to have any pointers to the information you are alluding to with
IPv6 and
** Description changed:
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking
something like:
- 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
+ 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
To manage notifications about this bug go to:
Public bug reported:
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking
something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to something that makes more
sense to my internal software (e.g., Apache), say:
Scott: Learn something new every day. I will give this a try.
** Changed in: cloud-init (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890501
Title:
EC2
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
Scott: Your suggested approach works for me even though I can't find any
documentation on how this is supposed to work. Everything I read says
that 127.0.1.1 should be the canonical hostname of the instance. Do you
happen to have any pointers to the information you are alluding to with
IPv6 and
Public bug reported:
I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce
in us-east-1.
About two days later, it became non-responsive
I found the attached kernel stack trace in /var/log/syslog
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package:
** Attachment added: stack-trace.txt
https://bugs.launchpad.net/bugs/884320/+attachment/2580430/+files/stack-trace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884320
Title:
EC2 oneiric
** Description changed:
I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce
in us-east-1.
- About two days later, it became non-responsive
+ About two days later, it became non-responsive to ssh, http, etc.
- I found the attached kernel stack trace in /var/log/syslog
** Description changed:
I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce
in us-east-1.
About two days later, it became non-responsive to ssh, http, etc.
- I found the following kernel oops stack trace in /var/log/syslog:
+ I found the following kernel oops stack
apport information
** Tags added: apport-collected
** Description changed:
I started a new EC2 instance of Ubuntu 11.10 Oneiric using ami-a7f539ce
in us-east-1.
About two days later, it became non-responsive to ssh, http, etc.
I found the following kernel oops stack trace in
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/884320/+attachment/2580465/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/884320/+attachment/2580464/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884320
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/884320/+attachment/2580466/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884320
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/884320/+attachment/2580467/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884320
Title:
EC2
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/884320/+attachment/2580468/+files/UdevLog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I (original requester) suggest the status of this wishlist item be
changed to wontfix now that there is a way for users to build their
own kernels on EC2. Canonical does not need to support multiple kernels
with different frequencies.
--
You received this bug notification because you are a
Public bug reported:
When I start a standard Ubuntu 11.10 Oneiric instance (ami-a7f539ce) on
Amazon EC2 I can ssh in just fine with the default .ssh/authorized_keys
file.
If I prefix the ssh key in .authorized_keys with the option no-pty
then attempts to ssh fail with the error:
PTY
This may also be a problem on non-EC2 Oneiric; I have no way of testing
that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/876168
Title:
EC2 Oneiric ssh no-pty triggers PTY
Closing as invalid. I wasn't testing correctly with a non-pty ssh.
** Changed in: openssh (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/876168
Public bug reported:
When I start a standard Ubuntu 11.10 Oneiric instance (ami-a7f539ce) on
Amazon EC2 I can ssh in just fine with the default .ssh/authorized_keys
file.
If I prefix the ssh key in .authorized_keys with the option no-pty
then attempts to ssh fail with the error:
PTY
This may also be a problem on non-EC2 Oneiric; I have no way of testing
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876168
Title:
EC2 Oneiric ssh no-pty triggers PTY allocation request
Closing as invalid. I wasn't testing correctly with a non-pty ssh.
** Changed in: openssh (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876168
Title:
EC2
Sorry, I should have been clear in the original bug report that I was
submitting it on behalf of Amazon and another customer and did not
experience it myself on that particular instance or AMI.
Also, I'm not sure that lack of a public IP address as described in
#615545 is sufficient to determine
Sorry, I should have been clear in the original bug report that I was
submitting it on behalf of Amazon and another customer and did not
experience it myself on that particular instance or AMI.
Also, I'm not sure that lack of a public IP address as described in
#615545 is sufficient to determine
Amazon recommends fixing this through DNS instead of through software on
the instance.
Instead of resolving eu-west-1.ec2.archive.ubuntu.com directly to an A
record of the internal IP address starting with 10., Canonical should
change it to resolve to a CNAME of the external elastic IP address
Amazon recommends fixing this through DNS instead of through software on
the instance.
Instead of resolving eu-west-1.ec2.archive.ubuntu.com directly to an A
record of the internal IP address starting with 10., Canonical should
change it to resolve to a CNAME of the external elastic IP address
Public bug reported:
DNS names like eu-west-1.ec2.archive.ubuntu.com (apt repository for eu-
west-1 on EC2) are currently resolving to private IP addresses (e.g.,
10.).
An EC2 instance running in VPC cannot access these repositories.
More details and possible fixes at:
--
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/824947
Title:
EC2 apt repository DNS resolution on VPC instances
To manage notifications about this bug go to:
Public bug reported:
DNS names like eu-west-1.ec2.archive.ubuntu.com (apt repository for eu-
west-1 on EC2) are currently resolving to private IP addresses (e.g.,
10.).
An EC2 instance running in VPC cannot access these repositories.
More details and possible fixes at:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824947
Title:
EC2 apt repository DNS resolution on VPC instances
To manage notifications about this bug go to:
Public bug reported:
Binary package hint: cloud-init
The EC2/UEC images currently allow users to ssh to root@ but do not give
the user shell access. Instead, a helpful message is displayed to the
user explaining they need to ssh to ubuntu@ and they are disconnected
after 10 seconds.
This is
--
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/798505
Title:
Tighten permissions on root@ ssh with EC2/UEC images
To manage notifications about this bug go to:
Public bug reported:
Binary package hint: cloud-init
The EC2/UEC images currently allow users to ssh to root@ but do not give
the user shell access. Instead, a helpful message is displayed to the
user explaining they need to ssh to ubuntu@ and they are disconnected
after 10 seconds.
This is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798505
Title:
Tighten permissions on root@ ssh with EC2/UEC images
To manage notifications about this bug go to:
Changing status to Confirmed because others have indicated they are
having the same problem.
** Changed in: apt-listchanges (Ubuntu)
Status: New = Confirmed
** Summary changed:
- Update Manager halts waiting for response to apt-listchanges hidden under
Details
+ Update Manager hangs
Public bug reported:
Binary package hint: apt-listchanges
I have installed the package apt-listchanges.
The Update Manager prompts me to upgrade some packages and I accept.
The Update Manager starts the upgrade and then hangs.
The only way to continue is to have enough knowledge to do the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787802
Title:
Update Manager halts waiting for response to apt-listchanges hidden
under Details
--
ubuntu-bugs mailing list
Since UEC is a specific product and this is used with both UEC and
EC2, should the name be more generic like cloud instead of uec?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768625
Title:
user
Public bug reported:
Binary package hint: console-setup
I have checked Make Caps Lock an additional Ctrl but Natty
occasionally forgets this and the Caps Lock key suddenly functions as a
Caps Lock key.
To fix this I have to go into the keyboard preferences to uncheck and
then recheck Make Caps
** Package changed: console-setup (Ubuntu) = ubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768683
Title:
Natty forgets Make Caps Lock an additional Ctrl
--
ubuntu-bugs
I have no idea what package this falls into. I'm sure it's
miscategorized right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768683
Title:
Natty forgets Make Caps Lock an additional Ctrl
--
In my experience in 2008-2009, just because networking is up on an EC2
instance does not mean that 169.254.169.254 is going to accept
connections and requests for meta-data and user-data. You need to wait
for this to become available. I had code to do this in Ubuntu AMIs I
built back then.
On second glance, cloud-init may actually be retrying the connection and
the problem is that sometimes it takes longer than the current number of
retries.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
In my experience in 2008-2009, just because networking is up on an EC2
instance does not mean that 169.254.169.254 is going to accept
connections and requests for meta-data and user-data. You need to wait
for this to become available. I had code to do this in Ubuntu AMIs I
built back then.
On second glance, cloud-init may actually be retrying the connection and
the problem is that sometimes it takes longer than the current number of
retries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux-ec2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740658
Title:
kernels compiled withCONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
I would like to see a solution like the following for this and other
files generated at startup (e.g., apt sources):
If the user has not modified the file since it was created from a
template, then the system should feel free to continue maintaining that
file by regenerating it from the template
I would like to see a solution like the following for this and other
files generated at startup (e.g., apt sources):
If the user has not modified the file since it was created from a
template, then the system should feel free to continue maintaining that
file by regenerating it from the template
Vlad: Off topic for the bug, but see: http://alestic.com/2009/06/ec2
-elastic-ip-internal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing sun
*** This bug is a duplicate of bug 651370 ***
https://bugs.launchpad.net/bugs/651370
Confirmed with my AWS account using same AMI in eu-west-1 and
m2.2xlarge. Console log attached.
** Changed in: ec2-api-tools (Ubuntu)
Status: New = Confirmed
** Attachment added: console.log
*** This bug is a duplicate of bug 651370 ***
https://bugs.launchpad.net/bugs/651370
** This bug has been marked a duplicate of bug 651370
ec2 kernel crash invalid opcode [#1]
* You can subscribe to bug 651370 by following this link:
*** This bug is a duplicate of bug 651370 ***
https://bugs.launchpad.net/bugs/651370
Confirmed with my AWS account using same AMI in eu-west-1 and
m2.2xlarge. Console log attached.
** Changed in: ec2-api-tools (Ubuntu)
Status: New = Confirmed
** Attachment added: console.log
*** This bug is a duplicate of bug 651370 ***
https://bugs.launchpad.net/bugs/651370
** This bug has been marked a duplicate of bug 651370
ec2 kernel crash invalid opcode [#1]
* You can subscribe to bug 651370 by following this link:
ProRunner: Is there an emoticon for sticking your tongue out at
somebody? :)
--
ec2-fetch-credentials lists ubuntu user in root authorized_keys even if
ec2-config.cfg specifies another
https://bugs.launchpad.net/bugs/506981
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: cloud-init
Attempting to log in to the root user on an Ubuntu AMI returns the
message:
Please login as the ubuntu user rather than root user.
This has two minor problems:
1. There is a missing the before the word root.
2. Adding quotes around the
Public bug reported:
Binary package hint: cloud-init
Attempting to log in to the root user on an Ubuntu AMI returns the
message:
Please login as the ubuntu user rather than root user.
This has two minor problems:
1. There is a missing the before the word root.
2. Adding quotes around the
1 - 100 of 377 matches
Mail list logo
