https://bugzilla.redhat.com/show_bug.cgi?id=1230677
Bug ID: 1230677
Summary: Tracker for golang-googlecode-net
Product: Fedora
Version: rawhide
Component: golang-googlecode-net
Severity: low
Priority: low
Assignee: lsm5(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com
Tracker for async updates of golang-github-prometheus-client_golang for rawhide
and other fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1272438
Bug ID: 1272438
Summary: etcd-v2.2.1 is available
Product: Fedora
Version: rawhide
Component: etcd
Keywords: FutureFeature, Triaged
Assignee: jchaloup(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: avagarwa(a)redhat.com, eparis(a)redhat.com,
golang(a)lists.fedoraproject.org, jcajka(a)redhat.com,
jchaloup(a)redhat.com, lacypret(a)gmail.com,
lemenkov(a)gmail.com, walters(a)redhat.com
Latest upstream release: v2.2.1
Current version/release in rawhide: 2.2.0-1.fc24
URL: https://github.com/coreos/etcd
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1279843
Bug ID: 1279843
Summary: etcd-v2.3.0-alpha.0 is available
Product: Fedora
Version: rawhide
Component: etcd
Keywords: FutureFeature, Triaged
Assignee: jchaloup(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: avagarwa(a)redhat.com, eparis(a)redhat.com,
golang(a)lists.fedoraproject.org, jcajka(a)redhat.com,
jchaloup(a)redhat.com, lacypret(a)gmail.com,
lemenkov(a)gmail.com, walters(a)redhat.com
Latest upstream release: v2.3.0-alpha.0
Current version/release in rawhide: 2.2.1-3.fc24
URL: https://github.com/coreos/etcd
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1246207
Bug ID: 1246207
Summary: Tracker for golang-github-boltdb-bolt
Product: Fedora
Version: rawhide
Component: golang-github-boltdb-bolt
Severity: low
Priority: low
Assignee: fpokorny(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com
Tracker for async updates of golang-github-boltdb-bolt for rawhide and other
fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096273
Bug ID: 1096273
Summary: repetition of signal 21 with --sig-proxy and SIGSTOP
of docker
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Severity: low
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
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
Depends On: 1087704
+++ This bug was initially created as a clone of Bug #1087704 +++
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-0.10.0-8.el7.x86_64
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...
--- Additional comment from Lukas Doktor on 2014-05-05 03:59:30 EDT ---
I retested this with the upstream dc9c28f/0.10.0 with the same results. The
daemon output is:
...
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) =
OK (0)
2014/05/05 09:58:13 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN)
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) =
OK (0)
2014/05/05 09:58:13 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN)
[/home/medic/Work/Projekty/Docker/root|fa3816b6] -job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) =
OK (0)
2014/05/05 09:58:13 POST
/v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN
[/home/medic/Work/Projekty/Docker/root|fa3816b6] +job
kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN)
...
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1087704
[Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of
docker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1286185
Bug ID: 1286185
Summary: Tracker for golang-github-opencontainers-specs
Product: Fedora
Version: rawhide
Component: golang-github-opencontainers-specs
Assignee: fpokorny(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com
Tracker for async updates of golang-github-opencontainers-specs for rawhide and
other fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1202517
Bug ID: 1202517
Summary: docker fd leak
Product: Red Hat Enterprise Linux 7
Version: 7.2
Component: docker
Assignee: dwalsh(a)redhat.com
Reporter: dwalsh(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
CC: adimania(a)gmail.com, admiller(a)redhat.com,
arozansk(a)redhat.com, b(a)wtnb.mydns.jp,
dwalsh(a)redhat.com, extras-qa(a)fedoraproject.org,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jeder(a)redhat.com,
jmario(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
srao(a)redhat.com, thrcka(a)redhat.com,
tstclair(a)redhat.com, vbatts(a)redhat.com,
vgoyal(a)redhat.com
Depends On: 1189028
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1189028
[Bug 1189028] docker fd leak
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1214958
Bug ID: 1214958
Summary: etcd-v2.1.0-alpha.0 is available
Product: Fedora
Version: rawhide
Component: etcd
Keywords: FutureFeature, Triaged
Assignee: lacypret(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: avagarwa(a)redhat.com, eparis(a)redhat.com,
golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lacypret(a)gmail.com, lemenkov(a)gmail.com,
lsm5(a)redhat.com, walters(a)redhat.com
Latest upstream release: v2.1.0-alpha.0
Current version/release in rawhide: 2.0.10-1.fc23
URL: https://github.com/coreos/etcd
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1259148
Bug ID: 1259148
Summary: Regression: kubernetes 1.1.0 breaks watching for
resources
Product: Fedora
Version: 22
Component: kubernetes
Assignee: jchaloup(a)redhat.com
Reporter: stefw(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jcajka(a)redhat.com, jchaloup(a)redhat.com,
lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com
Description of problem:
When cockpit tries to watch resources against kubernetes 1.1.0 it gets the
following complaints:
.> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
> watching kubernetes endpoints failed: too old resource version: 0 (7)
E> watching kubernetes nodes failed: too old resource version: 0 (13)
> watching kubernetes pods failed: too old resource version: 0 (1)
Version-Release number of selected component (if applicable):
kubernetes x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing 33 k
kubernetes-client x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing 2.8 M
kubernetes-master x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing 13 M
kubernetes-node x86_64 1.1.0-0.14.gitb6f18c7.fc22 updates-testing 9.1 M
How reproducible:
Every time.
Steps to Reproduce:
1. Run Cockpit on your node, with cockpit-kubernetes
2. Navigate to cluster tab
3. Look at javascript console output
--
You are receiving this mail because:
You are on the CC list for the bug.