[Starlingx-discuss] Sanity updates

[Miller, Frank]

As also mentioned on today's containerization call, Don Penney has now updated the docker builds to use the OpenStack Stein branch and Angie Wang has a commit to switch the system application-upload stx-openstack command to pull the "stable" aka Stein docker images.

Once this commit is merged today, the recent sanity issues should be addressed: https://review.openstack.org/#/c/650436/

Frank

From: Miller, Frank
Sent: Friday, April 05, 2019 11:29 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: RE: Sanity updates

An update on the 2nd issue where VMs fail to launch: Gerry has confirmed the issue is due to using a nova docker image from OpenStack master.  Don Penney is updating the docker image builds to use the OpenStack Stein branches.  After re-testing confirms these docker images are sane, he will work to switch the CENGN builds over to the Stein branches.

Frank

From: Miller, Frank
Sent: Wednesday, April 03, 2019 10:48 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Sanity updates

Folks:

I took an action on the containers community call to send out an update on the current sanity issues.


1.       AIO-SX: This configuration should now be ready for use.

*         Bart Wensley solved LP 1820928<https://bugs.launchpad.net/starlingx/+bug/1820928> which turned out to be a bug in kubelet where it was hitting a limit of 250 http2 streams in a single connection.


2.       Other multi-server configs: An intermittent issue still exists when launching VMs resulting in the VMs failing to be scheduled. Tracked under LPs 1821841<https://bugs.launchpad.net/starlingx/+bug/1821841> & 1822116<https://bugs.launchpad.net/starlingx/+bug/1822116>

*         Gerry Kopec continues to investigate intermittent issues with the nova-placement pod.  When issue occurs VMs cannot be launched.

*         Issue is with nova-compute unable to get requests processed to one of the nova-placement pods running on each controller.

*         Current theory is this is related to our docker images using OpenStack master and a recent nova commit in the nova placement area is impacting the placement pod.  Gerry expects to prove or disprove the theory later today.

Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190408/029c35bb/attachment.html>