Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAfullNetPartition_master_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0">

commit ce95eb75a3ce94c2daa9c4e6cf52b3c6bd4aad5c 9e989fbc1c2a669c698bdea4803c6eb04607ebee (HEAD, origin/master, origin/HEAD, master)
Author: souvikdas95 Carmelo Cascone [souvikdas95@yahoocarmelo@opennetworking.co.inorg]
AuthorDate: Fri Mon Sep 18 1628 19:1931:06 47 2020 -05000700
Commit: Charles Chan Carmelo Cascone [charles@opennetworkingcarmelo@opennetworking.org]
CommitDate: Wed Tue Sep 23 1829 05:0409:46 23 2020 +0000
Reactive Forwarding: Inherit Treatment Builder from PacketContext
Publish more grpc artifacts
--
(cherry picked from commit f358cd918e415e9bb355f3040f54ea8fea494325)

Case 1: Constructing test variables and building ONOS package - PASS

...

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch from each controller - No Result
• 5.3 Read device roles from ONOS - PASS
• 5.4 Check for consistency in roles from each controller - PASS
• 5.5 Get the intents from each controller - PASS
• 5.6 Check for consistency in Intents from each controller - PASS
• 5.7 Get the flows from each controller - PASS
• 5.8 Check for consistency in Flows from each controller - PASS
• 5.9 Get the OF Table entries - No Result
• 5.10 Start continuous pings - No Result
• 5.11 Collecting topology information from ONOS - No Result
• 5.12 Host view is consistent across ONOS nodes - PASS
• 5.13 Each host has an IP address - PASS
• 5.14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - PASS
• 5.16 Comparing ONOS topology to MN - PASS
• 5.17 Device information is correct - PASS
• 5.18 Links are correct - PASS
• 5.19 Hosts are correct - PASS

Case 14: Start Leadership Election app -

...

PASS

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS
• 14.3 Active node was elected leader? - FAIL
Incorrect leader
• PASS

Case 15: Check that Leadership Election is still functional - PASS

...

• 17.1 Increment then get a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.2 Get then Increment a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.3 Counters we added have the correct values - FAIL
Added counters are incorrect
• PASS
• 17.4 Add -8 to then get a default counter on each node - FAIL
Error incrementing default counter
• PASS
• 17.5 Add 5 to then get a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.6 Get then add 5 to a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.7 Counters we added have the correct values - FAIL
Added counters are incorrect
• PASS
• 17.8 Distributed Set get - FAIL
• Set elements are incorrect
• PASS
• 17 17.9 Distributed Set size - FAIL
• Set sizes are incorrect
• PASS
• 17.10 Distributed Set add() - FAIL
• Set add was incorrect
• PASS
• 17.11 Distributed Set addAll() - FAIL
Set addAll was incorrect
• PASS
• 17.12 Distributed Set contains() - FAIL
Set contains failed
• PASS
• 17.13 Distributed Set containsAll() - PASS
• 17.14 Distributed Set remove() - FAIL
• Set remove was incorrect
• PASS
• 17.15 Distributed Set removeAll() - FAIL
• Set removeAll was incorrect
• PASS
• 17.16 Distributed Set addAll() - FAIL
Set addAll was incorrect
• PASS
• 17.17 Distributed Set clear() - FAIL
• Set clear was incorrect
• PASS
• 17. 17.18 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• PASS
• 17.19 Distributed Set retain() - FAIL
• Set retain was incorrect
• 17.20 Partitioned Transactional maps put - FAIL
• Partitioned Transactional Map put values are incorrect
• PASS
• 17.21 Partitioned Transactional maps get - FAIL
Partitioned Transactional Map values incorrect
• PASS
• 17.22 Get the value of a new value - FAIL
• Error getting atomic Value None, found: ['null', 'null', 'null', None, None]
• PASS
• 17.23 Atomic Value set() - FAIL
• Error setting atomic Value[1, 1, 1, -1, -1]
• PASS
• 17. 17.24 Get the value after set() - FAIL
Error getting atomic Value foo, found: ['foo', 'foo', 'foo', None, None]
• PASS
• 17.25 Atomic Value compareAndSet() - PASS
• 17.26 Get the value after compareAndSet() - FAIL
• Error getting atomic Value bar, found: ['bar', 'bar', 'bar', None, None]
• 17.27 Atomic Value getAndSet() - PASS
• PASS
• 17.27 Atomic Value getAndSet() - PASS
• 17. 17.28 Get the value after getAndSet() - FAIL
Error getting atomic Value: expected baz, found: ['baz', 'baz', 'baz', None, None]
• PASS
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - FAIL
• Error getting atomic Value None, found: ['null', 'null', 'null', None, None]
• 17.31 Work Queue add() - FAIL
• Error adding to Work Queue
• PASS
• 17.31 Work Queue add() - PASS
• 17.32 Check the work queue stats - PASS
• 17.33 Work Queue addMultiple() - PASS
• 17.34 17.32 Check the work queue stats - No Result

