Hi Roman, That's great, that worked with one correction. Had to run with service/maas-region instead of just service/maas in the default setup. # kubectl -n ucp expose service/maas-region --type=NodePort --name=maas-dashboard On Mon May 06 2019 15:14:28 GMT+0000 (Greenwich Mean Time), Roman Gorshunov wrote:
Hi Hlini,
You are missing MaaS dashboard port.
Apply this patch: https://review.opendev.org/#/c/632457/
Publish MaaS dashboard: kubectl -n ucp expose service/maas --type=NodePort --name=maas-dashboard Get MaaS dashboard port: kubectl -n ucp get service maas-dashboard -o jsonpath="{.spec.ports[?(@.port==80)].nodePort}"
Hope it will help.
Best regards, -- Roman Gorshunov
On Mon, May 6, 2019 at 1:56 PM Hlini Melsteð Jóngeirsson <hlini@vivaldi.com> wrote:
Hi there,
I was wondering if is was intentional that MAAS was not working in the "Airship in a bottle" setup.
When it finishes I get the following text output.
n0: Other dashboards: n0: n0: MAAS: http://192.168.121.127:/MAAS/ admin/password12
That link is missing the port. I tried most of the open ports but didn't find the right one, seemed like the mapping was missing to me when I had a closer look at kubernetes.
-- All the best, Hlini
_______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
-- Hlini