I'm not entirely sure if it's the same issue, but I'm seeing something
very similar on the latest builds of precise and trusty at http://cloud-
images.ubuntu.com/vagrant/. On the first boot, ssh is unreachable and
provisioning fails. After halting the VM and subsequently booting it
again, ssh is re
Marking as fix released. Latest images handle this nicely.
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
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/bug
>From the logs, the local datasource for cloud-init is not claiming the
datasource on the first run. If you run cloud-init again, it claims the
data source again.
2013-09-30 14:36:00,208 - __init__.py[DEBUG]: Seeing if we can get any data
from
2013-09-30 14:36:00,208 - util.py[DEBUG]: Reading fr
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
DistroRelease: Ubuntu 13.04
MarkForUpload: True
Package: cloud-init 0.7.2-0ubuntu0.13.04.1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Tags: raring uec-images
Uname: Linux 3.8.0-30-generic x86_64
UpgradeStat
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://b
There's a new "batch" of machines (from Sep 28, 2013), and I was able to
import them on VirtualBox and verify that they have the previously
missing files. I could then ssh into my imported machine without
problems.
When I do "vagrant up", though, the files are not there, which is very
weird, but I
Having this problem as well.
--
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/1217950
Title:
SSH public key isn't created in vagrant cloud images
To manage notifications about thi
Errors in auth.log show:
Sep 26 19:43:51 vagrant-ubuntu-raring-64 sshd[1442]: error: Could not load host
key: /etc/ssh/ssh_host_rsa_key
Sep 26 19:43:51 vagrant-ubuntu-raring-64 sshd[1442]: error: Could not load host
key: /etc/ssh/ssh_host_dsa_key
Sep 26 19:43:51 vagrant-ubuntu-raring-64 sshd[14
I've hit this bug as well.
I've tried it with the following images:
http://cloud-images.ubuntu.com/vagrant/raring/20130917/raring-server-cloudimg-amd64-vagrant-disk1.box
http://cloud-images.ubuntu.com/vagrant/raring/20130921/raring-server-cloudimg-amd64-vagrant-disk1.box
http://cloud-ima
** Attachment added: "Debug output of manual attempt to SSH in to VM as
"vagrant""
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1217950/+attachment/3827671/+files/SSHdebug.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
As a point of information, the virtual instance works fine on the second
boot.
i.e. if you" vagrant up: vagrant halt; vagrant up" everything works as
expected with the exception that the post provisioning/configuration
process will have failed.
System configuration:
Ubuntu image:
http://cloud-
This appears to be a problem in certain daily builds only. I don't have
the exact dates of when it started and stopped working, but I was able
to reproduce several times in June, July, and August. After that, I was
unable to reproduce using a build made on August 20th, 2013, but then I
was able t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
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/b
13 matches
Mail list logo
