Re: [Starlingx-discuss] 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@lists.starlingx.io' <starlingx-discuss@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
On Fri, Apr 5, 2019 at 10:29 AM Miller, Frank <Frank.Miller@windriver.com> wrote:
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.
Timing is everything, they say... I just finished resetting the stx-nova repo [0] to track upstream nova: * the old master branch is now stx/old-master for reference * master branch is a snapshot of upstream master as of about 30 min ago * stable/stein branch is a snapshot of upstream stable/stein as of about 30 min ago * stx/stein is our working copy of stable/stein and where anything we backport should land. Big Note: I am thinking about keeping a policy of periodically rebasing stx/stein on stable/stein to keep a clear history as we move forward, making it easier to see what we have added. That possibly means doing it next week when the final stein tag is added. Thoughts? Force pushes can be inconvenient for developers but I am thinking the price may be worth the return on a wider scale. dt Also, I am going to re-post this as a top-level message to make sure it get seen...let's do follow-up conversations there [0] https://github.com/starlingx-staging/stx-nova -- Dean Troyer dtroyer@gmail.com
participants (2)
-
Dean Troyer
-
Miller, Frank