parallelcluster:cluster-name tags are created in duplicate

[mark-ship-it]

If you have an active AWS support contract, please open a case with AWS Premium Support team using the below documentation to report the issue:
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html

Before submitting a new issue, please search through GitHub Issues,
GitHub Wiki and check out the troubleshooting documentation.

Please make sure to add the following data in order to facilitate the root cause detection.

Required Info:

• AWS ParallelCluster version [e.g. 3.1.1]: 3.1.3
• Full cluster configuration without any credentials or personal data.
• Cluster name: all of them
• Output of pcluster describe-cluster command.
• [Optional] Arn of the cluster CloudFormation main stack: we can reproduce this with every cluster and cloudformation stack

Bug description and how to reproduce:
A clear and concise description of what the bug is and the steps to reproduce the behavior.

If you are reporting issues about scaling or job failure:
We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.

For issues with Slurm scheduler, please attach the following logs:

• From Head node: /var/log/parallelcluster/clustermgtd, /var/log/parallelcluster/clusterstatusmgtd (if version >= 3.2.0), /var/log/parallelcluster/slurm_resume.log, /var/log/parallelcluster/slurm_suspend.log, /var/log/parallelcluster/slurm_fleet_status_manager.log (if version >= 3.2.0) and/var/log/slurmctld.log.
• From Compute node: /var/log/parallelcluster/computemgtd.log and /var/log/slurmd.log.

If you are reporting issues about cluster creation failure or node failure:

If the cluster fails creation, please re-execute create-cluster action using --rollback-on-failure false option.

We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.

Please be sure to attach the following logs:

• From Head node: /var/log/cloud-init.log, /var/log/cfn-init.log and /var/log/chef-client.log
• From Compute node: /var/log/cloud-init-output.log.

Additional context:
Any other context about the problem. E.g.:

• CLI logs: ~/.parallelcluster/pcluster-cli.log
• Custom bootstrap scripts, if any
• Screenshots, if useful.

[hanwen-cluster]

Hi,

I apologize for the late reply. Can you describe the problem more and whether it is blocking your usecase?

Thank you,
Hanwen