Unsuccessful installation of OpenStack Rocky on a fresh bionic host

Bug #1792936 reported by Dr. Martin Bobak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Fix Released
High
Dr. Jens Harbott

Bug Description

I'm trying to install OpenStack devstack (Rocky) =using a stable/rocky branch= on a fresh bionic host (Ubuntu 18.04.1 LTS). However, I'm getting a following error:

Package graphviz is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package pm-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package thin-provisioning-tools is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package sysfsutils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libjs-jquery-tablesorter is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'graphviz' has no installation candidate
E: Unable to locate package libapache2-mod-proxy-uwsgi
E: Package 'libjs-jquery-tablesorter' has no installation candidate
E: Package 'pm-utils' has no installation candidate
E: Unable to locate package gir1.2-libosinfo-1.0
E: Couldn't find any package by glob 'gir1.2-libosinfo-1.0'
E: Couldn't find any package by regex 'gir1.2-libosinfo-1.0'
E: Package 'sysfsutils' has no installation candidate
E: Package 'thin-provisioning-tools' has no installation candidate
E: Unable to locate package postgresql-server-dev-all
E: Unable to locate package conntrackd
E: Unable to locate package dstat
+functions-common:apt_get:1 exit_trap
+./stack.sh:exit_trap:515 local r=100
++./stack.sh:exit_trap:516 jobs -p
+./stack.sh:exit_trap:516 jobs=
+./stack.sh:exit_trap:519 [[ -n '' ]]
+./stack.sh:exit_trap:525 '[' -f '' ']'
+./stack.sh:exit_trap:530 kill_spinner
+./stack.sh:kill_spinner:425 '[' '!' -z '' ']'
+./stack.sh:exit_trap:532 [[ 100 -ne 0 ]]
+./stack.sh:exit_trap:533 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:535 type -p generate-subunit
+./stack.sh:exit_trap:538 [[ -z /opt/stack/logs ]]
+./stack.sh:exit_trap:541 /opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs
World dumping... see /opt/stack/logs/worlddump-2018-09-17-084639.txt for details
/bin/sh: 1: brctl: not found

I tried different versions of local.conf, but it leads to the same error. This concrete error I got with a following (minimalist) local.conf file:

[[local|localrc]]

USE_PYTHON3=True

############################################################
# Customize the following HOST_IP based on your installation
############################################################
HOST_IP=127.0.0.1

ADMIN_PASSWORD=devstack
MYSQL_PASSWORD=devstack
RABBIT_PASSWORD=devstack
SERVICE_PASSWORD=$ADMIN_PASSWORD
SERVICE_TOKEN=devstack

Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

I cannot reproduce this, looks like something is wrong with your host. Is this a physical machine or a VM? How did you install the host? Are you using a local package mirror? Please show the output of "apt policy graphviz".

Changed in devstack:
status: New → Incomplete
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Oh, wait, I can reproduce this by building a machine from a server ISO instead of running a pre-built cloud image. Will dig further.

Changed in devstack:
status: Incomplete → In Progress
assignee: nobody → Dr. Jens Harbott (j-harbott)
importance: Undecided → High
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

O.k., so the reason for this behaviour seems to be that the failing packages are living in the "universe" repository. And the installation ISO only contains packages from "main" and "restricted", so this is what gets enabled by default, see also [1]. As a workaround, you can edit the /etc/apt/sources.list file and add "universe" after "main" on each line. Maybe we can have devstack do this automatically, otherwise there should at least be some warning in the documentation.

[1] https://help.ubuntu.com/community/Repositories/Ubuntu

Revision history for this message
Dr. Martin Bobak (martin.bobak) wrote :

Yes, you are right. Everything works fine, after adding the "universe" repository as you recommend.

I think, devstack should do it automatically, and there has to be information about it in documentation definitely.

About a pre-built cloud image, is it possible to use it by a virtual machine created by Virtual Box 5.2.10_Ubuntu r121806 (the host runs Ubuntu 18.04.1 LTS)?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master
Review: https://review.openstack.org/619562

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master)

Reviewed: https://review.opendev.org/619562
Committed: https://git.openstack.org/cgit/openstack/devstack/commit/?id=8d1b20b4c2334dc3045cea93441568657869f6d1
Submitter: Zuul
Branch: master

commit 8d1b20b4c2334dc3045cea93441568657869f6d1
Author: Jens Harbott <email address hidden>
Date: Thu Nov 22 13:17:01 2018 +0000

    Enable universe repository on Ubuntu

    The universe repository is not enabled when installing Ubuntu from an
    ISO (at least for Bionic). This leads to some errors during the devstack
    run that are not seen when running based on a cloud image which has that
    repo enabled by default. Enable that repository unconditionally, the
    operation is idempotent.

    Change-Id: Ifcb7ecd78fb25ca2136f5848c19b74500e520873
    Closes-Bug: 1792936

Changed in devstack:
status: In Progress → Fix Released
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.