Bug 1609907 – [free-int] Timeout waiting to approve node during control-plane upgrade

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

Bug 1609907 - [free-int] Timeout waiting to approve node during control-plane upgrade

Summary:	[free-int] Timeout waiting to approve node during control-plane upgrade

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.11.0
Assigned To:	Russell Teague
QA Contact:	liujia
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1612144 (view as bug list)
Depends On:
Blocks:	1614003
	Show dependency tree / graph

Reported:	2018-07-30 15:13 EDT by Justin Pierce
Modified:	2018-10-11 03:23 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: Upgrade tasks include node CSR approval which is no longer necessary once nodes are at 3.10. Fix: The node approval task has been removed from the node upgrade playbook.
Story Points:	---
Clone Of:
Clones:	1614003 (view as bug list)
Environment:
Last Closed:	2018-10-11 03:22:47 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	RHBA-2018:2652	None	None	None	2018-10-11 03:23 EDT

Groups: None (edit)

Description Justin Pierce 2018-07-30 15:13:52 EDT

Description of problem:

During an upgrade of the control-plane of a test cluster using 3.11.0-0.10.0:
11:26:55 fatal: [free-int-master-3c664 -> None]: FAILED! => {"changed": false, "finished": false, "msg": "Timed out accepting certificate signing requests. Failing as requested.", "nodes": [{"client_accepted": false, "csrs": {}, "denied": false, "name": "ip-172-31-50-177.ec2.internal", "server_accepted": false}], "results": [], "state": "approve", "timeout": true}



Version-Release number of the following components:
3.11.0-0.10.0 

How reproducible:
Retrying the operation produced the same result.

Steps to Reproduce:
1. Run control plane upgrade

Comment 2 Russell Teague 2018-07-30 15:18:46 EDT

When testing, skipping this task[1] would allow the upgrade to complete.

[1] https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_node/tasks/upgrade/restart.yml#L48-L53

Comment 3 Scott Dodson 2018-07-31 15:26:49 EDT

We're quite certain that this will also happen during 3.10.z.

Comment 4 Russell Teague 2018-08-08 15:31:46 EDT

For 3.11: https://github.com/openshift/openshift-ansible/pull/9488

Comment 5 openshift-github-bot 2018-08-10 11:30:40 EDT

Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/a1d87c62487f8d2454e8ddd759cddf8dd9233002
Merge pull request #9488 from mtnbikenc/fix-1609907

[Bug 1609907] Remove node CSR approval from upgrade in 3.11

Comment 6 Russell Teague 2018-08-13 08:44:48 EDT

*** Bug 1612144 has been marked as a duplicate of this bug. ***

Comment 7 Russell Teague 2018-08-13 08:45:35 EDT

openshift-ansible-3.11.0-0.14.0

Comment 8 liujia 2018-08-14 01:15:33 EDT

Verified on openshift-ansible-3.11.0-0.14.0.git.0.7bd4429None.noarch

Comment 9 Scott Dodson 2018-08-15 15:40:30 EDT

*** Bug 1612144 has been marked as a duplicate of this bug. ***

Comment 11 errata-xmlrpc 2018-10-11 03:22:47 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/RHBA-2018:2652

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