This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=low # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1784602,1784604 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
Hi Guilherme de Almeida, what's is the difference between this issue and https://bugzilla.redhat.com/show_bug.cgi?id=1784603? Is the former reported against kubernetes module?
> Hi Guilherme de Almeida, what's is the difference between this issue and > https://bugzilla.redhat.com/show_bug.cgi?id=1784603? Is the former reported > against kubernetes module? Hi Jan, I don't have sure what's the difference between the two. I found the entry 'kubernetes:1.10/kubernetes-1.10.3-1.module_2132+bd83c928' in our manifests file and also a similar bug entry for another kubernetes flaw[1]. So, it seems to be against the kubernetes module, let me know if this is not needed. [1]. https://bugzilla.redhat.com/show_bug.cgi?id=1753497
Hi, was this ever fixed?
The kubernetes module never got off the ground, and has been orphaned now. Nobody should be using this module. There are probably alternative ways to use openshift/kube.