Skip to end of metadata
Go to start of metadata
Test CaseDescriptionStatusOwnerDateJIRA linkComment
Forced failover from standby site in healthy systemVerify that the site operator is able to force the standby site to become active from the standby site when both sites are in a healthy state from any sitePASS

SDNC-213 - Getting issue details... STATUS


Forced failover from active site in healthy systemVerify that the site operator is able to force the standby site to become active from the active site when both sites are in a healthy state from any sitePASS
SDNC-213 - Getting issue details... STATUS

Forced failover from standby site in healthy systemVerify that the site operator is able to force the standby site to become active from the standby site when both sites are in a healthy state from any sitePASS
SDNC-213 - Getting issue details... STATUS

Forced failover from active site in healthy systemVerify that the site operator is able to force the standby site to become active from the active site when both sites are in a healthy state from any sitePASS

SDNC-213 - Getting issue details... STATUS


Site failover invoked by total ODL outageVerify that the sdnc.failover script can successfully be used to make a standby site active when the ODLs in the active site are no longer available.PASS
SDNC-213 - Getting issue details... STATUS

Site recovery after total ODL outageVerify that a documented process can be followed to recover an SDN-C site that failed due to a total loss of ODL instances. The procedure should restore the site so that it is available to become the active site.PASS

SDNC-213 - Getting issue details... STATUS


Site failover invoked by simple failureVerify that the enhancements in sdnc.failover do not affect the ability to failover in non-catastrophic conditions.PASS
SDNC-213 - Getting issue details... STATUS

Site failover invoked by total ODL outageVerify that the sdnc.failover script can successfully be used to make a standby site active when the ODLs in the active site are no longer available.PASS

SDNC-213 - Getting issue details... STATUS


Force failover from standby site without network segmentation
PASS

SDNC-213 - Getting issue details... STATUS


Forced failover from standby site during network segmentationVerify that the site operator is able to force the standby site to become active from the standby site when the network connection to the remote site has failed.PASS

SDNC-213 - Getting issue details... STATUS


DMaaP message for PROM-initiated failoverVerify that the SDN-C site delivers a DMaaP-based message when a successful automatic site switch from one site to the other has taken place.PASS

SDNC-281 - Getting issue details... STATUS


DMaaP message for healthy to unhealthy transition on active siteVerify that the SDN-C site delivers a DMaaP-based message when the active site transitions from healthy to unhealthy.PASS

SDNC-281 - Getting issue details... STATUS


DMaaP message for healthy to unhealthy transition on standby siteVerify that the SDN-C site delivers a DMaaP-based message when the standby site transitions from healthy to unhealthy.PASS
SDNC-281 - Getting issue details... STATUS

DMaaP message for unhealthy to healthy transition on standby siteVerify that the SDN-C site delivers a DMaaP-based message when the standby site transitions from unhealthy to healthy.PASS

SDNC-281 - Getting issue details... STATUS


DMaaP message for operator-initiated failoverVerify that the SDN-C site delivers a DMaaP-based message when a successful operator-initiated switch from one site to the other has taken place.PASS

SDNC-281 - Getting issue details... STATUS


DMaaP message for unsuccessful PROM-initiated failoverVerify that the SDN-C site delivers a DMaaP-based message when an automatic site switch fails to be completed successfully. The message should be very clear that the failover did not complete successfully.PASS
SDNC-281 - Getting issue details... STATUS

DMaap Initial state messageVerify that the SDN-C site delivers an initial DMaaP-based message about the health checkPASS

SDNC-281 - Getting issue details... STATUS


DMaap subsequent health state messageVerify that the SDN-C site delivers an subsequent DMaaP-based message about the health checkPASS
SDNC-281 - Getting issue details... STATUS

DMaaP messaging documentation reviewVerify that the ONAP wiki documentation correctly describes the DMaaP messaging feature for SDN-C Geo.PASS

SDNC-281 - Getting issue details... STATUS


