Your message dated Tue, 22 Jul 2025 09:29:05 +0000
with message-id <[email protected]>
and subject line Re: Forgot zaqar
has caused the Debian Bug report #1109696,
regarding unblock: cloudkitty/22.0.0-1
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.)
--
1109696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109696
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:cloudkitty
User: [email protected]
Usertags: unblock
Please unblock package cloudkitty
Please unblock package openstack-trove
Please unblock package vitrage
I forgot that one in the list of packages to unblock with the export:
env = OS_OSLO_MESSAGING_RABBIT__PROCESSNAME=cloudkitty-api
[ Reason ]
Avoid using the same file as other OpenStack API, therefore, not being able
to start when another OpenStack API starts.
[ Impact ]
Not being able to start cloudkitty-api.
[ Tests ]
Manually tested this fix.
[ Risks ]
No risk.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
The same applies to openstack-trove and vitrage. The diff being very
simillar (ie: just an export of OS_OSLO_MESSAGING_RABBIT__PROCESSNAME
at startup), I haven't produced diff files. Let me know if you think they
are still needed.
unblock cloudkitty/22.0.0-1
unblock openstack-trove/1:23.0.0-2
unblock vitrage/14.0.0-4
diff --git a/debian/changelog b/debian/changelog
index c5eb6f3..d0edc1e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cloudkitty (22.0.0-2) unstable; urgency=medium
+
+ * Add export OS_OSLO_MESSAGING_RABBIT__PROCESSNAME for all daemons.
+
+ -- Thomas Goirand <[email protected]> Fri, 11 Jul 2025 13:43:26 +0200
+
cloudkitty (22.0.0-1) unstable; urgency=medium
* New upstream release.
diff --git a/debian/cloudkitty-api-uwsgi.ini b/debian/cloudkitty-api-uwsgi.ini
index c6b56ce..6edd38f 100644
--- a/debian/cloudkitty-api-uwsgi.ini
+++ b/debian/cloudkitty-api-uwsgi.ini
@@ -53,6 +53,8 @@ listen = 100
##################################
### OpenStack service specific ###
##################################
+env = OS_OSLO_MESSAGING_RABBIT__PROCESSNAME=cloudkitty-api
+
# This is needed, otherwise connections stay open
add-header = Connection: close
diff --git a/debian/cloudkitty-processor.init.in
b/debian/cloudkitty-processor.init.in
index deb2381..3f04047 100644
--- a/debian/cloudkitty-processor.init.in
+++ b/debian/cloudkitty-processor.init.in
@@ -16,3 +16,4 @@
DESC="OpenStack CloudKitty processor"
PROJECT_NAME=cloudkitty
NAME=${PROJECT_NAME}-processor
+export OS_OSLO_MESSAGING_RABBIT__PROCESSNAME=cloudkitty-processor
--- End Message ---
--- Begin Message ---
Hi,
On Tue, Jul 22, 2025 at 09:58:07AM +0200, Thomas Goirand wrote:
> unblock cloudkitty/22.0.0-1
> unblock openstack-trove/1:23.0.0-2
> unblock vitrage/14.0.0-4
> unblock zaqar/20.0.0-2
Unblocked.
Ivo
--- End Message ---
