Bug 1278128 - quick installer clobbers existing "OPTIONS" field
quick installer clobbers existing "OPTIONS" field
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Scott Dodson
Xiaoli Tian
Depends On:
  Show dependency treegraph
Reported: 2015-11-04 12:32 EST by Erik M Jacobs
Modified: 2017-08-24 16:50 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-24 16:50:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Erik M Jacobs 2015-11-04 12:32:21 EST
When you have various things in the /etc/sysconfig/docker file OPTIONS line.

For example, if you start with:

OPTIONS='--selinux-enabled --insecure-registry foofoofoo --insecure-registry barbarbar'

These options are clobbered/lost and only the registry service IP and etc. ends up being there.

There is a workaround by moving these into the "ADD_REGISTRY" line, but that's not intuitive...
Comment 2 Jason DeTiberus 2015-11-04 12:57:17 EST
For the most part, this is working as intended.

We should better document how to set the various registry settings in the advanced docs, and rely on ansible to handle that config.  There are other docker options that we are setting that would make parsing the existing settings and modifying them a bit difficult (ensuring selinux is set properly, and the log driver options we currently support).

and we would also need to add support for setting these options in the quick installer.

That said...  We should not be setting --insecure-registry={{ openshift.node.portal_net }} in that file, since we now provide instructions on how to create a secure registry.

I also do not see an issue with adding support for appending arbitrary docker options as well.

I'm going to go ahead and mark this as UpcomingRelease though, since I do not believe

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