Hi, I wanted to use "virtsh console instance-" as described here:
http://www.jaredlog.com/?p=1484 for debugging this issue:
https://ask.openstack.org/en/question/89583/cant-ping-machine-after-
unrescue/ but I encountered this problem. My goal was to connect to the
instance and see the console
You can use the following:
virsh console --devname serial1 instance-
** Changed in: nova (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Its quite likely that this is intended function - the console output of
the instance is mapped to a log file so that 'nova console-log' can be
used to retrieve log data via the public API of nova.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
However that may not be usable - anyway I think this is by design - end
users won't normally have direct access to compute hosts!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/807091
I'm seeing this on trusty/icehouse:
root@furud:~# virsh list --all
IdName State
32instance-2bb1 running
37instance-2bb2 running
4237 instance-6b86
This should be fixed now, please re-open if you are still having
problems.
Regards
chuck
** Changed in: nova (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
So, I've tried the latest oneiric cloud images from today and two days
ago and I still get the PTY allocation request failed on channel 0
connecting via ssh.
With euca-get-console-output instance id I still get (from nova-api.log):
(nova.api): TRACE: RemoteError: Error local variable 'fpath'
Also, it seems moving the serial tag makes no difference for what I can
see
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/807091
Title:
internal error character device (null) is not
** Changed in: nova (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/807091
Title:
internal error character device (null) is not using a PTY when
@Tom, can you provide an update if that resolved the issue?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/807091
Title:
internal error character device (null) is not using a
@Chuck
Yes, tried todays daily oneiric image on diablo-3 and still see the same issue:
ubuntu@sugarloaf:~/images$ euca-describe-instances
RESERVATION r-vchanq4i projdefault
INSTANCEi-0023 ami-0008192.168.3.3 192.168.3.3
running psekey (proj, perce)
@Matt Interesting, I'll have a play around with it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/807091
Title:
internal error character device (null) is not using a PTY when using
** Changed in: nova (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/807091
Title:
internal error character device (null) is not using a PTY
Hi All,
I was able to replicate this running --libvirt_type=qemu, and see
similar virsh dumpxml output as reported in
https://www.redhat.com/archives/libvir-list/2009-July/msg00460.html. If
I move the serial type='pty' tag above serial type=file in
libvirt.xml (despite libvirt.xml stating that
Tom,
Is this still a problem for you?
Regards
chuck
** Changed in: nova (Ubuntu)
Importance: Undecided = Low
** Changed in: nova (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
I wonder if it's an issue with Nova (for example, does eucalyptus
succeed in the same situation), with libvirt, or with the Ubuntu cloud
images...
** Summary changed:
- error: internal error character device (null) is not using a PTY
+ internal error character device (null) is not using a PTY
16 matches
Mail list logo
