Bug 1371708 – atomic-openshift-node service wasn't reload on containerized env.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1371708 - atomic-openshift-node service wasn't reload on containerized env.

Summary:	atomic-openshift-node service wasn't reload on containerized env.

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Upgrade (Show other bugs)
Sub Component:
Version:	3.2.1
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	3.2.1
Assigned To:	Scott Dodson
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1371004
Blocks:
	Show dependency tree / graph

Reported:	2016-08-30 17:35 EDT by Scott Dodson
Modified:	2016-09-12 13:36 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	openshift-ansible-3.2.28-1.git.0.5a85fc5.el7
Doc Type:	Bug Fix
Doc Text:	Previously updates to the containerized atomic-openshift-node service were not properly reloaded during upgrades. We have corrected this error ensuring that the service is reloaded during upgrades.
Story Points:	---
Clone Of:	1371004
Environment:
Last Closed:	2016-09-12 13:36:44 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:1853	normal	SHIPPED_LIVE	Important: Red Hat OpenShift Enterprise 3.2 security update and bug fix update	2016-09-12 17:33:16 EDT

Groups: None (edit)

Comment 3 Anping Li 2016-08-31 22:09:56 EDT

After upgrade using atomic-openshift-utils-3.2.25-1,  the warning message is still exist.


[root@host6master ~]# systemctl status atomic-openshift-node
● atomic-openshift-node.service
   Loaded: loaded (/etc/systemd/system/atomic-openshift-node.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2016-08-31 21:45:03 EDT; 22min ago
  Process: 11528 ExecStop=/usr/bin/docker stop atomic-openshift-node (code=exited, status=0/SUCCESS)
  Process: 11895 ExecStartPost=/usr/bin/sleep 10 (code=exited, status=0/SUCCESS)
  Process: 11887 ExecStartPre=/usr/bin/docker rm -f atomic-openshift-node (code=exited, status=1/FAILURE)
 Main PID: 11894 (docker-current)
   Memory: 9.2M
<----snip---->
22:07:48.142651   12106 manager.go:1024] Using docker native exec to run cmd [/bin/sh -i -c MYSQL_PWD='tgSJ3W4WT4fhpPFY'...fb55de5333a}
Warning: atomic-openshift-node.service changed on disk. Run 'systemctl daemon-reload' to reload units.

Comment 4 Scott Dodson 2016-08-31 22:18:01 EDT

Sorry, this wasn't fixed until 3.2.27. The latest is now openshift-ansible-3.2.28-1.git.0.5a85fc5.el7

Comment 6 errata-xmlrpc 2016-09-12 13:36:44 EDT

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://access.redhat.com/errata/RHSA-2016:1853

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