MISSION CONTROL: Why Artifactory Replications May Not Be Visible in Mission Control

MISSION CONTROL: Why Artifactory Replications May Not Be Visible in Mission Control

AuthorFullName__c
Yonatan Brand
articleNumber
000004512
ft:sourceType
Salesforce
FirstPublishedDate
2019-07-22T08:53:07Z
lastModifiedDate
2021-05-24
VersionNumber
5

Relevant versions: This information pertains to Mission-Control versions 3.x and below

If you’re unable to see Artifactory replications in Mission-Control (see below screenshot), this may be due to a misconfiguration on the Artifactory side, and not necessarily in Mission Control. When this occurs, in most instances the following error will appear in your Mission Control logs:

2019-06-26 00:20:05.183 [pool-3-thread-1] [ERROR] (o.j.m.s.c.p.ConnectionProviderService:37) – Connection provider org.jfrog.mc.service.connection.provider.ReplicationConnectionProvider@66bacdbc could not get connections.
java.lang.IllegalArgumentException: Package type 'vagrant' is not supported in virtual repositories
        at org.jfrog.artifactory.client.model.impl.RepositoryBuilderBase.validate(RepositoryBuilderBase.java:115)
        at org.jfrog.artifactory.client.model.impl.VirtualRepositoryBuilderImpl.build(VirtualRepositoryBuilderImpl.java:57)
        at org.jfrog.artifactory.client.model.impl.VirtualRepositoryBuilderImpl.build(VirtualRepositoryBuilderImpl.java:16)
        at org.jfrog.artifactory.client.model.builder.RepositoryBuilder$build$1.call(Unknown Source)
        at org.jfrog.artifactory.client.parser.ConfigDescriptorParser.buildVirtualRepo(ConfigDescriptorParser.groovy:117)
        at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)

This shows that a virtual repository has been configured for a package type that doesn’t support virtual repositories. This scenario can arise if you've created a virtual repository using the REST API.

More information is available HERE.
To resolve this issue, reorient your repository from virtual to either local or remote.