Case 61: Partition ONOS nodes into two distinct partitions - PASS

• PASS
• 17.35 Work Queue takeAndComplete() 1 - PASS
• 17.36 Check the work queue stats
• 61.1 Checking ONOS Logs for errors - No Result
• 61.2 Partitioning ONOS nodes - PASS
• 61.3 Sleeping 60 seconds - No Result

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

• 17.37 Work Queue takeAndComplete() 2 - PASS
• 17.38 Check the work queue stats - PASS
• 17.39 Work Queue destroy() 8.1 Comparing ONOS topology to MN topology - PASS
• 17.40 Check the work queue stats - PASS

Case 61: Partition ONOS nodes into two distinct partitions - PASS

• 61.1 Checking ONOS Logs for errors - No Result
• 61.2 Partitioning ONOS nodes - PASS
• 61.3 Sleeping 60 seconds - No Result

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC 2 Hosts view is consistent across all ONOS nodes - PASS
• 8.7 Device 3 Hosts information is correct - PASS
• 8.8 Links are correct 4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links 9 Hosts are correct - PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 7: Running ONOS Constant State Tests -

...

PASS

• 7.1 Check that each switch has a master - PASS
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS
• 7.4 Get the intents from each controller - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 Compare current intents with intents before the failure - PASS
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• PASS
• 7.8 Leadership Election is still functional - FAIL
• Something went wrong with Leadership election
• PASS

Case 4: Verify connectivity by sending traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - PASS
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• PASS
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• PASS

Case 15: Check that Leadership Election is still functional -

...

PASS

• 15.1 Run for election on each node - FAIL
• At least one node failed to run for leadership
• Skipping the rest of this case.
• PASS
• 15.2 Check that each node shows the same leader and candidates - PASS
• 15.3 Find current leader and withdraw - PASS
• 15.4 Check that a new node was elected leader - PASS
• 15.5 Check that that new leader was the candidate of old leader - PASS
• 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.7 Check that oldLeader is a candidate, and leader if only 1 node - No Result

Case 17: Check for Case 17: Check for basic functionality with distributed primitives - FAIL

...

