Local repository moved and sym-linked, leads to puppet agent failure: missing repomd.xml

Discussion created by Stefano Elia on Feb 5, 2018
Latest reply on Feb 5, 2018 by John Snider

Like • Show 0 Likes0
Comment • 1

Hi all,
I have already browsed the browsable about the "missing repomd.xml" issue, but I already know the reason I'm getting this error.

Briefly, RSA support moved my local repository from /var/netwitness/srv/www/rsa/updates/{version} to another location in filesystem, in order to free some precious disk space. Then they made a symlink to the new location.

When I run puppet agent -t, I encounter the said error "cannot find repomd.xml for RSASoftware".
Later I discovered that if I run "curl http://puppetmaster.local/rsa/updates/{version}" , I get 403 (forbidden).

My question is: is there a way to allow puppet to follow that symlink? Or should I set some permission in order to make that file available via http?

Or am I forced to move back the local repo, in order to make things work again?

Any helpful consideration is appreciated.
Thank you.

Stefano

Outcomes

1 Reply

John Snider Feb 5, 2018 6:52 PM
It sounds like the Symbolic link is incorrect, and you may also have manifest issues.
When moving a repository, there are a couple of things that need to be done. For this example, I'll use the 10.6.5 repo and the 10.6.5.1 repo (which both show up in /var/netwitness/srv/www/rsa/updates/ as 10.6.5) I'm also going to use /var/netwitness/ipdbextractor filesystem as the place to MOVE the repo.
- Prepare the system to stage the repos
  Delete all repos in the UI: Administration -> System -> Updates -> manage repos select and delete any repos.
  Delete ALL files in the updats directory: rm -rf /var/netwitness/srv/www/rsa/updates/*
  Drop the puppet "repos" table from mongo: echo -e "db.repos.drop()\nquit()\n" | mongo puppet
- Stage the 10.6.5 repo
  upload the repo files via the UI as normal, an "move to repo"
  cd /var/netwitness/srv/www/rsa/updates/ , you should see the 10.6.5 directory and a manifest directory
  move the repo directory -> mv 10.6.5 /var/netwitness/ipdbextractor/repo_10.6.5
  move the manifest directory -> mv manifest /var/netwitness/ipdbextractor/manifest_10.6.5
  create a dump of the puppet "repos" table from mongo:
  cd /var/netwitness/ipdbextractor
  mkdir puppet_10.6.5
  cd puppet_10.6.5
  mongodump -d puppet -c repos
  Now that all the data required for 10.6.5 are staged in an alternate directory, you can sim-link them
  cd /var/netwitness/srv/www/rsa/updates
  ln -s /var/netwitness/ipdbextractor/repo_10.6.5 10.6.5
  ln -s /var/netwitness/ipdbextractor/manifest_10.6.5 manifest
- Now stage the next repo (10.6.5.1) the same way, except BEFORE uploading the files to the repo, be sure to unlink the current links, as the 10.6.5.1 will be uploaded into a directory named 10.6.5 which would mix the files with the 10.6.5 files.
  cd /var/netwitness/srv/www/rsa/updates
  unlink 10.6.5
  unlink manifest
  echo -e "db.repos.drop()\nquit()\n" | mongo puppet
- Stage the 10.6.5.1 repo
  upload the repo files via the UI as normal, an "move to repo"
  cd /var/netwitness/srv/www/rsa/updates/ , you should see the 10.6.5 directory and a manifest directory
  move the repo directory -> mv 10.6.5 /var/netwitness/ipdbextractor/repo_10.6.5.1
  move the manifest directory -> mv manifest /var/netwitness/ipdbextractor/manifest_10.6.5.1
  create a dump of the puppet "repos" table from mongo:
  cd /var/netwitness/ipdbextractor
  mkdir puppet_10.6.5.1
  cd puppet_10.6.5.1
  mongodump -d puppet -c repos
  Now that all the data required for 10.6.5 are staged in an alternate directory, you can sim-link them
  cd /var/netwitness/srv/www/rsa/updates
  ln -s /var/netwitness/ipdbextractor/repo_10.6.5.1 10.6.5
  ln -s /var/netwitness/ipdbextractor/manifest_10.6.5.1 manifest
- To switch between repos (say you have a new RMA running 10.6.0.0 and need to upgrade it to 10.6.5, then to 10.6.5.1 before restoring a backup to it).
  Unlink the active repo
  cd /var/netwitness/srv/www/rsa/updates
  unlink 10.6.5
  unlink manifest
  echo -e "db.repos.drop()\nquit()\n" | mongo puppet
  Link to the target repo and update puppet
  cd /var/netwiness/srv/www/rsa/updates
  ln -s /var/netwitness/ipdbextractor/repo_10.6.5.1 10.6.5
  ln -s /var/netwitness/ipdbextractor/manifest_10.6.5.1 manifest
  mongorestore -d puppet -c repos --drop /var/netwitness/ipdbextractor/puppet_10.6.5.1/dump/puppet/repos.bson
1 person found this helpful
Like • Show 2 Likes2
Actions

Local repository moved and sym-linked, leads to puppet agent failure: missing repomd.xml

Outcomes

Related Content

Recommended Content