[Bug 1230677] New: Tracker for golang-googlecode-net
by Red Hat Bugzilla
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.
8 years
[Bug 1272438] New: etcd-v2.2.1 is available
by Red Hat Bugzilla
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.
8 years
[Bug 1279843] New: etcd-v2.3.0-alpha.0 is available
by Red Hat Bugzilla
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.
8 years
[Bug 1246207] New: Tracker for golang-github-boltdb-bolt
by Red Hat Bugzilla
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.
8 years
[Bug 1312886] New: Flannel service fails on reboot
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1312886
Bug ID: 1312886
Summary: Flannel service fails on reboot
Product: Fedora
Version: 23
Component: flannel
Severity: medium
Assignee: jchaloup(a)redhat.com
Reporter: surajd(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, linville(a)redhat.com,
nhorman(a)redhat.com, vbatts(a)redhat.com
Description of problem: flanneld service fails to start when restarting the
Fedora 23 cloud Vagrant Box.
Version-Release number of selected component (if applicable):
flanneld - 0.5.4
fedora/23-cloud-base vagrant box
How reproducible:
Easily reproducible
Steps to Reproduce:
(pre-requisite = start etcd service on some other machine, here:
192.168.121.45)
1. Get a fedora/23-cloud-base vagrant box and start it.
2. Install flannel using dnf
3. Do configuration of flannel in /etc/sysconfig/flanneld as following
[root@fedminion2 ~]# cat /etc/sysconfig/flanneld
FLANNEL_ETCD="http://192.168.121.45:2379"
FLANNEL_ETCD_KEY="/fedmaster/network"
4. enable the flannel service to autostart using systemctl
5. exit out of the box, halt it and do vagrant up again.
6. Once inside the machine check the status of flanneld service.
Actual results:
The service fails as:
**Failed to get default interface: Unable to find default route**
This is also reported at
http://ask.projectatomic.io/en/question/3553/flanneld-fails-when-vm-starts/
Expected results:
The service should start
Additional info:
I fixed this problem by changing the value in
"/usr/lib/systemd/system/flanneld.service" of "After=network.target" to
"After=network-online.target"
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years
[Bug 1318576] New: Tracker for fleet
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1318576
Bug ID: 1318576
Summary: Tracker for fleet
Product: Fedora
Version: rawhide
Component: fleet
Assignee: lemenkov(a)gmail.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lemenkov(a)gmail.com, vbatts(a)redhat.com
Tracker for async updates of fleet 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.
8 years
[Bug 1316424] New: Regression local 127.0.0.1 node not registered by
default
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1316424
Bug ID: 1316424
Summary: Regression local 127.0.0.1 node not registered by
default
Product: Fedora
Version: 24
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,
nhorman(a)redhat.com, vbatts(a)redhat.com
Description of problem:
The local 127.0.0.1 kubernetes node should register itself in the default
install. In the fedora-24 build it no longer does:
Version-Release number of selected component (if applicable):
kubernetes-1.2.0-0.14.alpha6.gitf0cd09a.fc24.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. systemctl start etcd kube-apiserver kube-controller-manager kube-scheduler
docker kube-proxy kubelet
2. kubectl get nodes # wait or repeat as needed
Actual results:
No output.
Expected results:
NAME LABELS STATUS
127.0.0.1 kubernetes.io/hostname=127.0.0.1 Ready
Additional info:
This works on fedora-23 with the following kubernetes RPM:
kubernetes-1.1.0-0.17.git388061f.fc23.x86_64. In addition the following RPM
from fedora-23 updates-testing 1.2.0-0.15.alpha6.gitf0cd09a.fc23
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years
[Bug 1096273] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla
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.
8 years
[Bug 1286185] New: Tracker for golang-github-opencontainers-specs
by Red Hat Bugzilla
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.
8 years
[Bug 1318299] New: Tracker for golang-github-go-fsnotify-fsnotify
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1318299
Bug ID: 1318299
Summary: Tracker for golang-github-go-fsnotify-fsnotify
Product: Fedora
Version: rawhide
Component: golang-github-go-fsnotify-fsnotify
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-go-fsnotify-fsnotify 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.
8 years