[Bug 1087704] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
Bug ID: 1087704
Summary: repetition of signal 21 with --sig-proxy and SIGSTOP
of docker
Product: Fedora
Version: 20
Component: docker-io
Severity: low
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
I noticed weird reaction to SIGSTOP signal. When you start container with
--sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to
the `docker run` process, it's put into background. (so far correct behavior)
Than when you use kill -SIGCONT, it's resumed (still in background) and it's
continuing to send signal 21 to the container (100% CPU utilization).
This disappears once you attach the process with fg.
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly
localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps ax |grep docker
3. kill -SIGSTOP $PID
4. kill -SIGCONT $PID
Actual results:
[1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name
test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`;
do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1;
done'
[root@t530 ~]# Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
Received 21, ignoring...
... (100% CPU utilization, when you use fg it stops and you can use the
container again...)
Expected results:
[1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name
test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`;
do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1;
done'
[root@t530 ~]# Received 21, ignoring...
Additional info:
I'm not definitely sure if this is really required as it's not a common usage.
But as there is no way to detach the process apart from kill -SIGSTOP people
might use it and get to this problem...
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years
[Bug 1087720] New: signal 27 (SIGPROF) not passed to container using --sig-proxy
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Bug ID: 1087720
Summary: signal 27 (SIGPROF) not passed to container using
--sig-proxy
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
When I send signal 27 to the docker process, which is running with
--sig-proxy=true, it's not forwarded. Other signals are...
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly
localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps ax |grep docker
3. kill -27 $PID
Actual results:
nothing
Expected results:
Received 27, ignoring...
Additional info:
When you send any other signal (apart from 19 or 9) it works fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years
[Bug 1029587] New: upgrade to go1.2 (once it is available)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1029587
Bug ID: 1029587
Summary: upgrade to go1.2 (once it is available)
Product: Fedora
Version: rawhide
Component: golang
Severity: low
Assignee: adam(a)spicenitz.org
Reporter: vbatts(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adam(a)spicenitz.org, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
lsm5(a)redhat.com, renich(a)woralelandia.com,
vbatts(a)redhat.com
What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. export GOPATH=$(mktemp -d)
2. go get code.google.com/p/go.tools/cmd/oracle
3.
What is the expected output?
What do you see instead?
/tmp/tmp.cjYFzAeLWC/src/code.google.com/p/go.tools/importer/source.go:434:
n.Lparen undefined (type *ast.TypeAssertExpr has no field or method Lparen)
/tmp/tmp.cjYFzAeLWC/src/code.google.com/p/go.tools/importer/source.go:435:
n.Lparen undefined (type *ast.TypeAssertExpr has no field or method Lparen)
/tmp/tmp.cjYFzAeLWC/src/code.google.com/p/go.tools/importer/source.go:436:
n.Rparen undefined (type *ast.TypeAssertExpr has no field or method Rparen)
Which compiler are you using (5g, 6g, 8g, gccgo)?
6g
Which operating system are you using?
Red Hat Enterprise Linux Workstation release 6.4 (Santiago)
Which version are you using?
go version go1.1.2 linux/amd64 (golang-1.1.2-4.el6.x86_64)
Please provide any additional information below.
I tested against the tip of their repo (future version 1.2) (go version devel
+39c724dd7f25 Tue Nov 12 09:28:07 2013 +1100 linux/amd64)
and code.google.com/p/go.tools/cmd/oracle and
code.google.com/p/go.tools/cmd/ssadump build just fine
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1099074] New: Processing Dependency: golang-docs = 1.1-2.fc19 for package: golang-godoc-1.1-2.fc19.x86_64
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1099074
Bug ID: 1099074
Summary: Processing Dependency: golang-docs = 1.1-2.fc19 for
package: golang-godoc-1.1-2.fc19.x86_64
Product: Fedora
Version: 19
Component: golang
Severity: high
Assignee: adam(a)spicenitz.org
Reporter: dridi.boukelmoune(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adam(a)spicenitz.org, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io,
vbatts(a)redhat.com
Description of problem:
I'm trying to install the golang-godoc package but it fails. It's looking for
golang-docs which is provided by golang, but the required version doesn't
match.
Version-Release number of selected component (if applicable):
golang-1.2.1-1.fc19.x86_64
golang-godoc-1.1-2.fc19.x86_64
How reproducible: always
Steps to Reproduce:
1. sudo yum install golang
2. sudo yum install golang-godoc
Actual results:
Resolving Dependencies
--> Running transaction check
---> Package golang-godoc.x86_64 0:1.1-2.fc19 will be installed
--> Processing Dependency: golang-docs = 1.1-2.fc19 for package:
golang-godoc-1.1-2.fc19.x86_64
Package golang-docs-1.1-2.fc19.noarch is obsoleted by
golang-1.2.1-1.fc19.x86_64 which is already installed
--> Processing Dependency: golang(x86-64) = 1.1-2.fc19 for package:
golang-godoc-1.1-2.fc19.x86_64
--> Finished Dependency Resolution
Error: Package: golang-godoc-1.1-2.fc19.x86_64 (fedora)
Requires: golang(x86-64) = 1.1-2.fc19
Installed: golang-1.2.1-1.fc19.x86_64 (@updates)
golang(x86-64) = 1.2.1-1.fc19
Available: golang-1.1-2.fc19.x86_64 (fedora)
golang(x86-64) = 1.1-2.fc19
Error: Package: golang-godoc-1.1-2.fc19.x86_64 (fedora)
Requires: golang-docs = 1.1-2.fc19
Available: golang-docs-1.1-2.fc19.noarch (fedora)
golang-docs = 1.1-2.fc19
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Expected results:
Is this ok [y/d/N]:
Additional info:
I couldn't find golang-godoc in pkgdb2, so I'm filing against golang.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1056185] New: go test code.google.com/p/go.net/ipv6 test fails
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1056185
Bug ID: 1056185
Summary: go test code.google.com/p/go.net/ipv6 test fails
Product: Fedora EPEL
Version: el6
Component: golang-googlecode-net
Assignee: lsm5(a)redhat.com
Reporter: tis(a)foobar.fi
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, vbatts(a)redhat.com
Description of problem:
%check fails if machine you build this package on has ipv6 connectivity.
+ go test code.google.com/p/go.net/ipv6
--- FAIL: TestConnInitiatorPathMTU (0.00 seconds)
sockopt_test.go:58: ipv6.Conn.PathMTU failed: getsockopt: protocol not
available
--- FAIL: TestConnResponderPathMTU (0.00 seconds)
sockopt_test.go:91: ipv6.Conn.PathMTU failed: getsockopt: protocol not
available
--- FAIL: TestPacketConnReadWriteUnicastUDP (0.00 seconds)
unicast_test.go:120: ipv6.PacketConn.SetControlMessage failed:
setsockopt: protocol not available
FAIL
FAIL code.google.com/p/go.net/ipv6 0.041s
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.DbihRB (%check)
I guess package is broken for ipv6.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1101123] New: docker package binary conflicts with docker-io
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1101123
Bug ID: 1101123
Summary: docker package binary conflicts with docker-io
Product: Fedora
Version: 20
Component: docker-io
Severity: medium
Assignee: lsm5(a)redhat.com
Reporter: dmcf(a)dcorking.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
There is a file name conflict for /usr/bin/docker between 2 Fedora 20 packages.
Version-Release number of selected component (if applicable):
docker-1.5-10.fc20.x86_64 (f20 updates, a dockapp that provides a system tray
for WindowMaker, XFCE etc.)
docker-io-0.11.1-1.fc20.x86_64.rpm (f20 updates, a new Linux containerization
app that has proven very popular)
How reproducible: Consistent.
Steps to Reproduce:
1. sudo yum install docker
2. sudo yum install docker-io
Actual results:
Transaction check error:
file /usr/bin/docker from install of docker-io-0.11.1-1.fc20.x86_64 conflicts
with file from package docker-1.5-10.fc20.x86_64
Expected results:
All packages in F20 should be able to co-exist unless a conflict is documented
in the RPM file.
Since the conflict is only file naming, one of these packages could be patched
to allow it to co-exist with the other.
Additional info:
Possible workaround that keeps docker working for me follows.
(It allows docker-io to install, but I am not sure if docker-io is fully
functioning.)
#!/bin/bash
sudo mv /usr/bin/docker /usr/bin/wmdocker
# user must change dock icons that link to docker to point to wmdocker
sudo yum install docker-io --downloadonly
cd /var/cache/yum/x86_64/20/updates/packages/
sudo rpm -Uvf --force docker-io-0.11.1-1.fc20.x86_64.rpm
The conflict probably also exists in rawhide. (unverified)
The upstream binary in both packages is 'docker'. Debian/Ubuntu rename their
binary to 'docker-io' to deal with the conflict.
There is a plan to replace the 'docker' package with a renamed 'wmdocker'
package in F21. (Bug # 1043676). However, that will take until F23 release to
complete the Obsoletes/Expires process. In the meantime, any user with docker
from F20 or rawhide will be unable to install docker-io, unless they use the
workaround.
Related issues:
* https://fedorahosted.org/fpc/ticket/341 "How to replace "docker" package with
an entirely different package of the same name?"
* https://bugzilla.redhat.com/show_bug.cgi?id=1043676 "drop docker from rawhide
(or redirect to wmdocker)"
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 3 months
[Bug 1114098] New: fedora 20: etcd broken on install, very out of date, and misconfigured.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1114098
Bug ID: 1114098
Summary: fedora 20: etcd broken on install, very out of date,
and misconfigured.
Product: Fedora
Version: 20
Component: etcd
Assignee: lacypret(a)gmail.com
Reporter: bugs(a)jameskyle.org
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lacypret(a)gmail.com,
lemenkov(a)gmail.com
Description of problem:
etcd service on fedora 20 only returns 404 page not found for all queries.
Version-Release number of selected component (if applicable):
Fedora 20, etcd 0.1.3
How reproducible:
100%
Steps to Reproduce:
1. yum install etcd
2. systemctl start etcd
3. curl http://127.0.0.1:4001/v2/keys/foo -d "Bar"
Actual results:
404 page not found
Expected results:
{"action":"set","node":{"key":"/message","value":"Hello","modifiedIndex":5,"createdIndex":5}}
Additional info:
The service was configured to use a systemd socket service, but (from the
systemd debs) "etcd doesn't have socket activation".
Even if I disabled the socket service and ran etcd 0.1.3 in the foreground with
defaults, the same behavior was manifest.
Installing the current 0.4.4 version of etcd produced the expected/desired
behavior.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 4 months