Comment 3 for bug 2051915

Revision history for this message
Matt Verran (mv-2112) wrote (last edit ):

If this is in 2023.2/edge (390) then unfortunately I'm still seeing issues. Its definitely less, but still there.

NAME READY STATUS RESTARTS AGE
-----------------------8<--------------------8<-----------------------
horizon-0 2/2 Running 1 (81m ago) 117m
octavia-0 4/4 Running 1 (79m ago) 80m
keystone-mysql-0 2/2 Running 3 (27m ago) 118m
cinder-mysql-0 2/2 Running 3 (23m ago) 118m
neutron-mysql-0 2/2 Running 3 (17m ago) 118m
horizon-mysql-0 2/2 Running 5 (15m ago) 118m
placement-mysql-0 2/2 Running 4 (23m ago) 118m
magnum-mysql-0 2/2 Running 3 (12m ago) 89m
designate-mysql-0 2/2 Running 3 (11m ago) 86m
nova-mysql-0 2/2 Running 3 (7m10s ago) 118m
heat-mysql-0 2/2 Running 4 (6m11s ago) 98m
octavia-mysql-0 2/2 Running 3 (2m13s ago) 81m
barbican-mysql-0 2/2 Running 4 (70s ago) 93m
glance-mysql-0 1/2 Running 6 (11s ago) 118m

kubectl describe pod glance-mysql-0 -n openstack

  mysql:
    Container ID: containerd://360f8aa94fe905107622234457cb7f4a6b9dd738a960b047e4b86756fcfa49cd
    Image: registry.jujucharms.com/charm/62ptdfbrjpw3n9tcnswjpart30jauc6wc5wbi/mysql-image@sha256:b0d2e028aa86173918c319a0728a1124b6f025985bc6e9774f32d30bbfc96722
    Image ID: registry.jujucharms.com/charm/62ptdfbrjpw3n9tcnswjpart30jauc6wc5wbi/mysql-image@sha256:b0d2e028aa86173918c319a0728a1124b6f025985bc6e9774f32d30bbfc96722
    Port: <none>
    Host Port: <none>
    Command:
      /charm/bin/pebble
    Args:
      run
      --create-dirs
      --hold
      --http
      :38813
      --verbose
    State: Running
      Started: Mon, 12 Feb 2024 11:01:06 +0000
    Last State: Terminated
      Reason: Error
      Exit Code: 137
      Started: Mon, 12 Feb 2024 10:50:07 +0000
      Finished: Mon, 12 Feb 2024 11:01:06 +0000
    Ready: True