Solaris 11.1 - 11.2 (SRU) local repository upgrade problem

Question

Hello,
We have had several attempts at upgrading a previously working local IPS repository.  The repository started as an 11.1 repository, then was upgraded with SRUs to 11.1.13.  At this stage the repo server itself and all other machines were able to ‘pkg update’ successfully.
However we now want to pick up 11.2.
We tried two ways of doing this:
Upgrade existing 11.1.13 repo to 11.2 release then upgrade again to 11.2.2.8.0 SRU.
Start with a clean 11.2 release repo then apply 11.2.2.8.0 SRU.
In both cases, the repo server and all other machines do not correctly ‘pkg update’, they abort early with the following message:
http protocol error: code: 404 reason: Not Found               
URL: 'http://repo-test/s11_2_sru/repo/solaris/manifest/0/install%[email protected]%2C5.11-0.175.2.0.0.42.2%3A20140624T184445Z' (happened 4 times)
It looks like the catalog and filesystem contain the actual packages:
pkgadm@repo-test:/repo/repo$ pkgrepo -s /repo/repo list archive
PUBLISHER NAME                                          O VERSION
solaris install/archive 0.5.11,5.11-0.175.2.0.0.42.2:20140624T184445Z
pkgadm@repo-test:/repo/repo$ pkgrepo -s /repo/repo list entire
PUBLISHER NAME                                          O VERSION
solaris   entire 0.5.11,5.11-0.175.2.2.0.8.0:20140926T190209Z
solaris   entire 0.5.11,5.11-0.175.2.0.0.42.0:20140624T193832Z
However pkg.depotd doesn't seem to be able to extract the manifests on demand, despite multiple attempts at:
pkgrepo rebuild
pkgrepo refresh
svcadm refresh pkg/server
svcadm restart pkg/server
svcadm refresh apache22
svcadm restart apache22
reboot
and so on.
Browsing the repo via the web does indicate *some* manifests are available, just not all of them.

Answer 1

Hi Erik,
Thanks for your update. We've now managed to resolved this. It turned out to be apache getting confused by the '/' in the path:
[Fri Oct 17 14:32:53 2014] [info] [client 192.168.30.130] found %2f (encoded '/') in URI (decoded='/s11_2/solaris/manifest/0/install/[email protected],5.11-0.175.2.0.0.42.2:20140624T184445Z'), returning 404
We've now resolved this by turning on the AllowEncodedSlashes option for apache:
1. add "AllowEncodedSlashes On" at the end of /etc/apache2/2.2/httpd.conf
2. sudo svcadm refresh svc:/network/http:apache22
3. sudo svcadm restart svc:/network/http:apache22
'pkg update' on client now works successfully.
We have asked Oracle to augment their online instruction with this information.
Thanks for trying to help.
JW