Skip to content
Snippets Groups Projects
  1. Oct 28, 2024
    • Roman Krček's avatar
      Rewrite kolla-ansible CLI to python · 9ea63dc3
      Roman Krček authored
      
      Moving the CLI to python allows for easier
      maintenance and larger feature-set.
      
      This patch introduces a few breaking changes!
      The changes stem the nature of the cliff package.
      - the order of parameters must be
        kolla-ansible <action> <arguments>
      - mariadb_backup and mariadb_recovery now are
        mariadb-backup and mariadb-recovery
      
      Closes-bug: #1589020
      Signed-off-by: default avatarRoman Krček <roman.krcek@tietoevry.com>
      Change-Id: I9749b320d4f5eeec601a055b597dfa7d8fb97ce2
      9ea63dc3
  2. Oct 26, 2024
  3. Oct 25, 2024
  4. Oct 24, 2024
    • Michal Nasiadka's avatar
      CI: Add ProxySQL exception to check-logs.sh · 49cebeaf
      Michal Nasiadka authored
      After switching to ProxySQL as default we see following logs:
      CRITICAL neutron [None req-c214fdae-5da7-402d-92b0-0572c278a5b5 - - - - - -] Unhandled error: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (9001, 'Max connect timeout reached while reaching hostgroup 0 after 10150ms')
      
      Mainly in upgrade jobs, which otherwise pass successfuly - just fail on this
      check.
      
      Change-Id: I4336ec62a0a2dfbe815842f1bacb02135bcf4c0e
      49cebeaf
  5. Oct 22, 2024
  6. Oct 18, 2024
  7. Oct 17, 2024
    • Michal Arbet's avatar
      Fix mariadb backup unable to create history table · e3ce0711
      Michal Arbet authored
      The backup user was missing the necessary CREATE
      privilege for the mariadb_backup_history table
      within the mysql schema, causing backups to fail
      when attempting to create this table.
      
      This patch addresses the issue by granting the backup
      user the required CREATE permission specifically for
      the mariadb_backup_history table. With this change,
      the backup process can now complete successfully
      without manual intervention for user permissions.
      
      Closes-Bug: #2061889
      Change-Id: Ic92c8959972329adbd4b89c521aa87678f25b4e4
      e3ce0711
    • jayjahns's avatar
      Change from PERCONA_SCHEMA to mysql for mariabackup · 7aea1d3e
      jayjahns authored
      In 2023.1, mariadb was at version 10.6, which meant that
      the PERCONA_SCHEMA.xtrabackup_history table was used to
      log historicals for backups.
      
      Starting in 2023.2 onwards, mariadb is at version 10.11, and the
      default table used is now mysql.mariadb_backup_history.
      
      Because the mysql database already exists, there is no reason
      to try and create it. Instead, we just need to update the defaults
      and ensure the permissions get added to the correct database.
      
      Related-Bug: #2061889
      Change-Id: If146d8f896c70374884807d42ca0e12df3276d48
      7aea1d3e
    • Michal Arbet's avatar
      Switch mariadb's loadbalancer from HAProxy to ProxySQL · 8f0a4bcb
      Michal Arbet authored
      It's been some time since ProxySQL has been
      with us in Kolla. Let's switch the load balancer
      for MariaDB connections from HAProxy to ProxySQL.
      
      Depends-On: https://review.opendev.org/c/openstack/kolla/+/928956
      Change-Id: I42ba4fb83b5bb31058e888f0d39d47c27b844de5
      8f0a4bcb
    • Michal Arbet's avatar
      Adjust ProxySQL shunning behavior for single-node clusters · dafac823
      Michal Arbet authored
      In single-node clusters, ProxySQL shuns the server on MySQL
      errors, causing failures during upgrades or container restarts.
      This change increases the timeout to 10 seconds, allowing
      the backend time to recover and preventing immediate errors
      in CI environments.
      
      Change-Id: I70becdc3fcb4ca8f7ae31d26097d95bdc6dd67eb
      dafac823
  8. Oct 16, 2024
  9. Oct 15, 2024
  10. Oct 14, 2024
  11. Oct 09, 2024
  12. Oct 08, 2024
    • Michal Nasiadka's avatar
      ovn: Fix FQDN-based deployments · 35e59efa
      Michal Nasiadka authored
      Since [1] Neutron puts requested-chassis entry with a name taken
      from the agent, which results in FQDN-based name on FQDN-based
      deployments. It does not match what we set in hostname in OVS.
      
      [1]: I4e3c001dd3bb37b86fda8b9495a3c5178c3e736d
      
      Closes-Bug: #2080552
      Change-Id: I3ae03aa2e09bc445f0f5a95a43bf210f06685cc1
      35e59efa
  13. Oct 07, 2024
  14. Oct 04, 2024
Loading