Bug 1578204 - [DOCS] system container install on RHEL result in RPM install
Summary: [DOCS] system container install on RHEL result in RPM install
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.10.0
Assignee: Alex Dellapenta
QA Contact: Johnny Liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 03:29 UTC by Weihua Meng
Modified: 2018-08-08 19:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-08 19:18:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Weihua Meng 2018-05-15 03:29:41 UTC
Description of problem:
system container install on RHEL result in RPM install

Version-Release number of the following components:
openshift-ansible-3.10.0-0.41.0

How reproducible:
Always

Steps to Reproduce:
1. Install OCP on RHEL with 
containerized=true
openshift_use_system_containers=true
system_images_registry=***.openshift.com


Actual results:
[root@qe-wmengr75sysgcs-master-etcd-1 ~]# systemctl cat atomic-openshift-node.service 
# /etc/systemd/system/atomic-openshift-node.service
[Unit]
Description=OpenShift Node
After=docker.service
After=chronyd.service
After=ntpd.service
Wants=docker.service
Documentation=https://github.com/openshift/origin
Wants=dnsmasq.service
After=dnsmasq.service

[Service]
Type=notify
EnvironmentFile=/etc/sysconfig/atomic-openshift-node
ExecStart=/usr/local/bin/openshift-node
LimitNOFILE=65536
LimitCORE=infinity
WorkingDirectory=/var/lib/origin/
SyslogIdentifier=atomic-openshift-node
Restart=always
RestartSec=5s
TimeoutStartSec=300
OOMScoreAdjust=-999

[Install]
WantedBy=multi-user.target

# systemctl status atomic-openshift-node.service -l
● atomic-openshift-node.service - OpenShift Node
   Loaded: loaded (/etc/systemd/system/atomic-openshift-node.service; enabled; vendor preset: disabled)
   Active: active (running) since 一 2018-05-14 21:45:39 EDT; 50min ago
     Docs: https://github.com/openshift/origin
 Main PID: 26809 (hyperkube)
   CGroup: /system.slice/atomic-openshift-node.service
           └─26809 /usr/bin/hyperkube kubelet --v=5 --address=0.0.0.0 --allow-privileged=true --anonymous-auth=true --authentication-token-webhook=true --authentication-token-webhook-cache-ttl=5m 


Expected results:
system container used.

ExecStartPre=/bin/bash -c 'export -p > /run/atomic-openshift-node-env'
ExecStart=/usr/bin/runc --systemd-cgroup run 'atomic-openshift-node'
ExecStop=/usr/bin/runc --systemd-cgroup kill 'atomic-openshift-node'


   CGroup: /system.slice/atomic-openshift-node.service
           └─20654 /usr/bin/runc --systemd-cgroup run atomic-openshift-node

Comment 2 Johnny Liu 2018-05-15 06:18:58 UTC
Seem like this is intended introduced by https://github.com/openshift/openshift-ansible/pull/8329, QE open this bug want to have a confirm, if we only support:
1. for a install on RHEL, only rpm install method
2. for a install on AH, only node system container install method


If yes, we need turn this bug into doc bug to notify customer.

Comment 3 Scott Dodson 2018-05-15 12:48:58 UTC
Right, we only support RPM based installs on normal RHEL. We're going to be doing an audit of documentation to clarify this.

Comment 4 Vikram Goyal 2018-05-15 12:55:49 UTC
Scott - we already have a note here about this: https://docs.openshift.com/container-platform/3.9/install_config/install/advanced_install.html#overview

Is there more we need to update/add?

Comment 5 Scott Dodson 2018-05-15 19:08:06 UTC
Vikram,

That note looks to deal with where you're running the installer. Whereas this bug relates to the fact that in 3.10 we only support two options. RPM based installs on RHEL and System Container based installs on Atomic Host.

Comment 8 Johnny Liu 2018-06-08 02:30:10 UTC
LGTM, leave some comments about etcd in the PR, but that is another issue, verify this bug.


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