| haoiii | Back on it now, been away from office for a week++ | 08:23 |
|---|---|---|
| haoiii | Will come back with a status update soon | 08:24 |
| haoiii | Okay so I have managed to unlock my controller, and it is enabled according to system host-list. It also says it is degraded, which I think is a problem. Someone mentioned the horizon webpage, but I do not know which ip address to use to access this. | 08:54 |
| danielcaires[m] | haoiii: The script sets port 8080 to access the horizon dashboard (but you can check the port forwards with vboxmanage list natnets)... the access is via localhost, so "localhost:8080" | 11:04 |
| danielcaires[m] | But you can see the alarms via CLI on the controller, the command is fm alarm-list. As I understand degraded status means that your controller has active alarms, might be wrong though | 11:07 |
| danielcaires[m] | * active alarms, I might be | 11:07 |
| haoiii | https://paste.opendev.org/show/bXXgh40gG2YCz5E26ukI/ | 11:20 |
| haoiii | this is the natnets output, seems like 10.10.10.3 is the ip address, but I am not able to reach from host machine | 11:21 |
| danielcaires[m] | I believe you won't be able to because you are using natnetwork | 11:26 |
| haoiii | okay, how can i then access the horizon dashboard? | 11:30 |
| haoiii | saw your fm alarm-list message now, seems to be a memory problem. "Memory threshold exceeded; threshold 90%, actual 92,97%" | 11:33 |
| haoiii | so I guess it only needs some more memory | 11:33 |
| haoiii | right? | 11:33 |
| danielcaires[m] | yes! | 11:42 |
| danielcaires[m] | To access the horizon: from your browser access http://localhost:8080 | 11:42 |
| haoiii | Giving it 29gb+ memory, still same error. Struggling to understand | 13:09 |
| brunomuniz[m] | Like daniel.caires said, you should be able to access the Dashboard via `localhost:8080` because you have the following rule (from you paste earlier): "StarlingX-0-horizon-dashbord:tcp:[]:8080:[10.10.10.3]:8080". | 13:21 |
| brunomuniz[m] | The degraded status that you see is not necessarily an error. It's more like a warning for this setup. | 13:23 |
| brunomuniz[m] | * Like daniel.caires said, you should be able to access the Dashboard via `localhost:8080` because you have the following rule (from your paste earlier): "StarlingX-0-horizon-dashbord:tcp:\[\]:8080:\[10.10.10.3\]:8080". | 13:24 |
| haoiii | the localhost url is not working... | 13:29 |
| haoiii | https://paste.opendev.org/show/bjOFVw3dwc4tLusAZHim/ | 13:36 |
| haoiii | this is a new one, think it has enough memory now. | 13:37 |
| danielcaires[m] | haoiii: a simple lock and unlock should clear this alarm | 13:38 |
| brunomuniz[m] | haoiii: from inside the controller, can you check if there's something being served on port 8080? | 13:44 |
| brunomuniz[m] | A simple way to do this is a wget localhost:8080, which should download a file (index.html most likely). | 13:46 |
| brunomuniz[m] | If there is something being served on the VM, then you can check if VirtualBox is being able to correctly forward the ports that are configured (according to the paste you sent). | 13:52 |
| brunomuniz[m] | A simple way to do this is to run this on your host machine: netstat -tunlp | grep 8080. It should show something on the output. If not, that's a problem with VirtualBox, unfortunately. A workaround, then, is to restart the NatNetwork that the VMs are using with vboxmanage natnetwork stop --netname NatNetwork; vboxmanage natnetwork start --netname NatNetwork. | 13:52 |
| brunomuniz[m] | This happened to me before and I'm investigating this on the VirtualBox community. Others reported something similar. | 13:53 |
| brunomuniz[m] | Funny enough... this JUST HAPPENED to one of my clusters. Restarting the NatNetwork in VirtualBox solved it. | 14:17 |
| brunomuniz[m] | I'm having a problem deploying a Helm Chart and I don't know how to investigate anymore. It's the one I mentioned in the community call minutes ago.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/yJjqnXCGcaGkvknpROTVRXfF>) | 15:26 |
| brunomuniz[m] | A " sudo docker run ... registry.local:9001/poc-starlingx-novo" works just fine, by the way. | 15:27 |
| brunomuniz[m] | This solved the problem: https://docs.starlingx.io/usertasks/kubernetes/using-an-image-from-the-local-docker-registry-in-a-container-spec.html | 19:18 |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline briefly for a minor upgrade at 21:00 utc, approximately an hour from now | 20:04 | |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline briefly for a minor upgrade, but should return shortly | 21:03 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!