Yes. The host is subscribed using the new RH subscription model. Doing a "yum repo list --details" returns this initial URL for the repo. Getting similar response on my RHEL6 servers
Repo-id : rhel-x86_64-server-optional-6 Repo-name : RHEL Server Optional (v. 6 64-bit x86_64) Repo-updated : Wed Apr 22 06:21:06 2015 Repo-pkgs : 8,279 Repo-size : 13 G Repo-baseurl : *https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/rhel-x86_64-server-optional-6 <https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/rhel-x86_64-server-optional-6>* Repo-expire : 21,600 second(s) (last: Mon Apr 27 08:25:27 2015) Should pulp, via it's yum importers, be able to deal with these URLs? On Mon, Apr 27, 2015 at 11:21 AM, Alan Milligan < [email protected]> wrote: > This looks suspiciously like an old-style RHN-classic up2date repository > - are you sure it's even Yum?? > > On 04/28/2015 01:18 AM, Scott Tinsley wrote: > > That is the problem, I do not know what that base URL is. The URIL given > above cannot be hit via curl. YUM is making an XMLRPC call that is > returning something to YUM that it can then used to get the repomd.xml or > the repomd.xml file itself. But I cannot figure out how to make the XMLRPC > call. I have used the URLGRABBER_DEBUG flag with YUM and seen that YUM gets > are result of > > > > > https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-server-5-rpm/repodata/repomd.xml > > > > You cannot just pull this with a standard http/get/curl. > > > > Since PULP is using a YUM provider, is PULP supposed to be able to > handle the XMLRPC interface?? > > > > On Mon, Apr 27, 2015 at 11:05 AM, Brian Bouterse <[email protected] > <mailto:[email protected]> <[email protected]>> wrote: > > > > I'm not exactly sure on this, but I typically give the feed URL as the > path to the directory that contains the repodata folder. > > -Brian > > On 04/24/2015 03:44 PM, Scott Tinsley wrote: > > I am trying to create a PULP repo of a JBOSS release. The YUM repo > > has this detail. > > > ?Repo-id : jbappplatform-5-i386-server-5-rpm Repo-name : > > Red Hat JBoss EAP (v 5) for 5Server i386 Repo-updated : Mon Nov 10 > > 14:23:21 2014 Repo-pkgs : 746 Repo-size : 1.7 G Repo-baseurl > > : > > https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-serv > er-5-rpm > <https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-serv > er-5-rpm> > <https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-server-5-rpm> > > > Repo-expire : 3,600 second(s) (last: Fri Apr 24 15:10:08 2015) > > Problem is that pulp cannot deal with the URL above. > > > Any URL that goes through https://xmlrpc.rhn.redhat.com/XMLRPC/* > > fails. You cannot do a vanilla HTTP GET against > > https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-serv > er-5-rpm > <https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-serv > er-5-rpm> > <https://xmlrpc.rhn.redhat.com/XMLRPC/GET-REQ/jbappplatform-5-i386-server-5-rpm> > . > > > I am looking for suggestions on how I can get a valid feed URL for PULP. > > > Thanks > > > > _______________________________________________ Pulp-list mailing > > list [email protected] <mailto:[email protected]> > <[email protected]> > > https://www.redhat.com/mailman/listinfo/pulp-list > > > > > _______________________________________________ > > Pulp-list mailing list > > [email protected] <mailto:[email protected]> > <[email protected]> > > https://www.redhat.com/mailman/listinfo/pulp-list > > > > > > > > > > _______________________________________________ > > Pulp-list mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/pulp-list > > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
