Im not sure if this is really happening or not (im on my 3rd iteration to make sure it isnt just me) but it seems that the apigee-repo setup for on prem w/o external internet connectivity is leaving out a couple of key files when building:
The file that Im having issues w/ right now is bootstrap.sh. The file is being generated - but it appears to be empty when I check the file in /opt/apigee/data/apigee-mirror/repos.
I am also now getting this wonderful message:
apigee-4:/home/cloud # bash /tmp/bootstrap.sh apigeerepohost=moyhostapigeeuser=myusername apigeepassword=mypassword apigeeprotocol=http://
…
…
Loaded plugins: security
Setting up Install Process
error: not an rpm package
Cannot open: http://myrepo//apigee-repo-1.0-6.x86_64.rpm. Skipping.
Error: Nothing to do
bootstrap.sh: Error: Repo configuration failed
Which makes sense because the downloaded RPM is a zero byte file:
-rw-r–r-- 1 apigee apigee 0 Apr 14 13:57 apigee-repo-1.0-6.x86_64.rpm
This seems to only be happening for root level objects. Everything else appears to be free-and-clear
It is looking like the repomd.xml docs are also all zero byte which is pretty interesting.
The answer may be hidden in the sync code:
turns out that many of the files are downloaded w/ wget - which is not reading the user shell proxy settings! I am manually modifying the script to handle this. Another thing that could have been resolved w/ access to this code early.
The answer may be hidden in the sync code:
turns out that many of the files are downloaded w/ wget - which is not reading the user shell proxy settings! I am manually modifying the script to handle this. Another thing that could have been resolved w/ access to this code early.
need to add a “proxy server” parameter to the scripts for people that have really seriously locked down networks…
You can also use curl instead of wget as well.
yeah - im kind of hoping that I dont have to re-write all of the tooling that Apigee has provided for on prem.
re-writing it… means.. i might as well not use it.