Has anyone experienced and resolved an HTTP404 error when registering AWS-based CCO to an on-premise vSphere CCM in C3?
We've got a lab deployment of Cisco Cloud Center 4.8.0, on-premise CCM, CCO, AMQP, Monitor, Repo, Worker; all running normally. We can model, deploy, tag, etc, no problem.
We've previously added AWS-based CCO and RabbitMQ to this environment. We documented the process, to ensure we built a correct run book. Then we tore down the lab (VM resources, time, AWS money, etc). Six months later, we're building it again and everything is working up to the point where we register the AWS-based CCO and RabbitMQ.
When we add the AWS-based CCO/RabbitMQ to CCO, we are getting the dreaded HTTP404 errror. Better than some errors we could get, I suppose, but not very helpful. Looking at logs doesn't provide a lot of insight, other than to verify that everything is going to the IP and port that we expect. Those are allowed in the AWS security constructs, and we can telnet from our CCM to the AWS machine over the port in the logs (8443).
We've had this, and other, errors when registering the on-premise vSphere CCO with CCM; in those cases, restarting the VM or re-running the setup wizards on the VM seems to clear the error. In rare instances we've had to re-deploy the VM. We've tried all of that in this case, and nothing has improved the situation. We have changed a few things to intentionally break Layer3 connectivity, to ensure that the HTTP404 message isn't a generic "I can't reach the other side," and the error message does change accordingly; but when (we think) we've configured everything as before, when "it worked last time," we always get the HTTP404.
... View more