This bug was fixed in the package walinuxagent - 1.3.2-0ubuntu2~13.04.1
---
walinuxagent (1.3.2-0ubuntu2~13.04.1) raring-proposed; urgency=low
* Backport of 1.3.2-0ubuntu5 from 13.10
* disable ephemeral disk formating by default (LP: #1231490)
* debian/patches/shadow_permiss
** Changed in: walinuxagent (Ubuntu Precise)
Status: New => Fix Committed
** Changed in: walinuxagent (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: walinuxagent (Ubuntu Raring)
Importance: Undecided => Medium
** Changed in: walinuxagent (Ubuntu)
Assignee: (una
Hello Scott, or anyone else affected,
Accepted walinuxagent into raring-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/walinuxagent/1.3.2-0ubuntu2~13.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package
Makring verification-done as part of SRU testing.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195524
Title:
race condition / transient failure to provision
To m
** Description changed:
+ [Impact]:
+ WALinuxAgent currently handles the provisioning of Ubuntu. This bug is fixed
by Bug #1037723, which causes provisioning to be handled by Cloud-init.
+
+ [Regression] : By moving provisioning functions to cloud-init, the
+ regression potential is low. Furth
This bug was fixed in the package walinuxagent - 1.3.2-0ubuntu4
---
walinuxagent (1.3.2-0ubuntu4) saucy; urgency=low
* debian/patches/shadow_permissions.patch: apply the appropriate
permissions to /etc/shadow (LP: #1188820).
* debian/patches/verbose_logging.patch: use the appr
** Branch linked: lp:ubuntu/walinuxagent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195524
Title:
race condition / transient failure to provision
To manage notifications about this bug go to:
h
I'm fairly certain there is still a race condition that I described comment 8.
Please raise the hostname issue in another bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195524
Title:
race condi
s/Commissioning/Provisioning/ sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195524
Title:
race condition / transient failure to provision
To manage notifications about this bug g
I did some testing and it turns out the hostname size seems to be the
problem! I started a bunch of machines with a hostname of 64 characters
and a bunch of machines with a hostname of 25 characters (with the
script I linked above): all the machines with a hostname of 25 ended up
in the state "Run
Hello!
Thank you for confirming that. I think the hostname just looked odd so
just wanted to confirm as we don't have access to this environment.
If the instance is still available we really need more logs to figure
out what went wrong. This will help determine if there's something
wrong on the
The doc (http://msdn.microsoft.com/en-
us/library/windowsazure/jj157194.aspx) explicitly says the hostname can
get 64 characters long: "HostName: Required. Specifies the host name for
the VM. Host names are ASCII character strings 1 to 64 characters in
length. Used with the LinuxProvisioningConfigu
> 2013/06/28 15:08:12 EnvMonitor: Detected host name change: ubuntu ->
> gwaclhostblkhljy4re3yp9swkdwp63kswkss9bqhn0zm3f3gunipzu5vwdr8qzw
> 2013/06/28 15:08:12 Setting host name:
> gwaclhostblkhljy4re3yp9swkdwp63kswkss9bqhn0zm3f3gunipzu5vwdr8qzw
> Is it expected?
Yes, this machine was created us
Aside from the kernel logs, please also include /var/log/syslog and any other
relevant logs. Long, I believe the contents of /var/lib/waagent were posted
here:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1195524/+attachment/3717115/+files/waagent-info.tar
There is retry logic in
Can you also share the kernel logs, and all the files in
/var/lib/waagent?
In the waagent.log, the new host name seems uncommon:
2013/06/28 15:08:12 EnvMonitor: Detected host name change: ubuntu ->
gwaclhostblkhljy4re3yp9swkdwp63kswkss9bqhn0zm3f3gunipzu5vwdr8qzw
2013/06/28 15:08:12 Setting host
ok... i think ihave a reasonable description of what caused this specific hang.
The last entry in this /var/log/waagent.log was:
2013/06/28 14:50:12 Provisioning image using OVF settings in the DVD.
2013/06/28 14:50:12 Resource disk (/dev/sdb1) is mounted at /mnt/resource with
fstype ext4
2013/06/
I noticed while doing the kdump debugging that you can ssh into a
cloud-image instance very early (well before the console allows login) on a
kvm based cloud-image instance. I was surprised that service was available
before console login was available. Not sure it is related to what your are
seeing
ok. so i have 2 other systems that are showing this failure now.
I was able to ssh into them, though.
walinux-agent had provisioned the user, populated ssh keys and then also
started sshd (which it actually should not do).
it shouldn't start sshd because it is possibly doing that before sshd
has
** Attachment added: "waagent.log and waagent dir."
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1195524/+attachment/3717115/+files/waagent-info.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
You can get kdump working in Azure (not that you really need it for this)
with the attached patch.
Ref: http://support.microsoft.com/kb/2858695
On Thu, Jun 27, 2013 at 8:01 PM, Scott Moser wrote:
> given my previous comment, i would have suspected that there was disk or
> kernel failure.
> how
given my previous comment, i would have suspected that there was disk or kernel
failure.
however, ssh-keyscan seemed to indicate ssh was running:
$ ssh-keyscan us-west-1.cloudapp.net
# us-west-1.cloudapp.net SSH-2.0-OpenSSH_6.1p1 Debian-4
Connection closed by 137.135.115.232
--
You received thi
as I'm trying to debug this instance that failed for me, and then came up after
a 'vm restart', there is no indication that / was ever mounted RW the first
time. Ie, there is no evidence in /var/log of *anything* having run.
cloud-init starts on mounted MOUNTPOINT=/
and logs pretty much immediat
22 matches
Mail list logo
