Some strange things about HA

I am setting up a new Active-/Passive XG cluster. I did some testings and the results seem a bit strange to me.

1. HA was completely up and running.
2. I deactivated HA from the auxiliary/passive device (should that be possible at all?), then this device in HA status went to"Faulty" on the primary/active device.
3. I deactivated HA on the primary/active device, too.

So at this point I had 2 standalone appliances again.

1. I reactivated HA on the auxiliary device and initiated the HA on the primary device again.
2. After a few minutes the cluster was up and running again.

I received several mails from the auxiliary device, that user "hauser" used wrong credentials to login via SSH.
I know/understand WHO he is, but I don't understand why he is using wrong credentials.
I used the same passphrase for HA creation that I used in my first attempt.

The second thing is about pattern updates. I only updated all pattern updates on the primary device. Logging into the auxiliary's WebAdmin I saw this:

I was not allowed to "Install" the pattern updates (which made no sense at all, since it was the same version, already installed). That was the reason why I deactivated HA after it was built. Being a "Standalone" the pattern update Install buttons worked again.

So my questions:

1. is "hauser's activity" in using wrong credentials normal? First I only re-enabled HA from the auxiliary again to see if they would reunite. Maybe the mails came from that time.
   
   
2. Is there any official way to get rid of the "already installed updates" ready to install on the auxiliary?
   
   
3. When will Sophos fix the name issues to make things a bit transparent?

• In dashboard overview they are still called master (A-P (M)) and slave (A-P (S)), maybe with much interpretation will "master" and "standby".
• In cluster creation and mode they are called by funcionality, "active" and "passive".
• In cluster status they are called "primary" and "auxiliary".