Error producing repo metadata
When applying https://github.com/pulp/pulp_rpm/pull/720/files to my pulp install on a centos 6 systen, I am unable to use the produced repo.
I run yum update and get the error TypeError: Parsing primary.xml error: XML declaration allowed only at start of the document.
Sets to repoduce:
Install pulp on rhel/centos 6.
Apply change request above.
Sync any yum repo via pulp
Create yum.repo.d/newfile.repo that points to created repo from pulp.
Run yum update.
Should get the error above.
#8 Updated by email@example.com almost 6 years ago
To try to get specific environment settings, I built a new VM using these steps:
Created VM in libvirt from the http://mirror.us.oneandone.net/linux/distributions/centos/6.7/isos/x86_64/CentOS-6.7-x86_64-netinstall.iso
Gave it 200G for storage space
Set the Language to the default of English
Set the Keyboard layout to the default of US
Pointed to install media http://mirror.centos.org/centos/6/os/x86_64/
Used basic storage devices
Used default hostname and timezone
Updated the partition layout, gave /var most of the space (~140 G)
Chose minimal for software list
Once system boots up:
service iptables stop
chkconfig iptables off
Followed pulp install:
yum install -y wget
rpm -Uvh https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
yum install mongodb-server
service mongod start
chkconfig mongod on
yum install qpid-cpp-server qpid-cpp-server-store
service qpidd start
chkconfig qpidd on
yum groupinstall pulp-server-qpid
sudo -u apache pulp-manage-db
service httpd start
chkconfig httpd on
chkconfig pulp_workers on
service pulp_workers start
chkconfig pulp_celerybeat on
service pulp_celerybeat start
chkconfig pulp_resource_manager on
service pulp_resource_manager start
yum groupinstall pulp-admin
host = localhost.localdomain
ssl_verify = false
pulp-adm rpm repo create --serve-http true --repo-id puppet --feed https://yum.puppetlabs.com/el/6/products/x86_64/
pulp-admin rpm repo sync run
yum update look at stack trace
#9 Updated by firstname.lastname@example.org almost 6 years ago
After taking a much closer look at my manual applying of the patch, it looks like it was a case sensitivity issue with the encoding. I was typing UTF-8 instead of utf-8 for the encoding. I want to run this through on a few more test systems and make sure everything works.
Please register to edit this issue