This was fixed with updates and backports to the gccgo tool-chain.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: juju-core
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This was fixed with updates and backports to the gccgo tool-chain.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: juju-core
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: juju-core
Importance: High = Medium
** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
** Changed in: juju-core
Importance: High = Medium
** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a
** Tags added: panic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a panic: runtime error
To manage notifications about this bug go to:
** Tags added: panic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a panic: runtime error
To manage notifications about this bug go to:
With sinzui's help I have compiled the latest version of Juju 1.20.2
with the gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb.
NOT able to reproduce the “juju ssh” panic/problem having several ssh
sessions open simultaneously and having output streaming for over 2
hours.
For clarity and review here are the
btw. This has nothing to do with ssh, it is to do with the length of
time the juju cli process is running for. Normally this is a very
short period, but juju ssh forks ssh as a child then waits for it to
finish. The crash is caused by a bug in the previous runtime (compiled
statically into the
With sinzui's help I have compiled the latest version of Juju 1.20.2
with the gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb.
NOT able to reproduce the “juju ssh” panic/problem having several ssh
sessions open simultaneously and having output streaming for over 2
hours.
For clarity and review here are the
btw. This has nothing to do with ssh, it is to do with the length of
time the juju cli process is running for. Normally this is a very
short period, but juju ssh forks ssh as a child then waits for it to
finish. The crash is caused by a bug in the previous runtime (compiled
statically into the
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: ppc64el
--
You received this bug
Note, we have gotten an initial report from the field as to this failing
and it is blocking Juju Power deployments.
-thanks,
Antonio
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Is there a more complete log output? This seems like just a snippet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a panic: runtime error
To
** Attachment added: The juju logs from the 1.18.1 panic on stilson-01.
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1347322/+attachment/4161298/+files/machine_logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
I am using Juju on Power 8 hardware and I get a panic when I use juju to
ssh to a system. The reproduction steps are
+ juju init
juju bootstrap -e local
juju deploy local:trusty/ubuntu
juju ssh ubuntu/0
(use the session to the local machine and after
** Description changed:
I am using Juju on Power 8 hardware and I get a panic when I use juju to
ssh to a system. The reproduction steps are
juju init
juju bootstrap -e local
+ juju switch local
juju deploy local:trusty/ubuntu
juju ssh ubuntu/0
(use the session to the local
I have tried to reproduce this problem in utopic on rockne (a P7+
system), and it's not reproducible for me.
# grep P /proc/cpuinfo
cpu : POWER7+ (raw), altivec supported
cpu : POWER7+ (raw), altivec supported
machine : CHRP IBM pSeries (emulated by qemu)
# uname
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: ppc64el
--
You received this bug
Note, we have gotten an initial report from the field as to this failing
and it is blocking Juju Power deployments.
-thanks,
Antonio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
Is there a more complete log output? This seems like just a snippet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a panic: runtime error
To manage
** Attachment added: The juju logs from the 1.18.1 panic on stilson-01.
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1347322/+attachment/4161298/+files/machine_logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
I am using Juju on Power 8 hardware and I get a panic when I use juju to
ssh to a system. The reproduction steps are
+ juju init
juju bootstrap -e local
juju deploy local:trusty/ubuntu
juju ssh ubuntu/0
(use the session to the local machine and after
** Description changed:
I am using Juju on Power 8 hardware and I get a panic when I use juju to
ssh to a system. The reproduction steps are
juju init
juju bootstrap -e local
+ juju switch local
juju deploy local:trusty/ubuntu
juju ssh ubuntu/0
(use the session to the local
I have tried to reproduce this problem in utopic on rockne (a P7+
system), and it's not reproducible for me.
# grep P /proc/cpuinfo
cpu : POWER7+ (raw), altivec supported
cpu : POWER7+ (raw), altivec supported
machine : CHRP IBM pSeries (emulated by qemu)
# uname
26 matches
Mail list logo
