March 2015 - golang - Fedora Mailing-Lists

by Fedora Koji Build System

kubernetes has broken dependencies in the F-22 tree: On x86_64: kubernetes-0.12.0-0.9.git53b25a7.fc22.x86_64 requires docker Please resolve this as soon as possible.

9 years, 1 month

1
0
0 / 0

Broken dependencies: cadvisor

by Fedora Koji Build System

cadvisor has broken dependencies in the F-22 tree: On x86_64: cadvisor-0.6.2-0.1.git89088df.fc22.x86_64 requires docker-io Please resolve this as soon as possible.

9 years, 1 month

1
0
0 / 0

[Bug 1200924] New: typo in /etc/kubernetes/kubelet

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1200924 Bug ID: 1200924 Summary: typo in /etc/kubernetes/kubelet Product: Fedora Version: rawhide Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: leon(a)bcl.bz QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: In /etc/kubernetes/kubelet there is following line: KUBELET_API_SERVER="--api_server=127.0.0.1:8080" but according to kubelet --help output and source code actual command line option is --api_servers Version-Release number of selected component (if applicable): kubernetes-0.12.0-0.4.gita4d871a.fc2 How reproducible: Additional info: Following patch should be applied: --- contrib/init/systemd/environ/kubelet.orig 2015-03-03 07:04:24.000000000 +0300 +++ contrib/init/systemd/environ/kubelet 2015-03-11 18:10:49.638406448 +0300 @@ -11,7 +11,7 @@ KUBELET_HOSTNAME="--hostname_override=127.0.0.1" # location of the api-server -KUBELET_API_SERVER="--api_server=127.0.0.1:8080" +KUBELET_API_SERVER="--api_servers=127.0.0.1:8080" # Add your own! KUBELET_ARGS="" -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 1 month

1
10
0 / 0

[Bug 1200919] New: kube-proxy should start when network is ready

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1200919 Bug ID: 1200919 Summary: kube-proxy should start when network is ready Product: Fedora Version: rawhide Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: leon(a)bcl.bz QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: kube-proxy is unable to start if network interface is not initialised yet Version-Release number of selected component (if applicable): kubernetes-0.12.0-0.4.gita4d871a.fc23 How reproducible: Steps to Reproduce: 1. yum install kubernet 2. configure kube-proxy (etcd url, etc), run systemctl start kube-proxy and make sure it's running properly 3. systemctl enable kube-proxy 4. reboot Actual results: traceback in log, systemctl status kube-proxy say it's not running Expected results: no traceback in logs, systemctl status kube-proxy should say it's running properly Additional info: This patch helps: --- contrib/init/systemd/kube-proxy.service.orig 2015-03-07 20:33:29.765178753 +0300 +++ contrib/init/systemd/kube-proxy.service 2015-03-07 20:34:19.008530113 +0300 @@ -1,6 +1,7 @@ [Unit] Description=Kubernetes Kube-Proxy Server Documentation=https://github.com/GoogleCloudPlatform/kubernetes +After=network.target [Service] EnvironmentFile=-/etc/kubernetes/config -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 1 month

1
9
0 / 0

[Bug 1200969] New: apiserver needs tmpfiles.d file to create CA cert

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1200969 Bug ID: 1200969 Summary: apiserver needs tmpfiles.d file to create CA cert Product: Fedora Version: rawhide Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: eparis(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com https://github.com/GoogleCloudPlatform/kubernetes/pull/3602 -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 1 month

1
11
0 / 0

[Bug 1200502] New: etcd service does not start on f21 server

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1200502 Bug ID: 1200502 Summary: etcd service does not start on f21 server Product: Fedora Version: 21 Component: etcd Assignee: lacypret(a)gmail.com Reporter: avagarwa(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: 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 Description of problem: etcd service does not start on f21 server And I get following logs: systemctl status etcd ● etcd.service - Etcd Server Loaded: loaded (/usr/lib/systemd/system/etcd.service; enabled) Active: failed (Result: exit-code) since Tue 2015-03-10 12:06:50 EDT; 24min ago Process: 721 ExecStart=/usr/bin/etcd (code=exited, status=1/FAILURE) Main PID: 721 (code=exited, status=1/FAILURE) Mar 10 12:06:50 localhost.localdomain systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE Mar 10 12:06:50 localhost.localdomain systemd[1]: Unit etcd.service entered failed state. Mar 10 12:06:50 localhost.localdomain systemd[1]: etcd.service failed. [root@localhost ~]# journalctl -b -u etcd -- Logs begin at Mon 2015-03-09 14:20:10 EDT, end at Tue 2015-03-10 12:31:37 EDT. -- Mar 10 12:06:50 localhost.localdomain systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE Mar 10 12:06:50 localhost.localdomain systemd[1]: Unit etcd.service entered failed state. Mar 10 12:06:50 localhost.localdomain systemd[1]: etcd.service failed. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Install a fedora 21 server vm from http://download.devel.redhat.com/released/F-21/GOLD/Server/x86_64/os/ 2. Install etcd 3. run etcd as follows: systemctl start etcd Actual results: Error Expected results: Working etcd service. Additional info: Manual /bin/etcd starts a service so not sure if everything is fine with the running service. -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 1 month

1
10
0 / 0

[Bug 1055712] Review Request: docker - Automates deployment of containerized applications

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1055712 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA --- Comment #21 from Fedora Update System <updates(a)fedoraproject.org> --- Package docker-1.5.0-24.git5ebfacd.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing docker-1.5.0-24.git5ebfacd.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4619/docker-1.5.0-24.... then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 1 month

1
0
0 / 0

[Bug 1055712] Review Request: docker - Automates deployment of containerized applications

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1055712 --- Comment #20 from Fedora Update System <updates(a)fedoraproject.org> --- docker-1.5.0-25.git5ebfacd.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/docker-1.5.0-25.git5ebfacd.fc22 -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 1 month

1
0
0 / 0

Broken dependencies: kubernetes

by Fedora Koji Build System

kubernetes has broken dependencies in the F-22 tree: On x86_64: kubernetes-0.12.0-0.9.git53b25a7.fc22.x86_64 requires docker Please resolve this as soon as possible.

9 years, 1 month

1
0
0 / 0

Broken dependencies: golang-github-fsouza-go-dockerclient

by Fedora Koji Build System

golang-github-fsouza-go-dockerclient has broken dependencies in the F-22 tree: On x86_64: golang-github-fsouza-go-dockerclient-devel-0.2.1-4.git0758f40.fc22.x86_64 requires golang(github.com/docker/docker/pkg/fileutils) golang-github-fsouza-go-dockerclient-devel-0.2.1-4.git0758f40.fc22.x86_64 requires golang(github.com/docker/docker/pkg/archive) Please resolve this as soon as possible.

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang March 2015