IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status"

Bug #1859641 reported by Peng Peng
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
zhipeng liu

Bug Description

Brief Description
-----------------
During the initial regular system setup, apply stx-openstack application failed. armada/stx-openstack-apply log shows that there a time out for waiting for the condition "grpc_status".

And the mariadb-ingress pods are not ready:
mariadb-ingress-5bb8b69fc8-czb7z 0/1 Running 0 5h18m dead:beef::8e22:765f:6121:eb4e controller-0 <none> <none>
mariadb-ingress-5bb8b69fc8-h8zx5 0/1 Running 0 5h18m dead:beef::a4ce:fec1:5423:e306 controller-1 <none> <none>

Severity
--------
Critical

Steps to Reproduce
------------------
install a Ipv6 system
apply stx-openstack application

TC-name: installation

Expected Behavior
------------------
applied

Actual Behavior
----------------
- apply failed
- mariadb-ingress pods are not ready:
mariadb-ingress-5bb8b69fc8-czb7z 0/1 Running 0 5h18m dead:beef::8e22:765f:6121:eb4e controller-0 <none> <none>
mariadb-ingress-5bb8b69fc8-h8zx5 0/1 Running 0 5h18m dead:beef::a4ce:fec1:5423:e306 controller-1 <none> <none>

Reproducibility
---------------
Unknown - first time this is tried on IPv6 system

System Configuration
--------------------
Multi-node system

Lab-name: WCp_71-75

Branch/Pull Time/Commit
-----------------------
20200111T023000Z

Last Pass
---------
unknown

Timestamp/Logs
--------------
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller [-] [chart=openstack-mariadb]: Error while installing release osh-openstack-mariadb: grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with:
        status = StatusCode.UNKNOWN
        details = "release osh-openstack-mariadb failed: timed out waiting for the condition"
        debug_error_string = "{"created":"@1578993242.085407734","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"release osh-openstack-mariadb failed: timed out waiting for the condition","grpc_status":2}"
