It's unclear what the behavior of creating a Product CR should actually be.

We would expect that when you create a Product CR that it will only create the Product in 3scale and not Promote it to staging. Promotion should then be handled by the ProxyConfigPromote CR.

However we have observed the following different behaviors when creating a Product CR:

1. It only creates the Product in 3scale and does not promote it to staging
2. It creates the Product and promotes 2 versions to staging
3. It creates the Product, promotes 1 version to staging, and leaves some changes unpromoted.

It's clear that there is some race condition or some other bug but without knowing what the intended behavior is we can't really track down the root cause. It's also difficult to reproduce. I have observed the first two of the listed behaviors above in my environment and have observed the third in two different environments for a customer. 

The same inconsistent behavior can be observed when modifying the Product (i.e. changing a mapping rule). Again we would expect only the changes to be reflected in the 3scale Product, but it shouldn't actually deploy them until the ProxyConfigPromote CR is created.