certificate has expired

[samsalisbury]

Describe the bug
When running this action, I see the following in the logs:

2022-02-18T12:11:17.8413288Z ##[group]Setup JFrog CLI
2022-02-18T12:11:18.2593575Z certificate has expired
2022-02-18T12:11:18.2596765Z Waiting 19 seconds before trying again
2022-02-18T12:11:37.5734329Z certificate has expired
2022-02-18T12:11:37.5735300Z Waiting 18 seconds before trying again
2022-02-18T12:11:55.9134550Z ##[error]certificate has expired
2022-02-18T12:11:55.9207334Z ##[endgroup]
2022-02-18T12:11:55.9353133Z Post job cleanup.
2022-02-18T12:11:56.0852828Z ##[group]Cleanup JFrog CLI servers configuration
2022-02-18T12:11:56.4663941Z certificate has expired
2022-02-18T12:11:56.4667119Z Waiting 14 seconds before trying again
2022-02-18T12:12:10.8074540Z certificate has expired
2022-02-18T12:12:10.8074846Z Waiting 16 seconds before trying again
2022-02-18T12:12:27.1351354Z ##[error]certificate has expired
2022-02-18T12:12:27.1371105Z ##[endgroup]
2022-02-18T12:12:27.1443759Z Post job cleanup.

To Reproduce
Configure the action like this in the GHA workflow:

      - uses: jfrog/setup-jfrog-cli@v1
        env:
          JF_ARTIFACTORY_1: <<redacted>>

Expected behavior
Tool is installed without error.

Screenshots
See logs, no other relevant info.

Versions

• Setup JFrog CLI version: v1
• Workflow operating system: linux
• JFrog CLI version: ?
• Artifactory Version: ?

[eyalbe4]

Thanks for reporting this issue @samsalisbury.
Just making sure - are you seeing this on a Linux agent only?
Does fail the commands, or just prompts the warning?
I'm not sure which certificate it is complaining about...

[samsalisbury]

Hi @eyalbe4, we're running this on Ubuntu 18.04.6 LTS. The action prints the logs you can see above and then fails. Sadly the logs don't give any more detail than that.

We have now upgraded to v2.1.0 and this has resolved the issue for us.

Out of curiosity, what prompted the major version bump to v2? I expected that either the Action or the CLI interface had breaking changes, but was surprised (happily for our needs) that everything continued to work.

[eyalbe4]

@samsalisbury,
I'm happy to hear the issue was resolved by the upgrade, although I'm not yet sure what caused it.
So v2 of the Action brings JFrog CLI v2, which includes breaking changes compared to v1. You can read more about it here.
Please let us know if you have follow-up questions.