commits  

Messages by Thread

• • Re: [PR] Support for custom SSH port for KVM hosts from the host url on add host and the configuration [cloudstack] via GitHub
• [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
  • Re: [PR] backport: PR 11914 fixing MS maintenance test [cloudstack] via GitHub
• [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
  • Re: [PR] Fix VPC restart with multi-CIDR networks: handle comma-separated CIDR… [cloudstack] via GitHub
• [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
  • Re: [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
  • Re: [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
  • Re: [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
  • Re: [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
  • Re: [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
  • Re: [I] VPC restart with cleanup fails when VPC has multiple public IP ranges from different VLANs — "cidr is not formatted correctly" [cloudstack] via GitHub
• [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] chore(cks): include new script to generate cks images with cilium as … [cloudstack] via GitHub
  • Re: [PR] [CKS] script to generate cks images with cilium as default CNI [cloudstack] via GitHub
  • Re: [PR] [CKS] script to generate cks images with cilium as default CNI [cloudstack] via GitHub
  • Re: [PR] [CKS] script to generate cks images with cilium as default CNI [cloudstack] via GitHub
  • Re: [PR] [CKS] script to generate cks images with cilium as default CNI [cloudstack] via GitHub
  • Re: [PR] [CKS] script to generate cks images with cilium as default CNI [cloudstack] via GitHub
  • Re: [PR] [CKS] script to generate cks images with cilium as default CNI [cloudstack] via GitHub
• (cloudstack) branch clvm-enhancements updated (5fc1f12965c -> 9e03f4bb48e) pearl11594
• (cloudstack) branch clone-edit-existing-offerings updated (6ea054cb01b -> 425d8c7e70e) pearl11594
• [PR] build(deps): bump axios from 0.21.4 to 1.13.5 in /ui [cloudstack] via GitHub
  • Re: [PR] build(deps): bump axios from 0.21.4 to 1.13.5 in /ui [cloudstack] via GitHub
  • Re: [PR] build(deps): bump axios from 0.21.4 to 1.13.5 in /ui [cloudstack] via GitHub
  • Re: [PR] build(deps): bump axios from 0.21.4 to 1.13.5 in /ui [cloudstack] via GitHub
  • Re: [PR] build(deps): bump axios from 0.21.4 to 1.13.5 in /ui [cloudstack] via GitHub
  • Re: [PR] build(deps): bump axios from 0.21.4 to 1.13.5 in /ui [cloudstack] via GitHub
• (cloudstack) branch clvm-enhancements updated (1eeeeea892a -> 5fc1f12965c) pearl11594
  • (cloudstack) 01/01: CLVM enhancements and fixes pearl11594
• [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
  • Re: [PR] CLVM enhancements and fixes [cloudstack] via GitHub
• (cloudstack) branch clvm-enhancements created (now 1eeeeea892a) pearl11594
  • (cloudstack) 01/01: CLVM enhancements and fixes pearl11594
• Re: [I] No validation done when user resets a password [cloudstack] via GitHub
  • Re: [I] No validation done when user resets a password [cloudstack] via GitHub
• [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
  • Re: [PR] Usage: Heartbeat should not schedule usage job when a job is already running [cloudstack] via GitHub
• (cloudstack) branch ghi11438-errorprone-fixes updated: address possible npe pearl11594
• [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
  • Re: [PR] [4.20] Fix account deletion blocked by deleted project admin mappings [cloudstack] via GitHub
• [PR] Fix account deletion blocked by deleted project admin mappings (4.20) [cloudstack] via GitHub
  • Re: [PR] Fix account deletion blocked by deleted project admin mappings (4.20) [cloudstack] via GitHub
• [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
  • Re: [PR] Add a Prometheus metric to track host certificate expiry [cloudstack] via GitHub
• (cloudstack) branch healthcheck-4.20 updated (b4d270ccdcb -> c6b92cc7de2) dahn
• (cloudstack) branch healthcheck-4.22 updated (eae4f21897f -> 6cbded257dc) dahn
• (cloudstack) branch main updated (408e8c079db -> d3e19769125) dahn
  • (cloudstack) 01/01: Merge release branch 4.22 to main dahn
• (cloudstack) branch healthcheck-main updated (5eafe8d7d6e -> 930ef5844ff) dahn
• (cloudstack) branch 4.22 updated (53c98c33e60 -> 7324ef45d46) dahn
  • (cloudstack) 01/01: Merge branch '4.20' into 4.22 dahn
• [I] AccountDaoImpl.findUserAccountByApiKey() generates random UUID instead of reading from database [cloudstack] via GitHub
  • Re: [I] AccountDaoImpl.findUserAccountByApiKey() generates random UUID instead of reading from database [cloudstack] via GitHub
  • Re: [I] AccountDaoImpl.findUserAccountByApiKey() generates random UUID instead of reading from database [cloudstack] via GitHub
  • Re: [I] AccountDaoImpl.findUserAccountByApiKey() generates random UUID instead of reading from database [cloudstack] via GitHub
  • Re: [I] AccountDaoImpl.findUserAccountByApiKey() generates random UUID instead of reading from database [cloudstack] via GitHub
  • Re: [I] AccountDaoImpl.findUserAccountByApiKey() generates random UUID instead of reading from database [cloudstack] via GitHub
• Re: [I] Capacity dashboard doesn't load if incorrect backup.framework.provider.plugin value is given [cloudstack] via GitHub
  • Re: [I] Capacity dashboard doesn't load if incorrect backup.framework.provider.plugin value is given [cloudstack] via GitHub
• (cloudstack) branch ghi12449-capDashboard-multipleBackupProv deleted (was 09c2399d2b3) dahn

• Earlier messages
• Later messages