RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1289762 - /etc/kubernetes/config has typo for privileged containers option
Summary: /etc/kubernetes/config has typo for privileged containers option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kubernetes
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Chaloupka
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-08 22:04 UTC by Micah Abbott
Modified: 2016-03-04 15:06 UTC (History)
2 users (show)

Fixed In Version: kubernetes-1.2.0-0.2.alpha1.git8632732.el7_2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-16 16:30:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0184 0 normal SHIPPED_LIVE kubernetes bug fix and enhancement update 2016-02-16 21:29:08 UTC

Description Micah Abbott 2015-12-08 22:04:49 UTC 
Description of problem:
The '/etc/kubernetes/config' file has a typo in the 'KUBE_ALLOW_PRIV' option; it lists '--allow_privileged' as the option to the 'kubelet', but the correct option is '--allow-privileged'.  Note: dash vs underscore

Version-Release number of selected component (if applicable):

kubernetes-master-1.0.3-0.2.gitb9a88a7.el7.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Install kubernetes-master
2. Inspect /etc/kubernetes/config
3.

Actual results:

Option listed is '--allow_privileged'

Expected results:

Option should be '--allow-privileged'

Additional info:

See upstream docs:  http://kubernetes.io/v1.1/docs/admin/kubelet.html



-bash-4.2# rpm -q kubernetes-master
kubernetes-master-1.0.3-0.2.gitb9a88a7.el7.x86_64
-bash-4.2# rpm -ql kubernetes-master 
/etc/kubernetes
/etc/kubernetes/apiserver
/etc/kubernetes/config
/etc/kubernetes/controller-manager
/etc/kubernetes/scheduler
/usr/bin/kube-apiserver
/usr/bin/kube-controller-manager
/usr/bin/kube-scheduler
/usr/bin/kube-version-change
/usr/lib/systemd/system/kube-apiserver.service
/usr/lib/systemd/system/kube-controller-manager.service
/usr/lib/systemd/system/kube-scheduler.service
/usr/lib/tmpfiles.d/kubernetes.conf
/usr/share/doc/kubernetes-master-1.0.3
/usr/share/doc/kubernetes-master-1.0.3/CONTRIB.md
/usr/share/doc/kubernetes-master-1.0.3/CONTRIBUTING.md
/usr/share/doc/kubernetes-master-1.0.3/DESIGN.md
/usr/share/doc/kubernetes-master-1.0.3/LICENSE
/usr/share/doc/kubernetes-master-1.0.3/README.md
/usr/share/man/man1/kube-apiserver.1.gz
/usr/share/man/man1/kube-controller-manager.1.gz
/usr/share/man/man1/kube-scheduler.1.gz
-bash-4.2# cat /etc/kubernetes/config 
###
# kubernetes system config
#
# The following values are used to configure various aspects of all
# kubernetes services, including
#
#   kube-apiserver.service
#   kube-controller-manager.service
#   kube-scheduler.service
#   kubelet.service
#   kube-proxy.service
# logging to stderr means we get it in the systemd journal
KUBE_LOGTOSTDERR="--logtostderr=true"

# journal message level, 0 is debug
KUBE_LOG_LEVEL="--v=0"

# Should this cluster be allowed to run privileged docker containers
KUBE_ALLOW_PRIV="--allow_privileged=false"

# How the controller-manager, scheduler, and proxy find the apiserver
KUBE_MASTER="--master=http://127.0.0.1:8080"
Comment 5 errata-xmlrpc 2016-02-16 16:30:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0184.html
Comment 6 John Boero 2016-03-04 14:57:21 UTC 
Hi I just ran into this in Fedora 23 as well.  Suddenly pulled the updates that fixed it and left me confused.  Note that the man pages are still ambiguous, with references to both --api_servers and --api-servers etc.  Very confusing for users and no helpful output when mistaken.  Should another bug be filed for documentation?  .rpmnew config files leave me scratching my head with a partially functional cluster.

Thanks!
JohnnyB
Comment 7 Jan Chaloupka 2016-03-04 15:06:08 UTC 
Hi John,

atm both form of flags with dashes/underscores are supported. Flags with underscore are deprecated although still supported for backward compatibility.

If there are both forms supported, prefer flags with dashes.

If there is a flag that should be supported and is not, please report a bug.

Jan
Note You need to log in before you can comment on or make changes to this bug.