>
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller Traceback (most recent call last):
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py", line 473, in install_release
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller metadata=self.metadata)
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 533, in __call__
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller return _end_unary_response_blocking(state, call, False, None)
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 467, in _end_unary_response_blocking
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller raise _Rendezvous(state, None, None, deadline)
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with:
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller status = StatusCode.UNKNOWN
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller details = "release osh-openstack-mariadb failed: timed out waiting for the condition"
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller debug_error_string = "{"created":"@1578993242.085407734","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"release osh-openstack-mariadb failed: timed out waiting for the condition","grpc_status":2}"
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller >
2020-01-14 09:14:02.085 458 ERROR armada.handlers.tiller ^[[00m
2020-01-14 09:14:02.087 458 DEBUG armada.handlers.tiller [-] [chart=openstack-mariadb]: Helm getting release status for release=osh-openstack-mariadb, version=0 get_release_status /usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py:539^[[00m
2020-01-14 09:14:02.230 458 DEBUG armada.handlers.tiller [-] [chart=openstack-mariadb]: GetReleaseStatus= name: "osh-openstack-mariadb"
info {
  status {
    code: FAILED
  }
  first_deployed {
    seconds: 1578991441
    nanos: 428638329
  }
  last_deployed {
    seconds: 1578991441
    nanos: 428638329
  }
  Description: "Release \"osh-openstack-mariadb\" failed: timed out waiting for the condition"
}

Test Activity
-------------
installation

Revision history for this message
Peng Peng (ppeng) wrote :
Yang Liu (yliu12)
summary: - stx-openstack app apply failed by time out waiting for the condition
- "grpc_status"
+ IPv6: stx-openstack app apply failed by time out waiting for the
+ condition "grpc_status"
description: updated
Yang Liu (yliu12)
tags: added: stx.retestneeded
Revision history for this message
Yang Liu (yliu12) wrote :

Comments from Joseph form initial investigation:

The helm charts are also pulled from the IPv4 address, I tried updating it to use the hostname, but unfortunately there seems to be a bug in build-helm-charts with the image-records not correctly parsing pulling from hosts with hyphens in the name.

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

stx.4.0 / high priority -- it seems that the openstack helm charts are not working for IPv6.
Assigning to the openstack PL/team for further investigation

tags: added: stx.containers
tags: added: stx.distro.openstack
Changed in starlingx:
importance: Undecided → High
status: New → Triaged
assignee: nobody → yong hu (yhu6)
Ghada Khalil (gkhalil)
tags: added: stx.4.0
Revision history for this message
Joseph Richard (josephrichard) wrote :

That helm chart issue was a separate issue affecting an ipv6 lab, and has been fixed.

mariadb is correctly binding to 0.0.0.0 [1] even in ipv6 configs. This can be overwritten by a change in the mariadb helm plugin [2] to override this in an ipv6 environment.

There is also a bug in openstack-helm-infra [3] that it will not enclose ipv6 addresses in square brackets resulting in them being unable to be parsed.

[1] https://github.com/openstack/openstack-helm-infra/blob/master/mariadb/values.yaml#L322
[2] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/helm/mariadb.py
[3] https://github.com/openstack/openstack-helm-infra/blame/master/mariadb/files/nginx.tmpl#L476

Revision history for this message
Peng Peng (ppeng) wrote :

Issue reproduced on
Lab: WCP_71_75
Load: 2020-01-22_20-00-00
log @
https://files.starlingx.kube.cengn.ca/launchpad/1859641

Revision history for this message
Peng Peng (ppeng) wrote :

Please ignore comment #5. I post the comment on the wrong place. Sorry about that

zhipeng liu (zhipengs)
Changed in starlingx:
assignee: yong hu (yhu6) → zhipeng liu (zhipengs)
Revision history for this message
Yan Chen (ychen2u) wrote :

@Peng, please share us the localhost.yml file you used to deploy the stx.

Revision history for this message
zhipeng liu (zhipengs) wrote :

Hi Pengpeng

As Yan said, we need your help to set up IPv6 environment for our Ipv6 related bug analysis.

Thanks!
Zhipeng

Changed in starlingx:
status: Triaged → Incomplete
Revision history for this message
Peng Peng (ppeng) wrote :

2020-01-22_20-00-00/lab/yow/cgcs-wildcat-71_75/localhost.yml

system_mode: duplex
dns_servers:
- 2620:10a:a001:a103::2

management_subnet: face::/64
management_multicast_subnet: ff05::1b:0/124
cluster_host_subnet: feed:beef::/64
cluster_pod_subnet: dead:beef::/64
cluster_service_subnet: fd04::/112

external_oam_subnet: 2620:10a:a001:a103::6:0/64
external_oam_gateway_address: 2620:10a:a001:a103::6:0
external_oam_floating_address: 2620:10A:A001:A103::1218
external_oam_node_0_address: 2620:10A:A001:A103::1215
external_oam_node_1_address: 2620:10A:A001:A103::1024

admin_password: Li69nux*
ansible_become_pass: Li69nux*
docker_http_proxy: http://yow-proxomatic.wrs.com:3128
pxeboot_subnet: 192.168.202.0/24
docker_no_proxy:
- registry.local
- tis-lab-registry.cumulus.wrs.com
docker_registries:
  quay.io:
    url: tis-lab-registry.cumulus.wrs.com:9001/wrcp-staging/quay.io
  docker.elastic.co:
    url: tis-lab-registry.cumulus.wrs.com:9001/wrcp-staging/docker.elastic.co
  gcr.io:
    url: tis-lab-registry.cumulus.wrs.com:9001/wrcp-staging/gcr.io
  k8s.gcr.io:
    url: tis-lab-registry.cumulus.wrs.com:9001/wrcp-staging/k8s.gcr.io
  docker.io:
    url: tis-lab-registry.cumulus.wrs.com:9001/wrcp-staging/docker.io
  defaults:
    type: docker
~

Revision history for this message
Yan Chen (ychen2u) wrote :

@Peng,
Please also share us a simplex localhost.yml.
I want to also try how to setup ipv6 env for a simplex setup.
Thanks!

Revision history for this message
Peng Peng (ppeng) wrote :

from WCP_112:
BUILD_ID="2020-02-18_10-46-00"

system_mode: simplex
dns_servers:
- 2620:10a:a001:a103::2

management_subnet: abcd:204::/64
management_multicast_subnet: ff05::1b:0/124

cluster_host_subnet: abcd:205::/64
cluster_pod_subnet: abcd:206::/64
cluster_service_subnet: abcd:207::/112

external_oam_subnet: 2620:10a:a001:a103::6:0/64
external_oam_gateway_address: 2620:10a:a001:a103::6:0
external_oam_floating_address: 2620:10a:a001:a103::148

admin_password: Li69nux*
ansible_become_pass: Li69nux*
pxeboot_subnet: 192.168.202.0/24
docker_http_proxy: http://yow-proxomatic.wrs.com:3128
docker_https_proxy: http://yow-proxomatic.wrs.com:3129
docker_no_proxy:
- registry.local
- tis-lab-registry.cumulus.wrs.com

Revision history for this message
Yan Chen (ychen2u) wrote :

Thanks a lot.

Yang Liu (yliu12)
Changed in starlingx:
status: Incomplete → Confirmed
zhipeng liu (zhipengs)
Changed in starlingx:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-armada-app (master)

Fix proposed to branch: master
Review: https://review.opendev.org/709984

Revision history for this message
zhipeng liu (zhipengs) wrote :

Hi Joseph,

I have tested it on simplex with my fix.
The above issue has already been fixed.

But I found rabbitmq got crash. Not sure if it is our setup issue, I'm checking on it.

controller-0:~$ kubectl -n openstack get po
NAME READY STATUS RESTARTS AGE
ingress-c74489c96-jsb7n 1/1 Running 0 17h
ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h
mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h
mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h
mariadb-server-0 1/1 Running 0 17h
osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h
osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h
osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h

2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0
2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}'
2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0
2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']'
2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server
2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain)

In /etc/hosts,you just found localhost4, no localhost6

# HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
fd01::1 controller
169.254.202.1 pxecontroller
fd00::3 oamcontroller
fd01::4 controller-platform-nfs
fd01::3 controller-1
fd01::2 controller-0
fd02::3 controller-1-cluster-host
fd02::2 controller-0-cluster-host
fd01::e8b6:66fe storage-0

Any comment?

Thanks!
Zhipeng

Revision history for this message
Peng Peng (ppeng) wrote :

The issue was reproduced on
WCP_71-75
20200303T000005Z
new log uploaded @https://files.starlingx.kube.cengn.ca/launchpad/1859641

From sysinv.log
HelmTillerFailure: Helm operation failure: Failed to retrieve releases: Helm operation failure: Failed to retrieve releases: Error: forwarding ports: error upgrading connection: unable to upgrade connection: error dialing backend: dial tcp 128.224.151.215:41003: connect: network is unreachable

From stx-openstack-apply_2020-03-04-18-54-52.log

 Chart deploy [openstack-mariadb] failed: armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: osh-openstack-mariadb - Tiller Message: b'Release "osh-openstack-mariadb" failed: timed out waiting for the condition'

Revision history for this message
zhipeng liu (zhipengs) wrote :

Hi

Pengpeng, this is known issue, need wait for the fix in #13 getting merged.

Thanks!
Zhipeng

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-armada-app (master)

Reviewed: https://review.opendev.org/709984
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=4aeacc3e171b6566586a7e93ed16f87d5ca375ca
Submitter: Zuul
Branch: master

commit 4aeacc3e171b6566586a7e93ed16f87d5ca375ca
Author: Zhipeng Liu <email address hidden>
Date: Thu Feb 27 01:28:58 2020 +0800

    Fix ipv6 address issue causing mariadb ingress not ready

    In nginx.tmpl, it not enclose ipv6 addresses in square brackets
    resulting in them being unable to be parsed, which cause mariadb
    ingress pod could not be ready.

    Tested it on both ipv4 and ipv6 simplex setup, it fixes mariadb
    ingress not ready issue.

    Upstream patch submitted as below
    https://review.opendev.org/#/c/710413/

    Partial-Bug: 1859641

    Change-Id: Ic7726eea671bbedf4f37fbe31965bc8fffd2e8cd
    Signed-off-by: Zhipeng Liu <email address hidden>

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

@Peng, please retest with the above fix and let us know the results. Thanks.

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

As per the mailing list, a follow-up fix for rabbitmq is required to fully address this issue:
http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008073.html

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/714034

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-armada-app (master)

Fix proposed to branch: master
Review: https://review.opendev.org/714038

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/714034
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=24a533d800b2c57b84f1086593fe5f04f95fe906
Submitter: Zuul
Branch: master

commit 24a533d800b2c57b84f1086593fe5f04f95fe906
Author: Zhipeng Liu <email address hidden>
Date: Fri Mar 20 23:10:31 2020 +0800

    Fix rabbitmq could not bind port to ipv6 address issue

    When we use Armada to deploy openstack service for ipv6, rabbitmq
    pod could not start listen on [::]:5672 and [::]:15672.
    For ipv6, we need an override for configuration file.

    Upstream patch link is:
    https://review.opendev.org/#/c/714027/

    Test pass for deploying rabbitmq service on both ipv4 and ipv6 setup

    Partial-Bug: 1859641

    Change-Id: I6495c45fbd8cc1de3c9f5d9ef5003447079d91b8
    Signed-off-by: Zhipeng Liu <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-armada-app (master)

Reviewed: https://review.opendev.org/714038
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=530933f9c2d6eb762a40a323bf11520b68fb29db
Submitter: Zuul
Branch: master

commit 530933f9c2d6eb762a40a323bf11520b68fb29db
Author: Zhipeng Liu <email address hidden>
Date: Fri Mar 20 23:50:12 2020 +0800

    Fix rabbitmq could not bind port to ipv6 address issue

    When we use Armada to deploy openstack service for ipv6, rabbitmq
    pod could not start listen on [::]:5672 and [::]:15672.
    For ipv6, we need an override for configuration file.

    Upstream patch link is:
    https://review.opendev.org/#/c/714027/

    Partial-Bug: 1859641

    Depends-on: https://review.opendev.org/#/c/714034/
    Change-Id: I34e92afe291c4b7f31f53f1b974ad5fdc47b9560
    Signed-off-by: Zhipeng Liu <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-armada-app (master)

Fix proposed to branch: master
Review: https://review.opendev.org/714894

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/714898

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/714898
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=45c9fe2d3571574b9e0503af108fe7c1567007db
Submitter: Zuul
Branch: master

commit 45c9fe2d3571574b9e0503af108fe7c1567007db
Author: Zhipeng Liu <email address hidden>
Date: Thu Mar 26 01:58:34 2020 +0800

    Add ipv6 support for novncproxy_base_url.

    For ipv6 address, we need url with below format
    [ip]:port

    Partial-Bug: 1859641

    Change-Id: I01a5cd92deb9e88c2d31bd1e16e5bce1e849fcc7
    Signed-off-by: Zhipeng Liu <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/716137

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (f/centos8)
Download full text (32.3 KiB)

Reviewed: https://review.opendev.org/716137
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=cb4cf4299c2ec10fb2eb03cdee3f6d78a6413089
Submitter: Zuul
Branch: f/centos8

commit 16477935845e1c27b4c9d31743e359b0aa94a948
Author: Steven Webster <email address hidden>
Date: Sat Mar 28 17:19:30 2020 -0400

    Fix SR-IOV runtime manifest apply

    When an SR-IOV interface is configured, the platform's
    network runtime manifest is applied in order to apply the virtual
    function (VF) config and restart the interface. This results in
    sysinv being able to determine and populate the puppet hieradata
    with the virtual function PCI addresses.

    A side effect of the network manifest apply is that potentially
    all platform interfaces may be brought down/up if it is determined
    that their configuration has changed. This will likely be the case
    for a system which configures SR-IOV interfaces before initial
    unlock.

    A few issues have been encountered because of this, with some
    services not behaving well when the interface they are communicating
    over suddenly goes down.

    This commit makes the SR-IOV VF configuration much more targeted
    so that only the operation of setting the desired number of VFs
    is performed.

    Closes-Bug: #1868584
    Depends-On: https://review.opendev.org/715669
    Change-Id: Ie162380d3732eb1b6e9c553362fe68cbc313ae2b
    Signed-off-by: Steven Webster <email address hidden>

commit 45c9fe2d3571574b9e0503af108fe7c1567007db
Author: Zhipeng Liu <email address hidden>
Date: Thu Mar 26 01:58:34 2020 +0800

    Add ipv6 support for novncproxy_base_url.

    For ipv6 address, we need url with below format
    [ip]:port

    Partial-Bug: 1859641

    Change-Id: I01a5cd92deb9e88c2d31bd1e16e5bce1e849fcc7
    Signed-off-by: Zhipeng Liu <email address hidden>

commit d119336b3a3b24d924e000277a37ab0b5f93aae1
Author: Andy Ning <email address hidden>
Date: Mon Mar 23 16:26:21 2020 -0400

    Fix timeout waiting for CA cert install during ansible replay

    During ansible bootstrap replay, the ssl_ca_complete_flag file is
    removed. It expects puppet platform::config::runtime manifest apply
    during system CA certificate install to re-generate it. So this commit
    updated conductor manager to run that puppet manifest even if the CA cert
    has already installed so that the ssl_ca_complete_flag file is created
    and makes ansible replay to continue.

    Change-Id: Ic9051fba9afe5d5a189e2be8c8c2960bdb0d20a4
    Closes-Bug: 1868585
    Signed-off-by: Andy Ning <email address hidden>

commit 24a533d800b2c57b84f1086593fe5f04f95fe906
Author: Zhipeng Liu <email address hidden>
Date: Fri Mar 20 23:10:31 2020 +0800

    Fix rabbitmq could not bind port to ipv6 address issue

    When we use Armada to deploy openstack service for ipv6, rabbitmq
    pod could not start listen on [::]:5672 and [::]:15672.
    For ipv6, we need an override for configuration file.

    Upstream patch link is:
    https://review.opendev.org/#/c/714027/

    Test pass for deploying rabbitmq service on both ipv...

tags: added: in-f-centos8
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/716524

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-armada-app (master)

Reviewed: https://review.opendev.org/714894
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=b07282ff550c156b0f1466aef054ce89fb1b8d3e
Submitter: Zuul
Branch: master

commit b07282ff550c156b0f1466aef054ce89fb1b8d3e
Author: Zhipeng Liu <email address hidden>
Date: Thu Mar 26 01:49:54 2020 +0800

    Fix openstack services could not bind port to ipv6 address issue

    Need to set bind_host to :: instead of "0.0.0.0" and host listen
    ip to ::
    Otherwise it will only bind to port to ipv4 address.

    Partial-Bug: 1859641

    Test pass on both ipv4 and ipv6 simplex setup

    Depends-on: https://review.opendev.org/714898
    Change-Id: I51bd1a65d7728c74f6c69b87e57e3fc42e8adc15
    Signed-off-by: Zhipeng Liu <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/716524
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=e6dd6fee38f1f180c4b611db4570021eb7c85bae
Submitter: Zuul
Branch: master

commit e6dd6fee38f1f180c4b611db4570021eb7c85bae
Author: Zhipeng Liu <email address hidden>
Date: Thu Apr 2 01:03:34 2020 +0800

    Add mariadb database config override to support ipv6

    Override "config_override" in helm/mariadb.py according to ip version.
    Test Pass on both ipv4 and ipv6 simplex.

    Closes-Bug: 1859641

    Change-Id: Ic15865105f305a8d7b93187eb51ef5aaf3d7d96e
    Signed-off-by: Zhipeng Liu <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
Revision history for this message
Peng Peng (ppeng) wrote :

Verified on
Lab: WCP_71_75
Load: 2020-04-20_20-00-00

tags: removed: stx.retestneeded
Revision history for this message
Yang Liu (yliu12) wrote :

Readd retestneeded tag - previous testing was invalid - was meant to be posted for a different LP.

tags: added: stx.retestneeded
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/729812

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (f/centos8)
Download full text (37.5 KiB)

Reviewed: https://review.opendev.org/729812
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=539d476456277c22d0dcbc3cbbc832e623242264
Submitter: Zuul
Branch: f/centos8

commit 320cc40de8518787c2be234d7fdf88ec0a462df2
Author: Don Penney <email address hidden>
Date: Wed May 13 13:06:11 2020 -0400

    Add auto-versioning to starlingx/config packages

    This update makes use of the PKG_GITREVCOUNT variable to auto-version
    the packages in this repo.

    Change-Id: I3a2c8caeb4b4647608978b1f2ccfcf0661508803
    Depends-On: https://review.opendev.org/727837
    Story: 2006166
    Task: 39766
    Signed-off-by: Don Penney <email address hidden>

commit d9f2aea0fb228ed69eb9c9262e29041eedabc15d
Author: Sharath Kumar K <email address hidden>
Date: Wed Apr 22 16:22:22 2020 +0200

    De-branding in starlingx/config: CGCS -> StarlingX

    1. Rename CGCS to StarlingX for .spec files

    Test:
    After the de-brand change, bootimage.iso has been built in the flock
    Layer and installed on the dev machine to validate the changes.

    Please note, doing de-brand changes in batches, this is batch9 changes.

    Story: 2006387
    Task: 39524

    Change-Id: Ia1fe0f2baafb78c974551100f16e6a7d99882f15
    Signed-off-by: Sharath Kumar K <email address hidden>

    De-branding in starlingx/config: CGCS -> StarlingX

    1. Rename CGCS to StarlingX for .spec file
    2. Rename TIS to StarlingX for .service files

    Test:
    After the de-brand change, bootimage.iso has been built in the flock
    Layer and installed on the dev machine to validate the changes.

    Please note, doing de-brand changes in batches, this is batch10 changes.

    Story: 2006387
    Task: 36202

    Change-Id: I404ce0da2621495175ad31489e9ad6f7b0211e26
    Signed-off-by: Sharath Kumar K <email address hidden>

commit d141e954fa6bbf688929ec90d1b6604a97792c43
Author: Teresa Ho <email address hidden>
Date: Tue Mar 31 10:08:57 2020 -0400

    Sysinv extensions for FPGA support

    This update adds cli and restapi to support FPGA device
    programming.

    CLI commands:
    system device-image-apply
    system device-image-create
    system device-image-delete
    system device-image-list
    system device-image-remove
    system device-image-show
    system device-image-state-list
    system device-label-list
    system host-device-image-update
    system host-device-image-update-abort
    system host-device-label-assign
    system host-device-label-list
    system host-device-label-remove

    Story: 2006740
    Task: 39498

    Change-Id: I556c2e7a51b3931b5a66ab27b67f51e3a8aebd9f
    Signed-off-by: Teresa Ho <email address hidden>

commit 491cca42ed854d2cb3ee3646b93c56a4f45f563c
Author: Elena Taivan <email address hidden>
Date: Wed Apr 29 11:25:26 2020 +0000

    Qcow2 conversion to raw can be done using 'image-conversion' filesystem

    1. Conversion filesystem can be added before/after
       stx-openstack is applied
    2. If conversion filesystem is added after stx-openstack
       is applied, changes to stx-openstack will only take effec...

Revision history for this message
Peng Peng (ppeng) wrote :

Verified on
Lab: WCP_122
Load: 2020-06-03_20-00-00

tags: removed: stx.retestneeded
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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