[Bug 1037727] Re: support adding region/availability to mirror selection
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. https://bugs.launchpad.net/bugs/1037727 Title: support adding region/availability to mirror selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1037727/+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
[Blueprint servercloud-q-awstools] Package (more) AWS tools for Ubuntu
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 --- - - 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: rdscli] - * IAM - Identity and Access Management [package: iamcli] - - If we want Ubuntu to be the easiest distro for use with the biggest and - most popular public cloud, then there are a number of other important - AWS tool sets that we need to have packaged for easy installation in - Ubuntu when using AWS services, including: - - * ELB - Elastic Load Balancing - http://aws.amazon.com/developertools/2536 - [packaged as 'elbcli' in ppa:awstools-dev/awstools] - * aws-cloudformation-cli - [packaged as 'aws-cloudformation-cli' in ppa:awstools-dev/aws-cloudformation-cli] - * Auto Scaling - http://aws.amazon.com/developertools/2535 - * CloudWatch - http://aws.amazon.com/developertools/2534 - * ElastiCache - http://aws.amazon.com/developertools/Amazon-ElastiCache/2310261897259567 - * AWS Import/Export - http://aws.amazon.com/importexport/tools/ - * EMR - Elastic MapReduce - http://aws.amazon.com/developertools/Elastic-MapReduce/2264 - * CloudSearch - http://aws.amazon.com/developertools/9054800585729911 - * CloudFront - ? http://aws.amazon.com/code/CloudFront - * Route53 - ? - * etc. - - If all of these can't be supported, then prioritize the important ones - with user feedback and start working on getting them into Ubuntu, or at - least into a PPA. - - Note: Scott Moser has started an awstools team and PPA which can be used - for this purpose, but there have not been sufficient resources applied - to date in adding and updating all of the important tools: - https://launchpad.net/~awstools-dev/+archive/awstools - - Generally, I think I've got a reasonably easily copied [template] in - rdscli for the aws java tools. -- Package (more) AWS tools for Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-awstools -- 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
[Blueprint servercloud-q-awstools] Package (more) AWS tools for Ubuntu
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: rdscli] * IAM - Identity and Access Management [package: iamcli] If we want Ubuntu to be the easiest distro for use with the biggest and most popular public cloud, then there are a number of other important AWS tool sets that we need to have packaged for easy installation in Ubuntu when using AWS services, including: * ELB - Elastic Load Balancing - http://aws.amazon.com/developertools/2536 [packaged as 'elbcli' in ppa:awstools-dev/awstools] * aws-cloudformation-cli [packaged as 'aws-cloudformation-cli' in ppa:awstools-dev/aws-cloudformation-cli] * Auto Scaling - http://aws.amazon.com/developertools/2535 * CloudWatch - http://aws.amazon.com/developertools/2534 * ElastiCache - http://aws.amazon.com/developertools/Amazon-ElastiCache/2310261897259567 * AWS Import/Export - http://aws.amazon.com/importexport/tools/ * EMR - Elastic MapReduce - http://aws.amazon.com/developertools/Elastic-MapReduce/2264 * CloudSearch - http://aws.amazon.com/developertools/9054800585729911 * CloudFront - ? http://aws.amazon.com/code/CloudFront * Route53 - ? * etc. If all of these can't be supported, then prioritize the important ones with user feedback and start working on getting them into Ubuntu, or at least into a PPA. Note: Scott Moser has started an awstools team and PPA which can be used for this purpose, but there have not been sufficient resources applied to date in adding and updating all of the important tools: https://launchpad.net/~awstools-dev/+archive/awstools Generally, I think I've got a reasonably easily copied [template] in rdscli for the aws java tools. -- Package (more) AWS tools for Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-awstools -- 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 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
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 outside of EC2 using the S3 solution as using the CNAME solution. - The CNAME method only requires a change to entries in Canonical's DNS servers, no action is required with SRUs and updates to AMIs. The only objection I've heard that makes sense is a concern about the risk of increase in cost from use by non-EC2 instances, but it sounds like Canonical is already willing to take that risk with the S3 solution. This decision doesn't affect me personally. It just seems CNAME is the right approach and I'm not sure why it is not being adopted. -- 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/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+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 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
+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 features. Amazon has also recommended 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/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+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 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems
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 the behavior were fixed. Not horrible for me personally, but I don't know how many might be in a similar situation. -- 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/871966 Title: FQDN written to /etc/hosts causes problems for clustering systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/871966/+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 893400] [NEW] cloud-init: Output machine usable public ssh host key (for known_hosts)
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 that the remote system wishes to use to connect to the instance. As Scott Moser (smoser) points out, the existing ssh host key fingerprints should be left in the output in the current de facto standard format so as to not break any existing software or human processes that check this. The new output should be added using a different set of public ssh host key delimiters (see proposed format below). There is no need to require a cloud-init configuration option; this information should always be output. Extra information in the console output should not interfere with any existing programs as long as it is separate from the existing formatted information. The simplest way to present the information might be to just print out the first two fields of all public host keys. For example: cut -f1-2 -d' ' /etc/ssh/ssh_host_*_key.pub The client system would query the console output, select one of these ssh host keys, and add it to known_hosts, prepended by the IP address and/or hostnames that it wishes to use to connect to the instance. Here's an example of what this might look like in the console output: -BEGIN PUBLIC SSH HOST KEYS- ssh-dss B3NzaC1kc3MAAACBAOx12z6/snxt5HWbRZNmvs/hH+5EXsLLKR4XnyH56EQFNmpxGy3O5qBNvNpt4GejLmFR6TJdMANwFhkOfUkLcotTpgm+z3nA4wFUZt23o2CjYvqHSx5pOON390XM6xHhXzlGlkip5XUVM4flNhwQNAvt+9bo3//OTtXEZ1ZZ2M8bFQDiJIlHJxNS2jOsiHIsm5g3Vl5JuwAAAIEAiZXdnPnupHa5EvqAmaa0Gdzqp1mcRm7a/ovQ/Oko/IByF0OqAEZtb3VevUOoC1HFBoYfcP1kRKdey/W7TyLJPYWt/ZuMdNmZSuPZt7U99WkRt+sGfOlTc2PnxbKzbC+dqcBpuVvjy7AJEngucUJ8lykrpR30Fo538KkSHcITf+QAAACBAONcYr7hoksk3BhtvxFKjXoqcwBiDxAuj+aq90oWsenWfStuOO84eg1tJhZNp0VFv9mICevICoY4P+3ZjD7SvTdq5Xk3Uw4wabgFE4rBwS4XrZMA9+O9/S8+b20h+pQSbfwZIZiULTjBP2I89acPExhmrApSpZ+ByqB3HvnKawG+ ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= ssh-rsa B3NzaC1yc2EDAQABAAABAQC0I3L8UiDoF4LkzpJNHBDM2w9JFE6CbvmAQgW6+czbDOwvrFxQU2rw2HLLUOn+Z2WCE5AJSY7E7pxCrDo1v27hkVgaM6KqWks74vYxIkqfGCyf31y1N8QrmVCsAC74KFp9rhwP0uHmrN8XUIYFik8MoNphf+2aKWieJdZtzQGQ22mNNKDkP1yX3Uvb1QI+8d770dcIqr61AwkUBQgPgPyeii8W7r2+nq1lNQEnYts0N+13+40lEShnrRtsdKY6diEVs2uQId7VWw04lXOzWGi8oSWlunDWyRCQPtfvBFQtJ8AsivyZjmBuN9VJSDHLY1EQhXayygKfi6u6GKFVLZmd -END PUBLIC SSH HOST KEYS- And here's an example of what the client system might add to known_hosts: 50.16.12.209,ec2-50-16-12-209.compute-1.amazonaws.com ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= or with hashing: |1|q0CnRd/EVpfAXEVMAi7fqx0lFaI=|8BrFOu2+GGRMKDS+1WiVG8xpwt0= ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 22 00:12:40 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric -- 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 to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/893400/+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 893400] Re: cloud-init: Output machine usable public ssh host key (for known_hosts)
-- 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 to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/893400/+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 892554] Re: SSH keys summary does not report ECDSA key
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 subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/892554 Title: SSH keys summary does not report ECDSA key To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/892554/+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 893400] Re: cloud-init: Output machine usable public ssh host key (for known_hosts)
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 effort/risk. The man page for sshd(8) documents the format for /etc/ssh/ssh_known_hosts and ~/.ssh/known_hosts in the SSH_KNOWN_HOSTS FILE FORMAT section. It includes the paragraphs: Bits, exponent, and modulus are taken directly from the RSA host key; they can be obtained, for example, from /etc/ssh/ssh_host_key.pub. The optional comment field continues to the end of the line, and is not used. and:: [generate lines in known_hosts] by a script, ssh-keyscan(1) or by taking /etc/ssh/ssh_host_key.pub and adding the host names at the front. I suppose you could copy the information out of these files using ssh- keygen, but it converts the key to a different format. I lean towards copying the public key file directly because: - It's easier to find and manipulate single lines in the console output, instead of the multi-line output of ssh-keygen. - The public key file contains exactly the format that we will drop into known_hosts, instead of having to convert the output of ssh-keygen back into something usable. (I'm not even sure what tool you use to do that, though on experimentation it looks like it's a process of cutting out headers, reassembling lines and adding the appropriate keytype string.) -- 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 to: https://bugs.launchpad.net/cloud-init/+bug/893400/+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 893400] Re: cloud-init: Output machine usable public ssh host key (for known_hosts)
** 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 and/or hostname that the remote system wishes to use to connect to the instance. As Scott Moser (smoser) points out, the existing ssh host key fingerprints should be left in the output in the current de facto standard format so as to not break any existing software or human processes that check this. The new output should be added using a different set of public ssh host key delimiters (see proposed format below). There is no need to require a cloud-init configuration option; this information should always be output. Extra information in the console output should not interfere with any existing programs as long as it is separate from the existing formatted information. - The simplest way to present the information might be to just print out - the first two fields of all public host keys. For example: + The simplest way to present the information might be to just output the + contents of all public host keys. For example: - cut -f1-2 -d' ' /etc/ssh/ssh_host_*_key.pub + cat /etc/ssh/ssh_host_*_key.pub The client system would query the console output, select one of these ssh host keys, and add it to known_hosts, prepended by the IP address and/or hostnames that it wishes to use to connect to the instance. Here's an example of what this might look like in the console output: -BEGIN PUBLIC SSH HOST KEYS- - ssh-dss B3NzaC1kc3MAAACBAOx12z6/snxt5HWbRZNmvs/hH+5EXsLLKR4XnyH56EQFNmpxGy3O5qBNvNpt4GejLmFR6TJdMANwFhkOfUkLcotTpgm+z3nA4wFUZt23o2CjYvqHSx5pOON390XM6xHhXzlGlkip5XUVM4flNhwQNAvt+9bo3//OTtXEZ1ZZ2M8bFQDiJIlHJxNS2jOsiHIsm5g3Vl5JuwAAAIEAiZXdnPnupHa5EvqAmaa0Gdzqp1mcRm7a/ovQ/Oko/IByF0OqAEZtb3VevUOoC1HFBoYfcP1kRKdey/W7TyLJPYWt/ZuMdNmZSuPZt7U99WkRt+sGfOlTc2PnxbKzbC+dqcBpuVvjy7AJEngucUJ8lykrpR30Fo538KkSHcITf+QAAACBAONcYr7hoksk3BhtvxFKjXoqcwBiDxAuj+aq90oWsenWfStuOO84eg1tJhZNp0VFv9mICevICoY4P+3ZjD7SvTdq5Xk3Uw4wabgFE4rBwS4XrZMA9+O9/S8+b20h+pQSbfwZIZiULTjBP2I89acPExhmrApSpZ+ByqB3HvnKawG+ - ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= - ssh-rsa B3NzaC1yc2EDAQABAAABAQC0I3L8UiDoF4LkzpJNHBDM2w9JFE6CbvmAQgW6+czbDOwvrFxQU2rw2HLLUOn+Z2WCE5AJSY7E7pxCrDo1v27hkVgaM6KqWks74vYxIkqfGCyf31y1N8QrmVCsAC74KFp9rhwP0uHmrN8XUIYFik8MoNphf+2aKWieJdZtzQGQ22mNNKDkP1yX3Uvb1QI+8d770dcIqr61AwkUBQgPgPyeii8W7r2+nq1lNQEnYts0N+13+40lEShnrRtsdKY6diEVs2uQId7VWw04lXOzWGi8oSWlunDWyRCQPtfvBFQtJ8AsivyZjmBuN9VJSDHLY1EQhXayygKfi6u6GKFVLZmd + ssh-dss B3NzaC1kc3MAAACBAOx12z6/snxt5HWbRZNmvs/hH+5EXsLLKR4XnyH56EQFNmpxGy3O5qBNvNpt4GejLmFR6TJdMANwFhkOfUkLcotTpgm+z3nA4wFUZt23o2CjYvqHSx5pOON390XM6xHhXzlGlkip5XUVM4flNhwQNAvt+9bo3//OTtXEZ1ZZ2M8bFQDiJIlHJxNS2jOsiHIsm5g3Vl5JuwAAAIEAiZXdnPnupHa5EvqAmaa0Gdzqp1mcRm7a/ovQ/Oko/IByF0OqAEZtb3VevUOoC1HFBoYfcP1kRKdey/W7TyLJPYWt/ZuMdNmZSuPZt7U99WkRt+sGfOlTc2PnxbKzbC+dqcBpuVvjy7AJEngucUJ8lykrpR30Fo538KkSHcITf+QAAACBAONcYr7hoksk3BhtvxFKjXoqcwBiDxAuj+aq90oWsenWfStuOO84eg1tJhZNp0VFv9mICevICoY4P+3ZjD7SvTdq5Xk3Uw4wabgFE4rBwS4XrZMA9+O9/S8+b20h+pQSbfwZIZiULTjBP2I89acPExhmrApSpZ+ByqB3HvnKawG+ root@ip-10-32-30-193 + ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= root@ip-10-32-30-193 + ssh-rsa B3NzaC1yc2EDAQABAAABAQC0I3L8UiDoF4LkzpJNHBDM2w9JFE6CbvmAQgW6+czbDOwvrFxQU2rw2HLLUOn+Z2WCE5AJSY7E7pxCrDo1v27hkVgaM6KqWks74vYxIkqfGCyf31y1N8QrmVCsAC74KFp9rhwP0uHmrN8XUIYFik8MoNphf+2aKWieJdZtzQGQ22mNNKDkP1yX3Uvb1QI+8d770dcIqr61AwkUBQgPgPyeii8W7r2+nq1lNQEnYts0N+13+40lEShnrRtsdKY6diEVs2uQId7VWw04lXOzWGi8oSWlunDWyRCQPtfvBFQtJ8AsivyZjmBuN9VJSDHLY1EQhXayygKfi6u6GKFVLZmd root@ip-10-32-30-193 -END PUBLIC SSH HOST KEYS- And here's an example of what the client system might add to known_hosts: 50.16.12.209,ec2-50-16-12-209.compute-1.amazonaws.com ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= + root@ip-10-32-30-193 or with hashing: |1|q0CnRd/EVpfAXEVMAi7fqx0lFaI=|8BrFOu2+GGRMKDS+1WiVG8xpwt0= ecdsa- sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBD3aGodGnmPfXEWBRKKVW/zkKP+vC/HPBmNg87gcLLx+WwT7UQgKxsZXVWhccs2BEwbvik/dlfcQX1Zby0ZSYgQ= + root@ip-10-32-30-193 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 22 00:12:40 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest:
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
** 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 value to something that makes more sense to my internal software (e.g., Apache), say: - 127.0.1.1 myhost.example.com myhost + 127.0.1.1 myhost.example.com myhost BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run. The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone. If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value. Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same. - See also #371936 where a similar bug was fixed back in 2009. Figure out - if there is some reason that this part of the system is fragile and + See also bug #371936 where a similar bug was fixed back in 2009. Figure + out if there is some reason that this part of the system is fragile and prone to breaking. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 15 00:17:46 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking - something like: + When running an EC2 instance on Ubuntu 11.10 Oneiric, 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: 127.0.1.1 myhost.example.com myhost BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run. The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone. If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value. Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same. See also bug #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 15 00:17:46 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present
[Bug 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
-- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+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 890501] [NEW] EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
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: 127.0.1.1 myhost.example.com myhost BUG: Whenever I reboot the EC2 instance, cloud-init overwrites my important settings of this value back to the old default. This breaks the startup of my applications on the server as they expect to be able to resolve the names I want set in the /etc/hosts file. Once the user edits the value for 127.0.1.1 in the /etc/hosts file, it should never be overwritten. Not on a reboot. Not on a stop/start (which assigns new IP addresses). Not even when an AMI is built out of this instance and a new instance is run. The user changed that value to something they cared about with reasons we can't assume to trump. It should be left alone. If /etc/hosts does not exist or if 127.0.1.1 is still the same value that cloud-init last set it to, then it *might* be acceptable to overwrite it with a value based on a change in the private IP address, HOWEVER, this might still break the application if software configured itself using the old value. Either never change the value if it exists, or store elsewhere the value that was initially set and only change it if it is still the same. See also #371936 where a similar bug was fixed back in 2009. Figure out if there is some reason that this part of the system is fragile and prone to breaking. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu22 ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Nov 15 00:17:46 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t1.micro Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric -- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+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 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
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. 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+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 890501] Re: EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
** 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 /etc/hosts on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+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 890501] Re: 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 127.0.1.2? -- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/890501/+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 876168] [NEW] EC2 Oneiric ssh no-pty triggers PTY allocation request failed on channel 0
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 allocation request failed on channel 0 This worked fine on previous versions of Ubuntu but the behavior seems to have changed in Oneiric. This failure means that the gitolite package is not working on Ubuntu 11.10 Oneiric as it uses no-pty in the ssh authorized_keys file. Here's a sample of the $HOME/.ssh/authorized_keys file that fails: no-pty ssh-rsa B3NzaC1yc2EBIwAAAQEA6rn8cl41CkzaH4ZBhczOJZaR4xBBDI1Kelc2ivzVvCBTHcdJRWpDd5I5hY5W9qke9Tm4fH3KaUVndlcP0ORGvS3PAL4lTpkS4D4goMEFrwMO8BG0NoE8sf2U/7gaUkdcrDC7jzKYdwleRCI3uibNXiSdeG6RotClAAp7pMflDVp5WjjECDZ+8Jzs2wasdTwQYPhiWSiNcfbfS97QdtROf0AcoPWElZAgmabaDFBlvvzcqxQRjNp/zbpkFHZBSKp+Sm4+WsRuLu6TDe9lb2Ps0xvBp1FTHlJRUVKP2yeZbVioKnOsXcjLfoJ9TEL7EMnPYinBMIE3kAYw3FzZZFeX3Q== ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: ssh (not installed) ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 17 02:54:57 2011 Ec2AMI: ami-a7f539ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m1.small Ec2Kernel: aki-805ea7e9 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric ** Summary changed: - ec2 oneiric ssh no-pty triggers PTY allocation request failed on channel 0 + EC2 Oneiric ssh no-pty triggers PTY allocation request failed on channel 0 -- 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 allocation request failed on channel 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876168/+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 876168] Re: EC2 Oneiric ssh no-pty triggers PTY allocation request failed on channel 0
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 allocation request failed on channel 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876168/+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 876168] Re: EC2 Oneiric ssh no-pty triggers PTY allocation request failed on channel 0
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 Title: EC2 Oneiric ssh no-pty triggers PTY allocation request failed on channel 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/876168/+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 824947] Re: EC2 apt repository DNS resolution on VPC instances
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 if you are in VPC now-a-days. When VPC was launched, all instances were entirely private, but Amazon later released the ability for a VPC instance to have a public IP address with direct Internet access as an optional feature depending on the customer's security policies. Modifying Canonical's DNS seems like the best approach to support current and future AWS services and features. Using a CNAME to an Elastic IP Address transfers the burden to Amazon for determining how the instance should access the apt repository (internal or external). -- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+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 824947] Re: EC2 apt repository DNS resolution on VPC instances
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 hostname (e.g., ec2-NNN-NNN-NNN-NNN.compute-1.amazonaws.com) This will resolve to the internal 10. IP address for normal EC2 instances saving performance and cost, and will resolve to the external elastic IP address for VPC EC2 instances. Making this change not only clears up the issue with VPC, but any other future situation where an EC2 instance cannot access 10. IP addresses and EC2 DNS points it to the external IP address of the apt repository. This approach also makes it easier for Canonical when the apt repository instance gets a new internal IP address (e.g., stop/start, failure). Canonical would simply reassociate the elastic IP address with the new/restarted instance and all DNS would resolve to the correct new IP address without Canonical making any changes to their DNS servers. If Canonical is concerned about the EC2 apt repositories being accessed from outside of EC2 (I wouldn't be, but it's your choice), Amazon recommends the following: To protect the rep from being accessed outside of AWS, lockdown the security group rules to allow only traffic from the public AWS IP ranges (https://forums.aws.amazon.com/ann.jspa?annID=1097) and to the 10. network. Here is a github repository that keeps up to date lists of the EC2 IP address ranges in a format that is easy to parse: https://github.com/garnaat/missingcloud -- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+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 824947] [NEW] EC2 apt repository DNS resolution on VPC instances
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: https://forums.aws.amazon.com/thread.jspa?threadID=73379 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cloud-init 0.6.1-0ubuntu8 ProcVersionSignature: User Name 2.6.38-8.42-virtual 2.6.38.2 Uname: Linux 2.6.38-8-virtual i686 Architecture: i386 Date: Fri Aug 12 03:19:39 2011 Ec2AMI: ami-06ad526f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 natty -- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+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 824947] Re: EC2 apt repository DNS resolution on VPC instances
-- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+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 798505] [NEW] Tighten permissions on root@ ssh with EC2/UEC images
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 done with the following prefix in /root/.ssh/authorized_keys: command=echo 'Please login as the user \ubuntu\ rather than the user \root\.';echo;sleep 10 ssh-rsa ... The goal here is to prevent the user from having any serious access at all through root@ and to just be a helpful pointer for people who assume all EC2 AMIs are set up to allow ssh to root@ Users may change the ssh keys associated with /home/ubuntu/.ssh/authorized_keys and not know about or forget about the fact that there is some access also granted through /root/.ssh/authorized_keys The way that the /root/.ssh/authorized_keys file is currently implemented, an authorized user is blocked from shell access, but is granted some other permissions like doing port forwarding through the instance to anywhere that instance can connect. Hosts it connects to would also perceive the connection as coming from the instance. These additional permissions should be blocked in /root/.ssh/authorized_keys by adding qualifiers like: no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty These particular directives are based on best practices using subversion command= with ssh. The resulting prefix would then look like: command=echo 'Please login as the user \ubuntu\ rather than the user \root\.';echo;sleep 10,no-port-forwarding,no-agent- forwarding,no-X11-forwarding,no-pty ssh-rsa ... See the command= section in man authorized_keys for more details. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cloud-init 0.6.1-0ubuntu8 ProcVersionSignature: User Name 2.6.38-8.42-virtual 2.6.38.2 Uname: Linux 2.6.38-8-virtual i686 Architecture: i386 Date: Fri Jun 17 02:08:02 2011 Ec2AMI: ami-06ad526f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 natty -- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/798505/+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 798505] Re: Tighten permissions on root@ ssh with EC2/UEC images
-- 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: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/798505/+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 745930] Re: cloud-init timeout waiting for metadata service on EC2
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.
perl -MIO::Socket::INET -e 'until(new
IO::Socket::INET(169.254.169.254:80)){sleep 1}'
I used to think I was waiting for networking to come up, but it became
clear that the meta-data service was not listening even some times when
networking was working and I had a local IP address on the instance.
--
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/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
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 745930] Re: cloud-init timeout waiting for metadata service on EC2
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. https://bugs.launchpad.net/bugs/745930 Title: cloud-init timeout waiting for metadata service on EC2 -- 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 720440] Re: /etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl
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 on reboot, instance stop/start, booting of a new instance of an AMI based on an old instance, etc. This could be done by saving a hash or signature of the file after generating it from the template. If the signature no longer matches, then the file should not be overwritten again, but if the signature still matches, then the system should update the file to match the current environment (IP addresses, EC2 region, etc.). I think this solves most of the problems that folks are experiencing with the files not being maintained, while not creating the problems that would be experienced by users who want to manage their own files. -- 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/720440 Title: /etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl -- 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 662679] Re: EC2 kernel panic at boot with 34GB RAM
*** 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 https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/662679/+attachment/1728350/+files/console.log ** Changed in: ec2-api-tools (Ubuntu) Status: Confirmed = New ** Tags added: ec2-images ** Also affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-ec2 (Ubuntu) Status: New = Confirmed ** Changed in: ec2-api-tools (Ubuntu) Status: New = Invalid -- EC2 kernel panic at boot with 34GB RAM https://bugs.launchpad.net/bugs/662679 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-api-tools in ubuntu. -- 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 662679] Re: EC2 kernel panic at boot with 34GB RAM
*** 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651370/+subscribe -- EC2 kernel panic at boot with 34GB RAM https://bugs.launchpad.net/bugs/662679 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-api-tools in ubuntu. -- 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 672417] [NEW] Correct grammar, punctuation in root authorized_keys message on EC2
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 usernames would reduce confusion (see https://bugs.launchpad.net/ubuntu/+source/ec2-init/+bug/506981/comments/7) Proposed new messaging: Please login as the user ubuntu rather than the user root. or Please login as the ubuntu user rather than the root user. The first one is slightly clearer to me, but both get the message across. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ec2-init (not installed) ProcVersionSignature: User Name 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Sun Nov 7 18:27:51 2010 Ec2AMI: ami-508c7839 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: m1.small Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 maverick -- Correct grammar, punctuation in root authorized_keys message on EC2 https://bugs.launchpad.net/bugs/672417 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in ubuntu. -- 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 665235] Re: attaching a volume to maverick instance may boot off it
EBS volumes and snapshots create this sort of problem regularly for me, generally with conflicting duplicate XFS UIDs which I have to override. The best solution for EC2 AMIs may be to always accept that /dev/sda1 is the boot disk. -- attaching a volume to maverick instance may boot off it https://bugs.launchpad.net/bugs/665235 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in ubuntu. -- 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 664083] Re: package missing ec2-describe-tags
*** This bug is a duplicate of bug 649742 *** https://bugs.launchpad.net/bugs/649742 This is simply a software version issue. The ec2-describe-tags is in the ec2-api-tools version 1.3-57419, but that version is not available on Ubuntu 10.04 at this time. The latest version on Ubuntu 10.04 is 1.3-46266 which correctly does not include ec2-describe-tags. This bug might be replaced by a request to upgrade the ec2-api-tools software package on Ubuntu 10.04. -- package missing ec2-describe-tags https://bugs.launchpad.net/bugs/664083 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-api-tools in ubuntu. -- 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 583542] Re: ssh server doesn't start when irrelevant filesystems are not available
This is especially important for remotely controlled servers which have no console access (e.g., Amazon EC2). -- ssh server doesn't start when irrelevant filesystems are not available https://bugs.launchpad.net/bugs/583542 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 502490] Re: ec2-init overwrites user/vmbuilder provided /etc/apt/sources.list
Scott: Is this fixed in Karmic or just Lucid? -- ec2-init overwrites user/vmbuilder provided /etc/apt/sources.list https://bugs.launchpad.net/bugs/502490 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 505482] Re: euca-bundle-vol dies with Invalid cert
Scott: Thanks for checking. The original AMI no longer exists, and I am also unable to reproduce this on the latest Lucid daily: ami-e9b95680 ubuntu-images-testing-us/ubuntu-lucid-daily-i386-server-20100301.manifest.xml I have marked the bug invalid. ** Changed in: euca2ools (Ubuntu) Status: Incomplete = Invalid -- euca-bundle-vol dies with Invalid cert https://bugs.launchpad.net/bugs/505482 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 505482] [NEW] euca-bundle-vol dies with Invalid cert
Public bug reported: Binary package hint: euca2ools On a fresh copy of the latest 32-bit Ubuntu Lucid daily AMI ami-6a28c503 ubuntu-images-testing-us/ubuntu-lucid-daily-i386-desktop-20100110.manifest.xml I installed a copy of ec2-ami-tools (to get the EC2 certificate) echo deb http://us.ec2.archive.ubuntu.com/ubuntu/ lucid multiverse | sudo tee /etc/apt/sources.list.d/multiverse.list /dev/null sudo apt-get update sudo apt-get install -y ec2-ami-tools And then I ran the following euca2ools command: sudo -E euca-bundle-vol \ -r $arch \ -d /mnt \ -p $prefix \ -u $AWS_USER_ID \ -k /mnt/pk-*.pem \ -c /mnt/cert-*.pem \ -s 10240 \ -e /mnt,/root/.ssh,/home/ubuntu/.ssh \ --ec2cert /etc/ec2/amitools/cert-ec2.pem This failed with the simple error: Invalid cert Unfortunately, it's not telling me what cert is invalid. When I leave off the --ec2cert option, it still gives the same error. This exact same process works fine on an Ubuntu 9.10 Karmic AMI like ami-1515f67c ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml This problem is preventing me from completing the testing of the fix in bug 479823. ProblemType: Bug Architecture: i386 Date: Sun Jan 10 13:39:54 2010 DistroRelease: Ubuntu 10.04 Ec2AMI: ami-6a28c503 Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-lucid-daily-i386-desktop-20100110.manifest.xml Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-60cb2609 Ec2Ramdisk: ari-e629c48f Package: euca2ools 1.1~bzr238-0ubuntu2 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 2.6.32-301.4-ec2 SourcePackage: euca2ools Tags: lucid ec2-images Uname: Linux 2.6.32-301-ec2 i686 ** Affects: euca2ools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 lucid -- euca-bundle-vol dies with Invalid cert https://bugs.launchpad.net/bugs/505482 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 505482] Re: euca-bundle-vol dies with Invalid cert
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37676678/Dependencies.txt ** Description changed: Binary package hint: euca2ools On a fresh copy of the latest 32-bit Ubuntu Lucid daily AMI - ami-6a28c503 - ubuntu-images-testing-us/ubuntu-lucid-daily-i386-desktop-20100110.manifest.xml + ami-6a28c503 + ubuntu-images-testing-us/ubuntu-lucid-daily-i386-desktop-20100110.manifest.xml I installed a copy of ec2-ami-tools (to get the EC2 certificate) - echo deb http://us.ec2.archive.ubuntu.com/ubuntu/ $codename multiverse | - sudo tee /etc/apt/sources.list.d/multiverse.list /dev/null - sudo apt-get update sudo apt-get install -y ec2-ami-tools + echo deb http://us.ec2.archive.ubuntu.com/ubuntu/ lucid multiverse | + sudo tee /etc/apt/sources.list.d/multiverse.list /dev/null + sudo apt-get update sudo apt-get install -y ec2-ami-tools And then I ran the following euca2ools command: - sudo -E euca-bundle-vol \ - -r $arch \ - -d /mnt \ - -p $prefix \ - -u $AWS_USER_ID \ - -k /mnt/pk-*.pem \ - -c /mnt/cert-*.pem \ - -s 10240 \ - -e /mnt,/root/.ssh,/home/ubuntu/.ssh \ - --ec2cert /etc/ec2/amitools/cert-ec2.pem + sudo -E euca-bundle-vol \ + -r $arch \ + -d /mnt \ + -p $prefix \ + -u $AWS_USER_ID \ + -k /mnt/pk-*.pem \ + -c /mnt/cert-*.pem \ + -s 10240 \ + -e /mnt,/root/.ssh,/home/ubuntu/.ssh \ + --ec2cert /etc/ec2/amitools/cert-ec2.pem This failed with the simple error: - Invalid cert + Invalid cert Unfortunately, it's not telling me what cert is invalid. When I leave off the --ec2cert option, it still gives the same error. This exact same process works fine on an Ubuntu 9.10 Karmic AMI like - ami-1515f67c - ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml + ami-1515f67c + ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml This problem is preventing me from completing the testing of the fix in bug 479823. ProblemType: Bug Architecture: i386 Date: Sun Jan 10 13:39:54 2010 DistroRelease: Ubuntu 10.04 Ec2AMI: ami-6a28c503 Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-lucid-daily-i386-desktop-20100110.manifest.xml Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-60cb2609 Ec2Ramdisk: ari-e629c48f Package: euca2ools 1.1~bzr238-0ubuntu2 PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: User Name 2.6.32-301.4-ec2 SourcePackage: euca2ools Tags: lucid ec2-images Uname: Linux 2.6.32-301-ec2 i686 -- euca-bundle-vol dies with Invalid cert https://bugs.launchpad.net/bugs/505482 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 479823] Re: euca2ools: euca-bundle-vol strips leading zero (0) from user id
I tried to test the fix, but ran into bug 505482. -- euca2ools: euca-bundle-vol strips leading zero (0) from user id https://bugs.launchpad.net/bugs/479823 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 502495] Re: Too much image copying when using vmbuilder for EC2
For reference, this article enumerates the steps I took to run vmbuilder: http://alestic.com/2010/01/vmbuilder-ebs-boot-ami -- Too much image copying when using vmbuilder for EC2 https://bugs.launchpad.net/bugs/502495 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 502495] [NEW] Too much image copying when using vmbuilder for EC2
Public bug reported: I'm using the latest lp:vmbuilder source to build EBS boot AMIs for EC2. I noticed that there is an awful lot of image file copying being done which seems unnecessary when using vmbuilder for this purpose. 1. vmbuilder installs the image files into a temporary root subdirectory 2. The root subdirectory is copied with rsync into the target directory, which is a loopback filesystem on a huge root.img temporary file. 3. The big root.img file is copied with cp from the temporary directory to a destination directory. 4. I then have to mount this image file and copy the files a fourth time onto the EBS volume in order to create an EBS boot AMI. Ideally, three of these steps could be eliminated so that the image files are installed directly onto the EBS volume, with the path provided through an option. Though this does not affect the functionality in a major way, the current four copies take up a good chunk of time, IO, and disk space when building AMIs on EC2. Parts of the vmbuilder log file for reference: 2010-01-03 00:34:01,285 DEBUG : ['/usr/bin/kvm-img', 'create', '-f', 'raw', '/mnt/vmbuilderw8mCwo/root.img', '10240M'] 2010-01-03 00:34:09,061 DEBUG : ['mount', '-o', 'loop', '/mnt/vmbuilderw8mCwo/root.img', '/mnt/vmbuilderw8mCwo/target/'] [...] 2010-01-03 00:40:13,684 DEBUG : ['rsync', '-aHA', '/mnt/vmbuilderw8mCwo/root/', '/mnt/vmbuilderw8mCwo/target'] [...] 2010-01-03 00:40:32,288 DEBUG : ['cp', '--sparse=always', '/mnt/vmbuilderw8mCwo/root.img', '/mnt/dest-karmic-20100103-0033/root.img'] ProblemType: Bug Architecture: i386 Date: Sun Jan 3 00:47:11 2010 DistroRelease: Ubuntu 9.10 Ec2AMI: ami-1515f67c Ec2AMIManifest: ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml Ec2AvailabilityZone: us-east-1a Ec2InstanceType: c1.medium Ec2Kernel: aki-5f15f636 Ec2Ramdisk: ari-0915f660 Package: ubuntu-vm-builder (not installed) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 2.6.31-302.7-ec2 SourcePackage: vm-builder Tags: ec2-images Uname: Linux 2.6.31-302-ec2 i686 ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 -- Too much image copying when using vmbuilder for EC2 https://bugs.launchpad.net/bugs/502495 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 493510] [NEW] vmbuilder: Creates mostly empty EC2 images on 64-bit
Public bug reported:
I'm using vmbuilder on 32-bit and 64-bit EC2 instances with identical
arguments except for --arch, --kernel, and --ramdisk. The 32-bit EC2
images are created fine, but the 64-bit images are practically empty
except for a few /var directories.
I have tracked this down to the extra mount which is performed by
vmbuilder when run on the 64-bit instance to generate a 64-bit image:
2009-12-07 07:58:23,638 INFO: Mounting target filesystems
2009-12-07 07:58:23,638 DEBUG : Mounting /
2009-12-07 07:58:23,639 DEBUG : ['mount', '-o', 'loop',
'/mnt/vmbuilderDscdmG/root.img', '/mnt/vmbuilderDscdmG/target/']
2009-12-07 07:58:23,719 DEBUG : Creating /var/run in root filesystem
2009-12-07 07:58:23,720 DEBUG : Creating /var/lock in root filesystem
2009-12-07 07:58:23,720 DEBUG : Mounting /
2009-12-07 07:58:23,720 DEBUG : ['mount', '-o', 'loop',
'/mnt/vmbuilderDscdmG/root_.img', '/mnt/vmbuilderDscdmG/target/']
2009-12-07 07:58:23,728 DEBUG : Creating /var/run in root filesystem
2009-12-07 07:58:23,729 DEBUG : Creating /var/lock in root filesystem
2009-12-07 07:58:23,730 DEBUG : Mounting /mnt
2009-12-07 07:58:23,730 DEBUG : ['mount', '-o', 'loop',
'/mnt/vmbuilderDscdmG/.img', '/mnt/vmbuilderDscdmG/target/mnt']
2009-12-07 07:58:23,739 INFO: Installing guest operating system. This might
take some time...
The first mount of / is for the root.img file which is eventually used
to create the actual EC2 image. Unfortunately, the second mount of
root_.img on top of / causes everything to be written to root_.img
which is never used to create the bundle.
Here is the ec2-bundle-image command which shows that it is looking for
the system files in root.img, and not root_.img (which is where they
were placed because of the second mount above):
2009-12-07 08:03:29,471 DEBUG : ['ec2-bundle-image', '--image', '/mnt
/dest-karmic-20091207-0758/root.img', '--cert', '/mnt/cert-XXX.pem', '--
privatekey', '/mnt/pk-XXX.pem', '--user', 'XXX', '--prefix',
'ubuntu-9.10-karmic-x86_64--20091207-0758', '-r', 'x86_64',
'-d', '/mnt/vmbuilderDscdmG', '--kernel', 'aki-fd15f694', '--ramdisk',
'ari-c515f6ac']
This problem is currently making it impossible for me to generate 64-bit
EC2 images.
Here is the vmbuilder command I am running. It works on 32-bit with
only the obvious slight modifications:
sudo vmbuilder/vmbuilder xen ubuntu \
--suite=karmic\
--arch=amd64\
--dest=/mnt/dest-karmic-20091207-0758 \
--tmp=/mnt \
--ec2\
--ec2-version=$description \
--manifest=/mnt/$prefix \
--lock-user \
--components=main,restricted,universe,multiverse \
--part=part-${arch}.txt \
--ec2-bundle \
--ec2-upload \
--ec2-register \
--ec2-bucket=$bucket \
--ec2-prefix=$prefix \
--ec2-user=$AWS_USER_ID \
--ec2-cert=$cert \
--ec2-key=$pk\
--ec2-access-key=$AWS_ACCESS_KEY_ID \
--ec2-secret-key=$AWS_SECRET_ACCESS_KEY \
--ec2-kernel=aki-fd15f694 \
--ec2-ramdisk=ari-c515f6ac \
--install-mirror=http://ec2-us-east-mirror.rightscale.com/ubuntu \
--ppa=alestic/ppa\
--addpkg=runurl \
--addpkg=ncurses-dev \
--addpkg=vim \
--addpkg=zip \
--addpkg=unzip \
--addpkg=libgnutls-dev \
--addpkg=sox \
--addpkg=libsox-fmt-all \
--addpkg=cracklib-runtime\
--addpkg=wamerican \
--addpkg=wbritish\
--addpkg=libstdc++6 \
--addpkg=libcurl3\
--addpkg=libxml2
[Bug 493510] Re: vmbuilder: Creates mostly empty EC2 images on 64-bit
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/36525905/Dependencies.txt -- vmbuilder: Creates mostly empty EC2 images on 64-bit https://bugs.launchpad.net/bugs/493510 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 493510] Re: vmbuilder: Creates mostly empty EC2 images on 64-bit
No sooner entered as a bug than I think I've tracked this down to an invalid part file I was using: root 10240 a1 root 2048 a1 /mnt 1 b Note the extra root entry. I don't know if this can be used to create validation code to prevent other people from making this dumb mistake, but I'm marking this bug invalid now. ** Changed in: vm-builder (Ubuntu) Status: New = Invalid -- vmbuilder: Creates mostly empty EC2 images on 64-bit https://bugs.launchpad.net/bugs/493510 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 493020] Re: vmbuilder: Deletes most of /dev on interrupt
Set to Confirmed since Scott confirmed the bug. Setting to Medium since this seems like a severe impact on a non-core application. ** Changed in: vm-builder (Ubuntu) Status: New = Confirmed ** Changed in: vm-builder (Ubuntu) Importance: Undecided = Medium -- vmbuilder: Deletes most of /dev on interrupt https://bugs.launchpad.net/bugs/493020 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 493020] [NEW] vmbuilder: Deletes most of /dev on interrupt
Public bug reported:
I'm running vmbuilder on the latest EC2 Karmic AMI. When I Ctrl-C
interrupt the run, it deletes almost all of the devices in /dev making
the system somewhat unusable.
Here's a log demonstrating this. I have reproduced the problem on a
fresh AMI by interrupting it in about the same place. Before vmbuilder
was run, there were the usual hundreds of entries in /dev
[...vmbuilder running...]
2009-11-30 01:11:02,430 DEBUG : Setting up linux-image-2.6.31-14-virtual
(2.6.31-14.48) ...
2009-11-30 01:11:03,442 INFO: Running depmod.
2009-11-30 01:11:03,442 INFO: update-initramfs: Generating
/boot/initrd.img-2.6.31-14-server
2009-11-30 01:11:05,466 INFO: cp: cannot stat `/etc/lvm/lvm.conf': No such
file or directory
2009-11-30 01:11:06,471 DEBUG :
2009-11-30 01:11:07,290 DEBUG : Setting up linux-image-2.6.31-15-virtual
(2.6.31-15.50) ...
2009-11-30 01:11:08,302 INFO: Running depmod.
2009-11-30 01:11:08,302 INFO: update-initramfs: Generating
/boot/initrd.img-2.6.31-15-server
2009-11-30 01:11:10,322 INFO: cp: cannot stat `/etc/lvm/lvm.conf': No such
file or directory
2009-11-30 01:11:10,940 INFO: Running depmod.
2009-11-30 01:11:11,220 INFO: update-initramfs: Generating
/boot/initrd.img-2.6.31-302-ec2
2009-11-30 01:11:12,232 DEBUG :
2009-11-30 01:11:12,233 DEBUG : Setting up linux-image-2.6.31-302-ec2
(2.6.31-302.7) ...
2009-11-30 01:11:16,904 INFO: cp: cannot stat `/etc/lvm/lvm.conf': No such
file or directory
^C
ubu...@domu-12-31-39-00-8d-61:~$ ls /dev
pts shm
Here is the command I was running:
sudo vmbuilder/vmbuilder xen ubuntu \
--suite=$codename\
--arch=$arch2\
--dest=$dest \
--tmp=/mnt \
--ec2\
--ec2-version=$description \
--manifest=/mnt/$prefix \
--lock-user \
--components=main,restricted,universe,multiverse \
--part=part-${arch}.txt \
--ec2-bundle \
--ec2-upload \
--ec2-register \
--ec2-bucket=$bucket \
--ec2-prefix=$prefix \
--ec2-user=$AWS_USER_ID \
--ec2-cert=$cert \
--ec2-key=$pk\
--ec2-access-key=$AWS_ACCESS_KEY_ID \
--ec2-secret-key=$AWS_SECRET_ACCESS_KEY \
--ec2-kernel=aki-5f15f636 \
--ec2-ramdisk=ari-0915f660 \
--install-mirror=http://ec2-us-east-mirror.rightscale.com/ubuntu \
--ppa=alestic/ppa\
--addpkg=runurl \
--addpkg=ncurses-dev \
--addpkg=vim \
--addpkg=zip \
--addpkg=unzip \
--addpkg=libgnutls-dev \
--addpkg=sox \
--addpkg=libsox-fmt-all \
--addpkg=cracklib-runtime\
--addpkg=wamerican \
--addpkg=wbritish\
--addpkg=libstdc++6 \
--addpkg=libcurl3\
--addpkg=libxml2 \
--addpkg=collectd\
--execscript=$execscript\
--debug
I verified that /dev was full right before I pushed Ctrl-C and that it
was cleared out right after vmbuilder exited on the interrupt.
Let me know if you are unable to reproduce this problem or need further
information.
ProblemType: Bug
Architecture: i386
Date: Sun Dec 6 00:16:48 2009
DistroRelease: Ubuntu 9.10
Ec2AMI: ami-1515f67c
Ec2AMIManifest:
ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: m1.small
Ec2Kernel: aki-5f15f636
Ec2Ramdisk: ari-0915f660
Package: python-vm-builder 0.11.3-0ubuntu1
[Bug 493020] Re: vmbuilder: Deletes most of /dev on interrupt
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/36488152/Dependencies.txt -- vmbuilder: Deletes most of /dev on interrupt https://bugs.launchpad.net/bugs/493020 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 493020] Re: vmbuilder: Deletes most of /dev on interrupt
On IRC, smoser noted that he had also seen this behavior on nectarine. -- vmbuilder: Deletes most of /dev on interrupt https://bugs.launchpad.net/bugs/493020 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 493020] Re: vmbuilder: Deletes most of /dev on interrupt
In case it matters, I ran ubuntu-bug on the Karmic instance right before I ran the vmbuilder command so that all of the information in this bug would be captured from the system. Attempts to run ubuntu-bug fail after /dev is cleared out. -- vmbuilder: Deletes most of /dev on interrupt https://bugs.launchpad.net/bugs/493020 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 486128] Re: euca2ools: Requires more environment variables than EC2 AMI tools
I agree that given the goals of euca2ools, the default installation of the upstream source should not force AWS-specific options on users. The primary goal of this ticket is to have euca2ools on Ubuntu EC2 AMIs default to AWS/EC2 resources so that when a user runs an Ubuntu AMI, euca2ools commands operate in that environment without further customization. This could be done by setting appropriate environment variables or with appropriate config file settings based on euca2ools enhancements as Scott describes. I'm changing the title of the ticket to reflect the clarified goals. ** Summary changed: - euca2ools: Requires more environment variables than EC2 AMI tools + euca2ools on Ubuntu AMIs should default to using API URLs for EC2/S3 -- euca2ools on Ubuntu AMIs should default to using API URLs for EC2/S3 https://bugs.launchpad.net/bugs/486128 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 486128] Re: euca2ools on Ubuntu AMIs should default to using API URLs for EC2/S3
I'm removing this partly incorrect statement in my original bug report: - euca-register requires setting $EC2_ACCESS_KEY and $EC2_SECRET_KEY instead of also checking $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY_ID as ec2-register does. euca2ools is based on the access key and secret key, while Amazon's EC2 API tools are based on the X.509 certificate and private key. This is a more fundamental incompatibility which I don't expect is going to be changed just to make things seem similar on the surface. If somebody else thinks it should be modified, then it should be a separate bug report. ** Description changed: Binary package hint: euca2ools As I understand it, one of the goals in Ubuntu is for euca2ools to be a drop in replacement for Amazon's EC2 AMI (and API) command line tools. The following are differences where I noticed that I had to set additional environment variables for euca2ools to function properly. - euca-upload-bundle requires setting S3_URL instead of just defaulting to https://s3.amazonaws.com as ec2-upload-bundle does. - euca-register requires setting $EC2_URL instead of defaulting to https://ec2.amazonaws.com as ec2-register does. - - - euca-register requires setting $EC2_ACCESS_KEY and $EC2_SECRET_KEY - instead of also checking $AWS_ACCESS_KEY_ID and - $AWS_SECRET_ACCESS_KEY_ID as ec2-register does. See also: bug 435140 ProblemType: Bug Architecture: i386 Date: Sat Nov 21 01:38:11 2009 DistroRelease: Ubuntu 9.10 Ec2AMI: ami-1515f67c Ec2AMIManifest: ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-5f15f636 Ec2Ramdisk: ari-0915f660 Package: euca2ools 1.0+bzr20091007-0ubuntu1 PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: User Name 2.6.31-302.7-ec2 SourcePackage: euca2ools Tags: ec2-images Uname: Linux 2.6.31-302-ec2 i686 -- euca2ools on Ubuntu AMIs should default to using API URLs for EC2/S3 https://bugs.launchpad.net/bugs/486128 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 486956] [NEW] vmbuilder: --ec2-bundle triggers AttributeError: 'Ubuntu' object has no attribute 'suite'
Public bug reported:
This problem happens using vmbuilder on trunk.
When I specify --ec2-bundle (see entire command below) and I do not
specify --ec2-kernel and --ec2-ramdisk, then the following error is
generated:
2009-11-23 04:32:58,233 DEBUG : Oh, dear, an exception occurred
2009-11-23 04:32:58,233 INFO: Cleaning up
2009-11-23 04:32:58,233 DEBUG : ['rm', '/tmp/tmpPD5Esu']
Traceback (most recent call last):
File vmbuilder/vmbuilder, line 29, in module
VMBuilder.run()
File /home/ubuntu/vmbuilder/VMBuilder/__init__.py, line 65, in run
frontend.run()
File /home/ubuntu/vmbuilder/VMBuilder/plugins/cli/__init__.py, line 68, in
run
vm.create()
File /home/ubuntu/vmbuilder/VMBuilder/vm.py, line 477, in create
self.preflight_check()
File /home/ubuntu/vmbuilder/VMBuilder/vm.py, line 427, in preflight_check
self.call_hooks('preflight_check')
File /home/ubuntu/vmbuilder/VMBuilder/vm.py, line 178, in call_hooks
getattr(plugin, func)()
File /home/ubuntu/vmbuilder/VMBuilder/plugins/ec2/__init__.py, line 82, in
preflight_check
self.vm.ec2_kernel = self.vm.distro.get_ec2_kernel()
File /home/ubuntu/vmbuilder/VMBuilder/plugins/ubuntu/distro.py, line 219,
in get_ec2_kernel
if self.suite.ec2_kernel_info:
AttributeError: 'Ubuntu' object has no attribute 'suite'
Here's the full vmbuilder command:
sudo vmbuilder/vmbuilder xen ubuntu \
--suite=karmic \
--arch=i386 \
--dest=$dest \
--tmp=/mnt \
--ec2 \
--ec2-version=$description \
--manifest=/mnt/$prefix\
--lock-user\
--components=main,restricted,universe,multiverse \
--part=part-${arch}.txt\
--ec2-bundle \
--ec2-upload \
--ec2-register \
--ec2-bucket=$bucket \
--ec2-prefix=$prefix \
--ec2-user=$AWS_USER_ID\
--ec2-cert=$cert \
--ec2-key=$pk \
--ec2-access-key=$AWS_ACCESS_KEY_ID\
--ec2-secret-key=$AWS_SECRET_ACCESS_KEY\
--execscript=$(pwd)/setup-karmic-server\
--debug
ProblemType: Bug
Architecture: i386
Date: Mon Nov 23 04:58:10 2009
DistroRelease: Ubuntu 9.10
Ec2AMI: ami-1515f67c
Ec2AMIManifest:
ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: c1.medium
Ec2Kernel: aki-5f15f636
Ec2Ramdisk: ari-0915f660
Package: python-vm-builder 0.11.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 2.6.31-302.7-ec2
SourcePackage: vm-builder
Tags: ec2-images
Uname: Linux 2.6.31-302-ec2 i686
** Affects: vm-builder (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug ec2-images i386
--
vmbuilder: --ec2-bundle triggers AttributeError: 'Ubuntu' object has no
attribute 'suite'
https://bugs.launchpad.net/bugs/486956
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
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 486956] Re: vmbuilder: --ec2-bundle triggers AttributeError: 'Ubuntu' object has no attribute 'suite'
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35962337/Dependencies.txt -- vmbuilder: --ec2-bundle triggers AttributeError: 'Ubuntu' object has no attribute 'suite' https://bugs.launchpad.net/bugs/486956 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 486955] [NEW] vmbuilder: --execscript in current directory is not found
Public bug reported: This problem happens with the vmbuilder on trunk. When running vmbuilder I passed in an option like --execscript setup-karmic-server where setup-karmic-server was an executable file in my current directory. vmbuilder output the following messages which give a warm fuzzy: 2009-11-23 04:43:15,002 DEBUG : Checking if --exec PATH exists: setup-karmic-server 2009-11-23 04:43:15,002 DEBUG : Checking permissions of --exec PATH: setup-karmic-server It proceeded to build the entire image, then tried to run my script. At this point, it died with the error: Couldn't find the program 'setup-karmic-server' on your system If it's really checking to make sure that the script exists and is executable it might also check to make sure that the script is in the path, or add the current working directory to the path. The workaround is to specify a full path like --execscript $(pwd)/setup-karmic-server but this was an annoying thing to have to run into and to run again, so it would be nice to save others the hassle. See also related bug 292733. ProblemType: Bug Architecture: i386 Date: Mon Nov 23 05:03:36 2009 DistroRelease: Ubuntu 9.10 Ec2AMI: ami-1515f67c Ec2AMIManifest: ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml Ec2AvailabilityZone: us-east-1a Ec2InstanceType: c1.medium Ec2Kernel: aki-5f15f636 Ec2Ramdisk: ari-0915f660 Package: python-vm-builder 0.11.3-0ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 2.6.31-302.7-ec2 SourcePackage: vm-builder Tags: ec2-images Uname: Linux 2.6.31-302-ec2 i686 ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 -- vmbuilder: --execscript in current directory is not found https://bugs.launchpad.net/bugs/486955 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 486955] Re: vmbuilder: --execscript in current directory is not found
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35962327/Dependencies.txt -- vmbuilder: --execscript in current directory is not found https://bugs.launchpad.net/bugs/486955 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 486128] [NEW] euca2ools: Requires more environment variables than EC2 AMI tools
Public bug reported: Binary package hint: euca2ools As I understand it, one of the goals in Ubuntu is for euca2ools to be a drop in replacement for Amazon's EC2 AMI (and API) command line tools. The following are differences where I noticed that I had to set additional environment variables for euca2ools to function properly. - euca-upload-bundle requires setting S3_URL instead of just defaulting to https://s3.amazonaws.com as ec2-upload-bundle does. - euca-register requires setting $EC2_URL instead of defaulting to https://ec2.amazonaws.com as ec2-register does. - euca-register requires setting $EC2_ACCESS_KEY and $EC2_SECRET_KEY instead of also checking $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY_ID as ec2-register does. See also: bug 435140 ProblemType: Bug Architecture: i386 Date: Sat Nov 21 01:38:11 2009 DistroRelease: Ubuntu 9.10 Ec2AMI: ami-1515f67c Ec2AMIManifest: ubuntu-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml Ec2AvailabilityZone: us-east-1a Ec2InstanceType: m1.small Ec2Kernel: aki-5f15f636 Ec2Ramdisk: ari-0915f660 Package: euca2ools 1.0+bzr20091007-0ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 2.6.31-302.7-ec2 SourcePackage: euca2ools Tags: ec2-images Uname: Linux 2.6.31-302-ec2 i686 ** Affects: euca2ools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 uec-images -- euca2ools: Requires more environment variables than EC2 AMI tools https://bugs.launchpad.net/bugs/486128 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 486128] Re: euca2ools: Requires more environment variables than EC2 AMI tools
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35902309/Dependencies.txt -- euca2ools: Requires more environment variables than EC2 AMI tools https://bugs.launchpad.net/bugs/486128 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 479823] Re: euca2ools: euca-bundle-vol strips leading zero (0) from user id
Thierry: This is the first time I've typed any euca2ools commands, so I'm not sure where else there might be a problem. I don't think may commands would require the user id anyway. Let me know if there are any specific ones you'd like me to test. -- euca2ools: euca-bundle-vol strips leading zero (0) from user id https://bugs.launchpad.net/bugs/479823 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- 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 470355] Re: ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest
Torsten: What AMI id are you starting with? -- ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest https://bugs.launchpad.net/bugs/470355 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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 479621] Re: Re bundled karmic image fails to boot
Thanks for reporting this. Can you provide the AMI id you started with? ** Tags added: ec2-images -- Re bundled karmic image fails to boot https://bugs.launchpad.net/bugs/479621 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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 479621] Re: Re bundled karmic image fails to boot
*** This bug is a duplicate of bug 450044 *** https://bugs.launchpad.net/bugs/450044 Thanks Neil. This does appear to be a duplicate of bug 450044, so it is being marked as such. Torsten, please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. I've also added the ec2-images tag to the other bug. ** This bug has been marked a duplicate of bug 450044 euca-bundle-vol does not create essential tmpfs mounts when bundling Ubuntu images -- Re bundled karmic image fails to boot https://bugs.launchpad.net/bugs/479621 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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 440757] Re: ec2-images have ubuntu.canonical.com in /etc/hosts
Scott: Since you're solving this with an exec script, could you also remove the incorrect /etc/hostname file while you're at it? Even though I haven't found any standard packages which depend on /etc/hostname it still bugs me to have an incorrect value stored there by default. -- ec2-images have ubuntu.canonical.com in /etc/hosts https://bugs.launchpad.net/bugs/440757 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 439868] Re: UEC images could be smaller
Thierry: Half joking, I'll point out that anybody can have root on an Ubuntu system for an hour for only $0.10 with EC2. More seriously: If the benefit of the rsync approach is only to increase the number of inodes, perhaps the original mke2fs could be run with the -N option to increase the number of inodes to something reasonable for both 2GB and 10GB. The truncate method certainly seems like it would be faster than the rsync. -- UEC images could be smaller https://bugs.launchpad.net/bugs/439868 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 439868] Re: UEC images could be smaller
AMIs for Amazon EC2 should be 10 GB (10240 * 1024 * 1024 bytes) -- UEC images could be smaller https://bugs.launchpad.net/bugs/439868 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 296159] Re: ec2exec: quotes not needed in sed command
** Changed in: vmbuilder Assignee: Eric Hammond (esh) = Chuck Short (zulcss) ** Changed in: vm-builder (Ubuntu) Assignee: Eric Hammond (esh) = Chuck Short (zulcss) ** Changed in: vmbuilder Status: Fix Committed = Invalid ** Changed in: vm-builder (Ubuntu) Status: Fix Committed = Fix Released -- ec2exec: quotes not needed in sed command https://bugs.launchpad.net/bugs/296159 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 414997] Re: ec2-set-defaults should be 'run_once_per_ami'
Scott: What do you mean by not change anything else? If the user modifies sources.list would a rebundled AMI overwrite their changes or not? I'm also not clear which ami_id is referenced in the last step. If it is the AMI being created, then the user does not know the id yet. -- ec2-set-defaults should be 'run_once_per_ami' https://bugs.launchpad.net/bugs/414997 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 423497] Re: Sudoers file is misconfigured in AMI ami-5059be39
Are we sure that group admin should have sudo rights by default in Karmic? It doesn't in Jaunty. When this bug was submitted, the AMI in question had a comment in /etc/sudoers which claimed that admin should have sudo privs, but the actual line to implement this was missing. The latest Alpha-6 Karmic AMI does not include the comment and looks like the file is reasonable to me. Perhaps somebody could compare it to a standard Karmic /etc/sudoers; the only difference should be that ubuntu has sudo on everything. -- Sudoers file is misconfigured in AMI ami-5059be39 https://bugs.launchpad.net/bugs/423497 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 423497] Re: Sudoers file is misconfigured in AMI ami-5059be39
Upon further review, I stand corrected and the bug stands. -- Sudoers file is misconfigured in AMI ami-5059be39 https://bugs.launchpad.net/bugs/423497 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 414997] Re: ec2-set-defaults should be 'run_once_per_ami'
I'm marking this Low based on my understanding of the importance metrics, but since this can break a user's EC2 image on rebundling, I'd love to see the fix released. ** Changed in: ec2-init (Ubuntu) Importance: Undecided = Low -- ec2-set-defaults should be 'run_once_per_ami' https://bugs.launchpad.net/bugs/414997 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 427288] Re: Karmic i386 EC2 kernel emulating unsupported memory accesses
** Changed in: vmbuilder Status: New = Invalid -- Karmic i386 EC2 kernel emulating unsupported memory accesses https://bugs.launchpad.net/bugs/427288 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 429169] Re: ec2: Include kernel modules in AMIs
there presumably aren't very many modules for the EC2 kernel. I guess this raises the questions of what modules we are talking about, and this is an area where I wouldn't know what to cut out. I personally depend on some which may not be considered part of the core modules including: fuse, xfs, dm_mod, sha256, dm_crypt You'd think that you could cut out things like sound, but I know that some folks are using snd-dummy.ko I don't know what other kernel modules users might be depending on today in EC2. -- ec2: Include kernel modules in AMIs https://bugs.launchpad.net/bugs/429169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 429169] [NEW] ec2: Include kernel modules in AMIs
Public bug reported: It is fairly standard practice to include kernel modules in images for Amazon EC2, but the most recent Karmic AMIs do not include them: ami-a40fefcd canonical-alphas-us/karmic-i386-alpha5.1.manifest.xml ami-a20fefcb canonical-alphas-us/karmic-x86_64-alpha5.1.manifest.xml099720109477 Some other options have been discussed like building kernel modules into the kernel or copying them from initrd into /lib/modules at boot time, but the easiest approach to get things working in the short term is probably just to follow the existing de facto standard and include the kernel modules for the AMI's default kernel. If somebody wants to run it with a different kernel, they are already used to having to install those kernel modules themselves. Ideally, the addition of the kernel modules would be done by default in the vmbuilder EC2 plugin so that it works when normal users create images with vmbuilder. If it is done some other way, the method should be documented publicly so that users can create working images. ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Tags: ec2-images ** Package changed: ubuntu = vm-builder (Ubuntu) -- ec2: Include kernel modules in AMIs https://bugs.launchpad.net/bugs/429169 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 289998] Re: Allow multiple exec scripts
** Also affects: vm-builder (Ubuntu) Importance: Undecided Status: New ** Changed in: vmbuilder Status: Confirmed = Invalid ** Changed in: vm-builder (Ubuntu) Status: New = Confirmed -- Allow multiple exec scripts https://bugs.launchpad.net/bugs/289998 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 287860] Re: vmbuilder EC2: Retry ec2-upload-bundle on failures
** Changed in: vmbuilder Status: Fix Committed = Fix Released ** Changed in: vm-builder (Ubuntu) Status: Fix Committed = Fix Released -- vmbuilder EC2: Retry ec2-upload-bundle on failures https://bugs.launchpad.net/bugs/287860 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 235562] Re: Add ability to build Debian virtual machines
** Changed in: vmbuilder Status: Confirmed = Invalid -- Add ability to build Debian virtual machines https://bugs.launchpad.net/bugs/235562 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- 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 408562] [NEW] Updgrade ec2-ami-tools to 1.3-34544
Public bug reported: Binary package hint: ec2-ami-tools The package ec2-ami-tools is outdated on Hardy, Intrepid, Jaunty, Karmic. This prevents the usage of the latest EC2 features. ** Affects: ec2-ami-tools (Ubuntu) Importance: Undecided Status: New -- Updgrade ec2-ami-tools to 1.3-34544 https://bugs.launchpad.net/bugs/408562 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in ubuntu. -- 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
