Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CN-919] Fix WanReplication CR overwrite batch-publishers #814

Merged
merged 2 commits into from Aug 1, 2023

Conversation

SeriyBg
Copy link
Contributor

@SeriyBg SeriyBg commented Jul 21, 2023

User Impact

Fix subsequent WanReplication CR overwrite previous batch-publishers

@SeriyBg SeriyBg added the bug Something isn't working label Jul 21, 2023
@SeriyBg SeriyBg added this to the 5.9 milestone Jul 21, 2023
@SeriyBg SeriyBg temporarily deployed to report July 21, 2023 16:07 — with GitHub Actions Inactive
@github-actions
Copy link

Test Results

Total Tests 🔴 Failures 🟠 Errors ⚪ Skipped
OS 93 0 0 45
EE 109 52 0 36
Failed Tests
OS
EE
  • Hazelcast Map Config should create Map Config with correct default values
  • Hazelcast Queue Config should create Queue Config with correct default values
  • Hazelcast CR with Persistence feature enabled Should successfully restore from ExternalBackup-PVC using GCP bucket restore from BucketConfig
  • Hazelcast Map Config should create Map Config with Indexes
  • Hazelcast User Code Deployment should use the MapStore implementation correctly using user code from remote url
  • Hazelcast CR with Persistence feature enabled Should successfully restore from ExternalBackup-PVC using Azure bucket HotBackupResourceName
  • Hazelcast JetJob should download JAR and execute JetJob using jar from remote url
  • Hazelcast Queue Config should create Queue Config
  • Hazelcast CR with Persistence feature enabled Should successfully restore from ExternalBackup-PVC using GCP bucket HotBackupResourceName
  • Hazelcast JetJob should download JAR and execute JetJob using jar from bucket
  • Hazelcast User Code Deployment should use the MapStore implementation correctly using user code from bucket
  • Hazelcast CR with Persistence feature enabled Should successfully restore from ExternalBackup-PVC using AWS S3 bucket HotBackupResourceName
  • Hazelcast CR with expose externally feature should create Hazelcast cluster exposed with NodePort services and allow connecting with Hazelcast smart client
  • Hazelcast CR with Persistence feature enabled should successfully restore from LocalBackup-PVC-HotBackupResourceName
  • Hazelcast WAN should start WanReplication for the maps created after the Wan CR
  • Hazelcast Map Config should create Map Config
  • Hazelcast CR with Persistence feature enabled should trigger corresponding action when startupActionSpecified ForceStart
  • Hazelcast WAN should set WanReplication CR status to Success when resource map is created after the wan
  • Hazelcast CR with Persistence feature enabled should trigger corresponding action when startupActionSpecified PartialStart
  • Hazelcast Cache Config should create Cache Config with correct default values
  • Hazelcast JetJob should change JetJob status
  • Hazelcast Map Config with Persistence should fail when persistence of Map CR and Hazelcast CR do not match
  • Hazelcast MultiMap Config should create MultiMap Config with correct default values
  • Hazelcast Hazelcast cluster name should create a Hazelcast cluster with Cluster name: development
  • Hazelcast Map Config when Native Memory is not enabled for Hazelcast CR should fail with InMemoryFormat value is set to NativeMemory in near cache configuration
  • Hazelcast Cache Config when Native Memory is not enabled for Hazelcast CR should fail with InMemoryFormat value is set to NativeMemory
  • Hazelcast Map Config when Native Memory is not enabled for Hazelcast CR should fail with InMemoryFormat value is set to NativeMemory
  • Hazelcast Map Config with Persistence should persist Map Config with Indexes
  • Hazelcast MultiMap Config should create MultiMap Config
  • Hazelcast Hazelcast CR TLS configuration when TLS property is configured should form a cluster and be able to connect
  • Hazelcast CR with expose externally feature should create Hazelcast cluster and allow connecting with Hazelcast unisocket client
  • Hazelcast Cache Config with Persistence should fail when persistence of Cache CR and Hazelcast CR do not match
  • Hazelcast Hazelcast CR TLS configuration when TLS with Mutual Authentication property is configured should form a cluster and be able to connect
  • Hazelcast JetJobSnapshot should export a snapshot canceling the job
  • Hazelcast Cache Config with Persistence should keep the entries after a Hot Backup
  • Hazelcast Cache Config should create Cache Config
  • Hazelcast Topic Config should create Topic Config with correct default values
  • Hazelcast WAN should delete the map from status and WAN status should be failed
  • Hazelcast JetJob should execute JetJob successfully using jar from remote url
  • Hazelcast Topic Config should create Topic Config
  • Hazelcast WAN should continue replication if one reference is deleted
  • Hazelcast JetJob should execute JetJob successfully using jar from bucket
  • Hazelcast User Code Deployment should add executor services both initially and dynamically
  • Hazelcast JetJob should fail the job if Hz cluster is failing
  • Hazelcast Map Config should update the map correctly
  • Hazelcast WAN should send data using WanReplication configuration in Config
  • Hazelcast Topic Config should fail to update Topic Config
  • Hazelcast WAN should replicate maps to target cluster including maps with names different from map CR name
  • Hazelcast Map Config with Persistence should persist the map successfully created configs into the config
  • Hazelcast JetJobSnapshot should set status to 'failed' if exporting snapshot from non-running job
  • Hazelcast MultiMap Config should fail to update MultiMap Config
  • Hazelcast User Code Deployment should add entry listeners
  • @SeriyBg SeriyBg changed the title [CN-919] Fix WanReplication CR overwrite batch-pubblishers [CN-919] Fix WanReplication CR overwrite batch-publishers Jul 24, 2023
    @SeriyBg SeriyBg temporarily deployed to report July 24, 2023 08:43 — with GitHub Actions Inactive
    @github-actions
    Copy link

    Test Results

    Total Tests 🔴 Failures 🟠 Errors ⚪ Skipped
    OS 93 0 0 45
    EE 109 54 0 34
    Failed Tests
    OS
    EE
  • Hazelcast Map Config with Persistence should keep the entries after a Hot Backup
  • Hazelcast JetJob should download JAR and execute JetJob using jar from remote url
  • Hazelcast WAN should send data to another cluster
  • Hazelcast WAN should stop replicating to target cluster
  • Hazelcast Queue Config should create Queue Config
  • Hazelcast JetJob should download JAR and execute JetJob using jar from bucket
  • Hazelcast Topic Config should create Topic Config with correct default values
  • Hazelcast Map Config with Persistence should continue persisting last applied Map Config in case of failure
  • Hazelcast Map Config should create Map Config with Indexes
  • Hazelcast Cache Config with Persistence should keep the entries after a Hot Backup
  • Hazelcast Queue Config should create Queue Config with correct default values
  • Hazelcast Map Config should create Map Config with correct default values
  • Hazelcast ReplicatedMap Config should create ReplicatedMap Config with correct default values
  • Hazelcast CR with Persistence feature enabled should trigger corresponding action when startupActionSpecified ForceStart
  • Hazelcast Queue Config should fail to update Queue Config
  • Hazelcast Hazelcast CR dependent CRs when Hazelcast CR is deleted dependent Data Structures and HotBackup CRs should be deleted
  • Hazelcast CR with Persistence feature enabled should successfully restore from LocalBackup-PVC-HotBackupResourceName
  • Hazelcast Map Config with Persistence should fail when persistence of Map CR and Hazelcast CR do not match
  • Hazelcast Cache Config should create Cache Config with correct default values
  • Hazelcast Map Config should create Map Config
  • Hazelcast Cache Config with Persistence should persist the cache successfully created configs into the config
  • Hazelcast CR with Persistence feature enabled should trigger corresponding action when startupActionSpecified PartialStart
  • Hazelcast Hazelcast member status should update HZ ready members status
  • Hazelcast MultiMap Config should create MultiMap Config
  • Hazelcast Map Config when Native Memory is not enabled for Hazelcast CR should fail with InMemoryFormat value is set to NativeMemory
  • Hazelcast Map Config with Persistence should persist Map Config with Indexes
  • Hazelcast MultiMap Config should create MultiMap Config with correct default values
  • Hazelcast JetJobSnapshot should export a snapshot canceling the job
  • Hazelcast CR with Persistence feature enabled should start HotBackup after cluster is ready
  • Hazelcast Hazelcast CR TLS configuration when TLS with Mutual Authentication property is configured should form a cluster and be able to connect
  • Hazelcast CR with expose externally feature should create Hazelcast cluster and allow connecting with Hazelcast unisocket client
  • Hazelcast JetJob should persist jobs when lossless restart is enabled
  • Hazelcast Cache Config with Persistence should fail when persistence of Cache CR and Hazelcast CR do not match
  • Hazelcast Cache Config when Native Memory is not enabled for Hazelcast CR should fail with InMemoryFormat value is set to NativeMemory
  • Hazelcast Map Config when Native Memory is not enabled for Hazelcast CR should fail with InMemoryFormat value is set to NativeMemory in near cache configuration
  • Hazelcast Hazelcast cluster name should create a Hazelcast cluster with Cluster name: development
  • Hazelcast JetJobSnapshot should export snapshot and initialize new job from that snapshot
  • Hazelcast WAN should delete the map from status and WAN status should be failed
  • Hazelcast JetJob should execute JetJob successfully using jar from remote url
  • Hazelcast WAN should continue replication if one reference is deleted
  • Hazelcast User Code Deployment should add executor services both initially and dynamically
  • Hazelcast CR with Persistence feature enabled should successfully trigger HotBackup
  • Hazelcast JetJob should execute JetJob successfully using jar from bucket
  • Hazelcast Topic Config should create Topic Config
  • Hazelcast WAN should send data using WanReplication configuration in Config
  • Hazelcast WAN should replicate maps to target cluster including maps with names different from map CR name
  • Hazelcast MultiMap Config should fail to update MultiMap Config
  • Hazelcast JetJob should fail the job if Hz cluster is failing
  • Hazelcast JetJobSnapshot should set status to 'failed' if exporting snapshot from non-running job
  • Hazelcast Hazelcast CR TLS configuration when TLS property is configured should form a cluster and be able to connect
  • Hazelcast User Code Deployment should add entry listeners
  • Hazelcast Map Config with Persistence should persist the map successfully created configs into the config
  • Hazelcast Map Config should update the map correctly
  • Hazelcast Topic Config should fail to update Topic Config
  • @SeriyBg SeriyBg temporarily deployed to report July 24, 2023 10:34 — with GitHub Actions Inactive
    @SeriyBg SeriyBg marked this pull request as ready for review July 24, 2023 10:40
    @SeriyBg SeriyBg requested a review from a team as a code owner July 24, 2023 10:40
    @SeriyBg SeriyBg requested review from cagric0 and semihbkgr and removed request for a team July 24, 2023 10:40
    @SeriyBg SeriyBg added fix This type is used to identify changes related to backward-compatible bug fixes and removed bug Something isn't working labels Jul 25, 2023
    @SeriyBg SeriyBg merged commit c574dd7 into main Aug 1, 2023
    42 checks passed
    @SeriyBg SeriyBg deleted the CN-919-wan-publisher branch August 1, 2023 07:12
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    fix This type is used to identify changes related to backward-compatible bug fixes
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    None yet

    3 participants