config_controller --kubernetes failed during applying controller manifest

Bug #1816199 reported by Juan Carlos Alonso
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
Low
David Sullivan

Bug Description

Title
-----

'config_controller --kubernetes' failed during '06/08 Applying controller manifest'

Brief Description
-----------------

Configuration failed to apply controller manifest.

Severity
--------

<Critical: System/Feature is not usable after the defect>

Steps to Reproduce
------------------

sudo config_controller --kubernetes

Expected Behavior
------------------

Configuration applied

Actual Behavior
----------------

01/08: Creating bootstrap configuration ... DONE
02/08: Applying bootstrap manifest ... DONE
03/08: Persisting local configuration ... DONE
04/08: Populating initial system inventory ... DONE
05/08: Creating system configuration ... DONE
06/08: Applying controller manifest ... Failed to execute controller manifest

Configuration failed: Failed to apply controller manifest...

2019-02-15T15:51:26.511 Error: 2019-02-15 15:51:26 +0000 /Stage[main]/Platform::Kubernetes::Master::Init/Exec[configure master node]/returns: change from notrun to 0 failed: Command exceeded timeout

Reproducibility
---------------

<Reproducible/100%>

System Configuration
--------------------

Containers Virtual Environment:
  - Simplex

Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :
Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :
Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :
Revision history for this message
Frank Miller (sensfan22) wrote :

Please include the load used (from the bug template), ie:

Branch/Pull Time/Commit
-----------------------
Branch and the time when code was pulled or git commit

Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :
Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :

ISO: 20190215T060000Z
Branch: master

Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :

Issue still present on ISO 20190218T060000Z

Revision history for this message
David Sullivan (dsullivanwr) wrote :

I tested with 20190218T060000Z this morning in a virtual simplex setup and everything completed normally.

How is your virtual environment configured? Containers initialization requires internet access. Is this setup behind a proxy?

As a reminder the steps to setup and install a simplex virtual environment can be found here: https://wiki.openstack.org/wiki/StarlingX/Containers/Installation

Revision history for this message
Juan Carlos Alonso (juancarlosa) wrote :

I tried with 20190218T060000Z two times and a coworker too, got the same results.
But, with ISOs from 2/19 (yesterday) and 2/20 (today) I could install STX and setup without problems.
So, this issue is not reproducing with latest ISOs, I think could be closed.

Revision history for this message
Ghada Khalil (gkhalil) wrote :

As per the latest note from JC, this issue is not reproducible. Marking as Invalid

Changed in starlingx:
importance: Undecided → Low
assignee: nobody → David Sullivan (dsullivanwr)
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.