• 17.1 Increment then get a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.2 Get then Increment a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.3 Counters we added have the correct values - FAIL
Added counters are incorrect
• PASS
• 17.4 Add -8 to then get a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.5 Add 5 to then get a default counter on each node - FAIL
Error incrementing
• default counter on each node - PASS
• 17.6 Get then add 5 to a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.7 Counters we added have the correct values - FAIL
• Added counters are incorrect
• PASS
• 17.8 Distributed Set get - FAIL
• Set elements are incorrect
• 17.9 Distributed Set size - FAIL
• Set sizes are incorrect
• 17.10 Distributed Set add() - FAIL
• Set add was incorrect
• PASS
• 17.11 Distributed Set addAll() - FAIL
Set addAll was incorrect
• PASS
• 17.12 Distributed Set contains() - FAIL
• Set contains failed
• PASS
• 17.13 Distributed Set containsAll() - PASS
• 17.14 Distributed Set remove() - FAIL
• Set remove was incorrect
• PASS
• 17.15 Distributed Set removeAll() - FAIL
Set removeAll was incorrect
• PASS
• 17.16 Distributed Set addAll() - FAIL
Set addAll was incorrect
• PASS
• 17.17 Distributed Set clear() - FAIL
• Set clear was incorrect
• PASS
• 17.18 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• PASS
• 17.19 Distributed Set retain() - FAIL
• Set retain was incorrect
• 17.20 Partitioned Transactional maps put Partitioned Transactional maps put - PASS
• 17.21 Partitioned Transactional maps get - PASS
• 17.22 Get the value of a new value - PASS
• 17.23 Atomic Value set() - PASS
• 17.24 Get the value after set() - PASS
• 17.21 Partitioned Transactional maps get - FAIL
• Partitioned Transactional Map values incorrect
• 17.22 Get the value of a new value - FAIL
• Error getting atomic Value None, found: ['null', 'null', None]
• 17.23 Atomic Value set() - FAIL
• Error setting atomic Value[1, 1, -1]
• 17.24 Get the value after set() - FAIL
• Error getting atomic Value foo, found: ['foo', 'foo', None]
• 17.25 Atomic Value compareAndSet() - FAIL
• Error setting atomic Value:-1
• 17.26 Get the value after compareAndSet() - FAIL
• Error getting atomic Value bar, found: ['foo', 'foo', None]
• 17.27 Atomic Value getAndSet() - FAIL
• Error with GetAndSet atomic Value: expected bar, found: foo
• 17.28 Get the value after getAndSet() - FAIL
• Error getting atomic Value: expected baz, found: ['baz', 'baz', None]
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - FAIL
• Error getting atomic Value None, found: ['null', 'null', None]
• 17.31 Work Queue add() - FAIL
• Error adding to Work Queue
• 25 Atomic Value compareAndSet() - PASS
• 17.26 Get the value after compareAndSet() - PASS
• 17.27 Atomic Value getAndSet() - PASS
• 17.28 Get the value after getAndSet() - PASS
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - PASS
• 17.31 Work Queue add() - PASS
• 17.32 Check the work queue stats - PASS
• 17.33 Work Queue addMultiple() - PASS
• 17.34 Check the work queue stats - PASS
• 17.35 Work Queue takeAndComplete() 1 - PASS
• 17.36 Check the work queue stats - PASS
• 17.37 Work Queue takeAndComplete() 2 - PASS
• 17.38 Check the work queue stats - PASS
• 17.39 Work Queue destroy() - PASS
• 17.40 Check the work queue stats - PASS 17.32 Check the work queue stats - No Result

Case 62: Healing Partition - PASS

...

• 62.1 Deleteing firewall rules - PASS
• 62.2 Checking ONOS nodes - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - PASS FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 10 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 7: Running ONOS Constant State Tests - FAIL

• 7.1 Check that each switch has a master - PASS
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS FAIL
• ONOS nodes have different views of switch roles
• 7.4 Get the intents from each controller - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 Compare current intents with intents before the failure - PASS the failure - FAIL
• The Intents changed during failure
• 7.7 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.8 Leadership Election is still functional - FAIL
• Something went wrong with Leadership election
• PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - PASS

• 15.1 Run for election on each node - PASS
• 15.2 Check that each node shows the same leader and candidates - PASS
• 15.3 Find current leader and withdraw - PASS
• 15.4 Check that a new node was elected leader - PASS
• 15.5 Check that that new leader was the candidate of old leader - PASS
• 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.7 Check that oldLeader is a candidate, and leader if only 1 node - No Result

...

