Your message dated Fri, 09 Oct 2026 11:09:59 +0000
with message-id <[email protected]>
and subject line Bug#883723: fixed in openstack-meta-packages 0.42
has caused the Debian Bug report #883723,
regarding openstack-deploy: incomplete, undocumented
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
883723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883723
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openstack-deploy
Version: 0.15
Severity: minor

After running "openstack-deploy all-in-one", I find that I do have
something resembling a working openstack installation. Thanks for that!

Unfortunately, however, after all that has happened, one sits there with
a "now what" feeling:

- The installation asks for a number of things. What do these things
  mean? (just hitting "enter" to everything *seems* to work, except for
  the "keystone endpoint IP, for which I just entered 127.0.0.1 in this
  test environment).
- Something is running, but where? (localhost:80, it turns out, with
  non-SSL HTTP redirected to its SSL version)
- After fiddling with apache SSL settings so that those work (this was
  on a pristine VM to test with), I need to log on. What with? (the
  value of RC_KEYSTONE_ADMINPASS in /root/osinstallrc, it turns out)

I realize that the goal of openstack-deploy is probably to support
openstack-tempest-ci rather than to support users; but since it's
packaged in Debian, and since it seems to have several modes, all of
which should support larger installations too, it seems like a prime
candidate for "look at this if you want to build your own cloud"

If only it were a bit better documented.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unreleased'), (500, 'unstable'), 
(500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, m68k, arm64

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openstack-deploy depends on:
ii  ipcalc                 0.41-5
pn  openstack-pkg-tools    <none>
pn  python-keystoneclient  <none>

openstack-deploy recommends no packages.

openstack-deploy suggests no packages.

--- End Message ---
--- Begin Message ---
Source: openstack-meta-packages
Source-Version: 0.42
Done: Thomas Goirand <[email protected]>

We believe that the bug you reported is fixed in the latest version of
openstack-meta-packages, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated openstack-meta-packages 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 09 Oct 2026 10:17:34 +0200
Source: openstack-meta-packages
Architecture: source
Version: 0.42
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Closes: 883723
Changes:
 openstack-meta-packages (0.42) unstable; urgency=medium
 .
   * Fixed and completed preseed-lib to match the current debconf
     questions of all OpenStack services (shared openstack-pkg-tools
     templates), added placement, gnocchi, ironic, magnum, octavia and
     vigie preseeding, and rewrote openstack-preseed on top of preseed-
     lib (now shipped in /usr/sbin).
   * openstack-preseed: fully automated with zero interaction: single-
     node and proxy-node auto-detect everything and save their values in
     /root/osinstallrc (also creating a remote-capable openstack RabbitMQ
     user), while compute-node reads them from that same file and only
     prompts for missing values.
   * openstack-deploy now prints a summary of what has been installed and
     of what still needs to be done at the end of a deployment run, and
     the whole deployment tooling is documented in a top-level README.md
     (Closes: #883723).
Checksums-Sha1:
 cee9e24fe2cf19fc651781e4729365a3723a6561 2452 openstack-meta-packages_0.42.dsc
 1734d7d09aed571aa96fd3dd69af5a2e79397358 59144 
openstack-meta-packages_0.42.tar.xz
 9098febccb705a24cd8c00167650cee3ed31dc70 8392 
openstack-meta-packages_0.42_amd64.buildinfo
Checksums-Sha256:
 a5f6b6f3db5bf477012556af6db27917e92c6976c4c4f232095fd47e52785cdd 2452 
openstack-meta-packages_0.42.dsc
 68528707ac0fdc8260f830b532e9b6aed8bcfa28671a911ccd1e25e92e929f02 59144 
openstack-meta-packages_0.42.tar.xz
 b5543d8ac3a45c39a7c4afca28887408030e84f58e3a8bd2b1553988b173a333 8392 
openstack-meta-packages_0.42_amd64.buildinfo
Files:
 044944061bd1ee4b7d868e96513072e3 2452 net optional 
openstack-meta-packages_0.42.dsc
 6fcf5db310da4d4f9701c4667fe894e0 59144 net optional 
openstack-meta-packages_0.42.tar.xz
 f18190b809571467f1702af2dbce4bee 8392 net optional 
openstack-meta-packages_0.42_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmrIxg4ACgkQ1BatFaxr
Q/4PjxAAnYyhISioR4IkUKqKvkYtSI/+m5fFjtJ+VG5C/rcbNhTGHoeVoo0M7Ur3
+bWdDOvNSTMHjo3Db+57Xz+0YAYrDK7EZrvfxPwV3SnQI9SaSbUSfPBPE2D3UXvq
OXmojj8FLCY/PZT9/XzPezPTD7CSZ9loBwQeH5cvOjHvGjH37esOySbQPpw7cMWt
p3taGyzfE0aCEjnz1Et+P0uB4uQMwz1+g+mmRf29KQDh9OujUkBsK3CDhsC2hLsj
V3ZY56yJHwtYQvcXMyrs8Htx+dkyi5/RMhK7iD0mpiLrNu5FMulEXfLPqYl4zLR5
GEsl8W6AyKMliB+ZJxGxHNvsbiThmd7g5Ni8vUmz76ulicG+vDEq9ZNpMNmT71e4
TbK7Sa9dkbB62U1A/fB8S9sVN6jwrA/ajomTu7yRiELEaBqsEiwbbRD9HjNuO25P
In9CA4BaOLcDuW+vjNPbL6nkcv6c+EaUCHbJKxuGSLE9SjJ/JMHDQb3+1g+5vGZf
m6dHGac2pxdI542AxISyx5awS6LHg9JiGqwWTc4aWw8uAqA7my6bnEPpz+oMwXwi
Ph1sxJMhuWbx0L6o5CDU3ZRUip65l/vwDKvzEFQt12YyL+NhbVTwZbXvrTfv8IQ3
i4FLud3jfVHiMI3Aes5UySJ2pL0uH0AnaaJ671LtJyK8IrzLHsM=
=8XQO
-----END PGP SIGNATURE-----

Attachment: pgpGoBdF4gEJK.pgp
Description: PGP signature


--- End Message ---

Reply via email to