Thread: rocks-update -c fails with a 404 error

i am having problems running

Code:

rocks-update -c

The result is a failure to complete the command.
this occurred after a run of up2date on the frontend. (Yes, i know that up2date should not be run). up2date log shows only the following packages updated: ['libxml2-2.6.16-12.2', 'libxml2-2.6.16-12.2', 'libxml2-python-2.6.16-12.2'], ['ipsec-tools-0.3.3-7.el4_7'],
I have included an strace of the command execution for review. Any assistance would be appreciated.

Yes, up2date frequently breaks things. If you knew that, why did you run it?

The easiest thing now is to roll back the updates, and to reinstall the original RPMs. You can find them on the install media, but then you will also have to update your repository so that the nodes are provisioned with the same version as on the frontend.

Also, a few questions:
- which version of OCS?
- which OS, RHEL or CentOS?
- can you provide a Python error message?
- please attach the following file, where x.x.x is your OCS version:
/export/home/install/site-profiles/x.x.x/nodes/extend-compute.xml

from rpmpkgs - rocks-dist-4.4.0-0.x86_64.rpm

OK, and? Is that the answer to my questions?

Originally Posted by jfillatr

OK, and? Is that the answer to my questions?

- which version of OCS? 4.4
- which OS, RHEL or CentOS? Red Hat (Release shows 4.7 now)
- can you provide a Python error message?
It isn't a python error. The error is a 404 repository not found.
/export/home/install/site-profiles/x.x.x/nodes/extend-compute.xml isn't available immediately, but I will provide that. Thanks for the help.

Did you recently update your RedHat installation? By any chance, did it work fine before updating, and it doesn't work now that it's been updated?

How did you update your RedHat install? Which tool(s) did you use?

The systems are registered with current entitlements. The updates came from RHN. The tool used was up2date. Yes, it worked prior to updating the head node. You mentioned roll-back earlier, but I don't think that is an option prior to RHEL 5.
I did find that the extend-compute is not modified whatsoever, so nothing different about it from a stock install.

Thinking that the easiest way out is going to be a reinstall. I don't really have an opportunity to work on the system directly. I have to make my recommendations and hope for the best. Since I don't have a system backup, I think that the best option is to backup my license keys and custom configuration files and reinstall the frontend. If that isn't successful . . . I will be back.