• 17.1 Increment then get a default counter on each node - FAIL
Error incrementing default counter
• PASS
• 17.2 Get then Increment a default counter on each node - FAIL
Error incrementing default counter
• PASS
• 17.3 Counters we added have the correct values - FAIL
• Added counters are incorrect
• PASS
• 17.4 Add -8 to then get a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.5 Add 5 to then get a default counter on each node - FAIL
Error incrementing
• default counter on each node - PASS
• 17.6 Get then add 5 to a default counter on each node - FAIL
• Error incrementing default counter
• PASS
• 17.7 Counters we added have the correct values - FAIL
• Added counters are incorrect
• PASS
• 17.8 Distributed Set get - FAIL
• Set elements are incorrect
• 17.9 Distributed Set size - FAIL
• Set sizes are incorrect
• 17.10 Distributed Set add() - FAIL
• Set add was incorrect
• PASS
• 17.11 Distributed Set addAll() - FAIL
Set addAll was incorrect
• PASS
• 17.12 Distributed Set contains() - FAIL
• Set contains failed
• PASS
• 17.13 Distributed Set containsAll() - PASS
• 17.14 Distributed Set remove() - FAIL
• Set remove was incorrect
• PASS
• 17.15 Distributed Set removeAll() - FAIL
Set removeAll was incorrect
• PASS
• 17.16 Distributed Set addAll() - FAIL
Set addAll was incorrect
• PASS
• 17.17 Distributed Set clear() - FAIL
• Set clear was incorrect
• PASS
• 17.18 Distributed Set addAll() - FAIL
• Set addAll was incorrect
• PASS
• 17.19 Distributed Set retain() - FAIL
• Set retain was incorrect
• 17.20 Partitioned Transactional maps put - PASS
• 17.21 Partitioned Transactional maps get - FAIL
• Partitioned Transactional Map values incorrect
• 17.22 Get the value of a new value - FAIL
• Error getting atomic Value None, found: ['null', 'null', 'null', None, None]
• 17.23 Atomic Value set() - FAIL
• Error setting atomic Value[1, 1, 1, -1, -1]
• 17.24 Get the value after set() - FAIL
• Error getting atomic Value foo, found: ['foo', 'foo', 'foo', None, None]
• 17.25 Atomic Value compareAndSet() - FAIL
• Error setting atomic Value:-1
• 17.26 Get the value after compareAndSet() - FAIL
• Error getting atomic Value bar, found: ['foo', 'foo', 'foo', None, None]
• 17.27 Atomic Value getAndSet() - FAIL
• Error with GetAndSet atomic Value: expected bar, found: None
• 17.28 Get the value after getAndSet() - FAIL
• Error getting atomic Value: expected baz, found: ['foo', 'foo', 'foo', None, None]
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - FAIL
• Error getting atomic Value None, found: ['null', 'null', 'null', None, None]
• - PASS
• 17.22 Get the value of a new value - PASS
• 17.23 Atomic Value set() - PASS
• 17.24 Get the value after set() - PASS
• 17.25 Atomic Value compareAndSet() - PASS
• 17.26 Get the value after compareAndSet() - PASS
• 17.27 Atomic Value getAndSet() - PASS
• 17.28 Get the value after getAndSet() - PASS
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - PASS
• 17.31 Work Queue add() - PASS
• 17.32 Check the work queue stats - PASS
• 17.33 Work Queue addMultiple() - PASS
• 17.34 Check the work queue stats - PASS
• 17.35 Work Queue takeAndComplete() 1 - PASS
• 17.36 Check the work queue stats - PASS
• 17.37 Work Queue takeAndComplete() 2 - PASS
• 17.38 Check the work queue stats - PASS
• 17.39 Work Queue destroy 17.31 Work Queue add() - PASS
• 17.32 40 Check the work queue stats - No Result PASS

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

...

• 9.1 Kill Link between s28 and s3 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - PASS FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 13 SCCs
• 8.7 Device information is correct - PASS
• 8.8 8 Links are correct - FAIL
• Links are
correct - PASS
• incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...

• 10.1 Bring link between s28 and s3 back up - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - PASS FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 13 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

Case 11: Killing a switch to ensure it is discovered correctly - PASS

• 11.1 Kill s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - PASS FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 14 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

Case 12: Adding a switch to ensure it is discovered correctly - PASS

• 12.1 Add back s5 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - PASS FAIL
• ONOS topology don't match Mininet
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 13 SCCs
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.2 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• 4.3 Check leadership of topics - PASS
• 4.4 Wait a minute then ping again - FAIL
• Intents have not been installed correctly, pings failed.

...