openstack-install fails

Bug #1546484 reported by kevin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

MAAS has been fresh installed, the version is 19. and then failed to configure landscape . before, it was working well on code 18.

below is command.log:

[DEBUG: 02-16 23:42:31, multi.py:391] Running landscape configure: /usr/share/openstack/bin/configure-landscape --admin-email <email address hidden> --admin-name admin --system-email <email address hidden> --maas-host 192.168.110.48
[INFO: 02-16 23:42:34, utils.py:771] pollinate: sudo su - -c 'pollinate -q -r --curl-opts "-k --user-agent uoi/be6718a7-1937-4f93-8bfc-b0f46430eddc/ET"'
[ERROR: 02-16 23:42:36, multi.py:397] Problem with configuring Landscape: {'status': 1, 'err': 'Traceback (most recent call last):\n File "/usr/share/openstack/bin/configure-landscape", line 209, in <module>\n main()\n File "/usr/share/openstack/bin/configure-landscape", line 202, in main\n system_email=args.system_email)\n File "/usr/share/openstack/bin/configure-landscape", line 173, in register_new_user\n \'https://%s/api/\' % host)\n File "/usr/share/openstack/bin/configure-landscape", line 126, in run_query\n assert r.status_code == 200\nAssertionError\n', 'output': ''}.
[ERROR: 02-16 23:42:36, gui.py:267] A fatal error has occurred: Error configuring Landscape.

steps to reproduce:
1. install ubuntu
2. install MAAS 19
3. load image and configure MAAS
4. run command "openstack@can48:~$ sudo openstack-install --openstack-release liberty" to install landscape.

Revision history for this message
kevin (kevin-x-wang) wrote :
Revision history for this message
kevin (kevin-x-wang) wrote :

openstack@can48:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================-=====================================-============-============================================================================================================
ii maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server provisioning libraries

Revision history for this message
kevin (kevin-x-wang) wrote :
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Kevin,

MAAS does not install nor configures Landscape. That seems to be a bug in the openstack-install. I'll retarget accordingly.

no longer affects: maas
summary: - MAAS failed to configure landscape
+ openstack-install fails
Revision history for this message
Adam Stokes (adam-stokes) wrote :

I don't think you have MAAS configured properly, according to this error:

[INFO: 02-16 23:04:23, openstack-install:227] Starting OpenStack Installer v0.99.27
[INFO: 02-16 23:04:23, openstack-install:228] Start command: ['/usr/bin/openstack-install', '--openstack-release', 'liberty']
[INFO: 02-16 23:04:23, openstack-install:239] Creating juju directories: /home/openstack/.cloud-install/juju
[INFO: 02-16 23:04:25, openstack-install:295] Running Liberty release
[INFO: 02-16 23:04:38, installbase.py:132] Performing a OpenStack Autopilot install
[INFO: 02-16 23:04:38, utils.py:771] pollinate: sudo su - -c 'pollinate -q -r --curl-opts "-k --user-agent uoi/be6718a7-1937-4f93-8bfc-b0f46430eddc/IL"'
[DEBUG: 02-16 23:05:14, landscape.py:74] Existing MAAS defined, doing a LDS installation with existing MAAS.
[DEBUG: 02-16 23:05:19, utils.py:618] ssh keys exist for this user, they will be used instead.
[DEBUG: 02-16 23:05:19, multi.py:127] Bootstrapping Juju: JUJU_HOME=/home/openstack/.cloud-install/juju juju bootstrap
[ERROR: 02-16 23:23:47, multi.py:206] Failed to get ip directly: [Errno -2] Name or service not known

Is your MAAS configured to manage both dns/dhcp on your private network?

tags: added: cloud-installer
Revision history for this message
kevin (kevin-x-wang) wrote :

hello, Stokes

yes, i did configure DNS/DHCP on private networks

openstack@can48:~$ sudo cat /etc/resolv.conf
[sudo] password for openstack:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.106.16.23
nameserver 10.108.94.48
nameserver 192.168.110.48

search test.emc.com maas
openstack@can48:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:56:a4:43:12
          inet addr:10.108.94.48 Bcast:10.108.94.255 Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fea4:4312/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1123141 errors:0 dropped:53 overruns:0 frame:0
          TX packets:172833 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1155379168 (1.1 GB) TX bytes:24749383 (24.7 MB)

eth1 Link encap:Ethernet HWaddr 00:0c:29:bc:74:f0
          inet addr:192.168.110.48 Bcast:192.168.110.255 Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:febc:74f0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2015599 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7054905 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:142058166 (142.0 MB) TX bytes:16221117139 (16.2 GB)

Revision history for this message
kevin (kevin-x-wang) wrote :

hello, Stokers

can i share webex with you to check test bed? you can decision the time, thank you

Revision history for this message
kevin (kevin-x-wang) wrote :

hello, Stokers

any update? thank you

Revision history for this message
Adam Stokes (adam-stokes) wrote :

Are you able to `juju bootstrap` outside of the installer?

Revision history for this message
kevin (kevin-x-wang) wrote :

"bootstrap" has been done during "sudo openstack-install --openstack-release liberty". same output if i run command again
openstack@MAAS:~$ juju bootstrap
WARNING ignoring environments.yaml: using bootstrap config in file "/home/openstack/.cloud-install/juju/environments/maas.jenv"
WARNING This juju environment is already bootstrapped. If you want to start a new Juju
environment, first run juju destroy-environment to clean up, or switch to an
alternative environment.
ERROR environment is already bootstrapped

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openstack (Ubuntu):
status: New → Confirmed
Revision history for this message
Adam Stokes (adam-stokes) wrote :

You'll want to make sure you've:

sudo openstack-install -u
rm -rf ~/.cloud-install

Then re-run the installer, please note that you do not have to define --openstack-release as Autopilot is already configured to use the appropriate version.

Also note on 16.04 you'll want to use the new installer via `conjure-up openstack` (apt install conjure-up)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.