Golang-updates December 2019

golang-updates@lists.fedoraproject.org

1 participants
5 discussions

[Bug 1431306] golang-github-digitalocean-godo-1.29.0 is available
by bugzilla＠redhat.com 13 Dec '19

13 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1431306 --- Comment #50 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> --- The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you. Please use URLs in your Source declarations if possible. - glide.yaml - glide.lock -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1431306] golang-github-digitalocean-godo-1.29.0 is available
by bugzilla＠redhat.com 13 Dec '19

13 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1431306 Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|golang-github-digitalocean- |golang-github-digitalocean- |godo-1.28.0 is available |godo-1.29.0 is available --- Comment #49 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> --- Latest upstream release: 1.29.0 Current version/release in rawhide: 1.15.0-2.fc31 URL: https://github.com/digitalocean/godo 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. Based on the information from anitya: https://release-monitoring.org/project/6804/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1315472] kube-controller-manager ignores --master argument
by bugzilla＠redhat.com 10 Dec '19

10 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1315472 hong <511173846(a)qq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |511173846(a)qq.com --- Comment #5 from hong <511173846(a)qq.com> --- ult config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined Dec 11 10:35:19 master01 kube-controller-manager: invalid configuration: no configuration has been provided Dec 11 10:35:19 master01 systemd: kube-controller-manager.service: main process exited, code=exited, status=1/FAILURE Dec 11 10:35:19 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:19 master01 systemd: kube-controller-manager.service failed. Dec 11 10:35:19 master01 systemd: kube-controller-manager.service holdoff time over, scheduling restart. Dec 11 10:35:19 master01 systemd: --experimental-cluster-signing-duration=87600h0m0s': /opt/k8s/conf/kube-controller-manager.env Dec 11 10:35:19 master01 kube-controller-manager: I1211 10:35:19.911712 124830 serving.go:319] Generated self-signed cert in-memory Dec 11 10:35:19 master01 kube-controller-manager: W1211 10:35:19.911767 124830 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. Dec 11 10:35:19 master01 kube-controller-manager: W1211 10:35:19.911774 124830 client_config.go:546] error creating inClusterConfig, falling back to default config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined Dec 11 10:35:19 master01 kube-controller-manager: invalid configuration: no configuration has been provided Dec 11 10:35:19 master01 systemd: kube-controller-manager.service: main process exited, code=exited, status=1/FAILURE Dec 11 10:35:19 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:19 master01 systemd: kube-controller-manager.service failed. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service holdoff time over, scheduling restart. Dec 11 10:35:20 master01 systemd: --experimental-cluster-signing-duration=87600h0m0s': /opt/k8s/conf/kube-controller-manager.env Dec 11 10:35:20 master01 kube-controller-manager: I1211 10:35:20.527572 124838 serving.go:319] Generated self-signed cert in-memory Dec 11 10:35:20 master01 kube-controller-manager: W1211 10:35:20.527650 124838 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. Dec 11 10:35:20 master01 kube-controller-manager: W1211 10:35:20.527660 124838 client_config.go:546] error creating inClusterConfig, falling back to default config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined Dec 11 10:35:20 master01 kube-controller-manager: invalid configuration: no configuration has been provided Dec 11 10:35:20 master01 systemd: kube-controller-manager.service: main process exited, code=exited, status=1/FAILURE Dec 11 10:35:20 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service failed. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service holdoff time over, scheduling restart. Dec 11 10:35:20 master01 systemd: start request repeated too quickly for kube-controller-manager.service Dec 11 10:35:20 master01 systemd: Unit kube-controller-manager.service entered failed state. Dec 11 10:35:20 master01 systemd: kube-controller-manager.service failed. [root@master01 ansible]# cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [root@master01 ansible]# hi, when i install the kubernetes via binary,i got the same bug. the install version is kubernetes-server-linux-amd64-1.16.tar.gz and my system environment is CentOS Linux release 7.6.1810 (Core). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1431306] golang-github-digitalocean-godo-1.28.0 is available
by bugzilla＠redhat.com 04 Dec '19

04 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1431306 --- Comment #48 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> --- The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you. Please use URLs in your Source declarations if possible. - glide.yaml - glide.lock -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1431306] golang-github-digitalocean-godo-1.28.0 is available
by bugzilla＠redhat.com 04 Dec '19

04 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1431306 Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|golang-github-digitalocean- |golang-github-digitalocean- |godo-1.27.0 is available |godo-1.28.0 is available --- Comment #47 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> --- Latest upstream release: 1.28.0 Current version/release in rawhide: 1.15.0-2.fc31 URL: https://github.com/digitalocean/godo 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. Based on the information from anitya: https://release-monitoring.org/project/6804/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

Golang-updates December 2019