This content has been marked as final. Show 4 replies
Are you using a local repository? Could it have been built with only 11.1 packages and not 11 packages? The error message shows it's checking for version ...175.0... (Solaris 11 11/11) and you've only shown the 11.1 version (...175.1...). Could you run the command from the 1470879.1 doc to see if your repo also has the older version?
pkg info -g <REPO_URL> //solaris/entire\@0.5.11,5.11-0.175.0.0.0.2.0
I get the same error when attempting to install OC 220.127.116.111 on Solaris 11.1 x86.
I have a local repository which I created from the Solaris 11.1 repo ISO's.
Verifying we can reach the solaris IPS repository.
This may take a couple of minutes if it is not currently reachable.
solaris IPS publisher is reachable
Error: //firstname.lastname@example.org,5.11-0.175.0.0.0.2.0 not found in solaris IPS repository, exiting
Looking at the code in the installer script, I see that it is checking the repository for Sol 11.0
# The Solaris entire package that will be included in any repo that contains S11 GA
# which is currently the min S11 version that we support
my $SOLARIS_11_GA_ENTIRE = "//solaris/entire\@0.5.11,5.11-0.175.0.0.0.2.0";
...and a little further on...
# now check to be sure S11 GA is available from the solaris repo
$ret = system("pkg info -r $SOLARIS_11_GA_ENTIRE > /dev/null 2>&1");
print "Error: $SOLARIS_11_GA_ENTIRE not found in solaris IPS repository, exiting\n";
This would imply that I need to install a Sol 11.0 local repository and then upgrade the repository to 11.1 ??
I would have thought that a fresh build using the latest version of OC should be checking for a MINIMUM of 11.0 and been happy to only find 11.1.
Is this a bug or am I missing something ?
Edited by: graham1137 on 11-Dec-2012 00:04
Edited by: graham1137 on 11-Dec-2012 00:05
I don't know if it's a bug or a feature, but it is looking for the 11GA version of the package: after I rsync'd a 11GA repo into my existing 11.1 (so both versions of the package were available) that error message went away.
I took an even easier option... I commented out the "exit 1" in the installer script. :)
The installation then proceeded without any further complaints.
I guess this means that I won't be able to use this repository for Sol 11.0 assets until I do as you did, and install the 11.0 repo files. That's not a biggie for me at the moment, as aside from the Ops Center servers, we have no other Solaris 11 servers in our environment.
I do find it odd that the installer script should choose to exit if a Sol 11 repo is not found. I'm sure that not all OC users intend to manage Solaris 11 assets immediately. One should be able to install the EC software on a Sol 11 server, and worry about the Sol 11 repository later.
Anyhow, thanks for your input halycon. I hope our discussion has helped the original poster.