Does a transition rule create versioned objects?

Question

I have a versioned bucket with a transition rule to Deep Glacier. The original (at upload) storage class was Standard-IA and after some time (transition rule was applied) I found the transitioned objects as current version with storage class Deep Glacier (as intended) but additionally the originally uploaded objects (as previous version) with their original storage class (Standard-IA).  
What would cause that behaviour?   
I was under the impression, that storage class transitions (both manual and lifecycle-based) just modify the objects storage class but don't replicate it into multiple versions. True?

Answer

When you specify a lifecycle policy there are options for the current version and the previous version. Have you also applied your existing policy to previous versions?

Answer

I'm aware that a policy can or can not include existing "old" versions. The policy is set only to apply to the current version.  
But there was only ever one version created (by me), a single upload to the object no modifications thereafter. Only after some time, the "old" versions appeared additionally, assumingly created by the policy. An accidental (unintended) re-upload is unlikely, as it involved +500Gbyte that would have needed a couple of days to upload.

Answer

Lifecycle rules do not create a new version of the object. If you have CloudTrail enabled, I recommend looking at your request history to identify what created the second version. That second version would have been created before the lifecycle rule moved the objects to Glacier.

Does a transition rule create versioned objects?

Relevant content