Auto-switch on unhealthy reportVerify that PROM is able to publish the local site's health to MUSIC and the remote site's PROM initiates site failover in the case where the site is found to be unhealthy.PASS

SDNC-213 - Getting issue details... STATUS


Auto-switch on PROM failureVerify that the remote site's PROM initiates a site failover when the local site's PROM is unable to publish health updates.PASS

SDNC-213 - Getting issue details... STATUS


Single failover activityVerify that delays in carrying out a site failover do not prevent PROM from running its enableSdncActive.sh script or from initiating multiple failover activities. The failover process should be called asynchronously.PASS
SDNC-213 - Getting issue details... STATUS

PROM starts in passive mode on standby siteVerify that PROM starting in passive mode on standby sitePASS

SDNC-213 - Getting issue details... STATUS


No component outagesVerify that when all components in the site are available, the site is reported as being healthy.PASS

SDNC-282 - Getting issue details... STATUS


Single ODL outageVerify that a single ODL outage does not result in the site being unhealthy.PASS

SDNC-282 - Getting issue details... STATUS


Double ODL outageVerify that a double ODL outage results in the site being unhealthy.PASS

SDNC-282 - Getting issue details... STATUS


Triple ODL outageVerify that a triple ODL outage results in the site being unhealthy.PASS

SDNC-282 - Getting issue details... STATUS


Single Admin Portal outageVerify that an outage of the Admin Portal results in the site being unhealthy.PASS

SDNC-282 - Getting issue details... STATUS


Exit code on successful execution of healthyVerify that when sdnc.monitor runs successfully and detects the site is healthy, the exit code returned is "0".PASS

SDNC-282 - Getting issue details... STATUS


Exit code on successful execution of unhealthyVerify that when sdnc.monitor runs successfully and detects the site is unhealthy, the exit code returned is "0".PASS

SDNC-282 - Getting issue details... STATUS


sdnc.dnsswitch updates CoreDNS settings for Site AVerify that the sdnc.dnsswitch script modifies the CoreDNS configuration so that the SDN-C domain points to the local site.PASS

SDNC-213 - Getting issue details... STATUS


sdnc.dnsswitch updates CoreDNS settings for Site BVerify that the sdnc.dnsswitch script modifies the CoreDNS configuration so that the SDN-C domain points to the local site.PASS

SDNC-213 - Getting issue details... STATUS


sdnc.dnsswitch run when site is already targetVerify that the dns.dnsswitch script is capable of being run on the local site when the CoreDNS configuration is already pointing to the local site.PASS
SDNC-213 - Getting issue details... STATUS

sdnc.dnsswitch returns "0" exit code on successVerify that the sdnc.dnsswitch script provides a "0" exit code when run successfully.PASS
SDNC-213 - Getting issue details... STATUS

sdnc.dnsswitch returns non-zero exit code on failureVerify that the sdnc.dnsswitch script provides a non-zero exit code when run unsuccessfully.PASS
SDNC-213 - Getting issue details... STATUS

sdnc.dnsswitch returns non-zero exit code on failure when core-dns is unavailable in config fileVerify that the sdnc.dnsswitch script provides a non-zero exit code when core-dns is unavailable in site.confPASS
SDNC-213 - Getting issue details... STATUS

sdnc.dnsswitch returns non-zero exit code on failure when app name is other than sdnc in config fileVerify that the sdnc.dnsswitch script provides a non-zero exit code when app name is other than sdnc in site.confPASS
SDNC-213 - Getting issue details... STATUS

sdnc.dnsswitch returns non-zero exit code on failure when core-dns host is invalidVerify that the sdnc.dnsswitch script provides a non-zero exit code when core-dns host is invalid in site.confPASS
SDNC-213 - Getting issue details... STATUS

sdnc.dnsswitch returns non-zero exit code on failure when appname or siteip are missingVerify that the sdnc.dnsswitch script provides a non-zero exit code when appname or siteip are missing from site.confPASS

SDNC-213 - Getting issue details... STATUS