pkg/util: use random port to make test TestVerifyCommonNameAndRotate stable

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #37819

Problem Summary:

What changed and how does it work?

I suspect the unstable is caused by the environment, maybe there are some other service running using that port.
So I change the port to a random one to avoid conflict.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @tiancaiamao. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codecov]

Codecov Report

Merging #50369 (938e5e9) into master (095227d) will decrease coverage by 14.6304%.
Report is 2 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #50369         +/-   ##
=================================================
- Coverage   70.0357%   55.4054%   -14.6304%     
=================================================
  Files          1444       1555        +111     
  Lines        419997     586921     +166924     
=================================================
+ Hits         294148     325186      +31038     
- Misses       105536     239033     +133497     
- Partials      20313      22702       +2389     

Flag	Coverage Δ
integration	36.5805% <ø> (?)
unit	70.0026% <ø> (-0.0332%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.0269% <ø> (ø)
parser	∅ <ø> (∅)
br	55.4976% <ø> (+5.8036%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, xhebox

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hawkingrei,xhebox]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-12 07:18:07.444656656 +0000 UTC m=+600477.028910329: ☑️ agreed by hawkingrei.
• 2024-01-12 07:44:19.652266318 +0000 UTC m=+602049.236520003: ☑️ agreed by xhebox.

[tiprow]

@tiancaiamao: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tiprow_fast_test	938e5e9	link	true	/test tiprow_fast_test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[hawkingrei]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #50373.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #50374.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #50375.