[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1110104: marked as done (unblock: pcs/0.12.1-2)

Your message dated Thu, 14 Aug 2025 13:52:43 +0200
with message-id <906e549b-f761-4c21-b196-54e704c4bee0@debian.org>
and subject line close all open unblock requests, the trixie release happened
has caused the Debian Bug report #1110104,
regarding unblock: pcs/0.12.1-2
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 owner@bugs.debian.org
immediately.)


-- 
1110104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110104
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pcs@packages.debian.org
Control: affects -1 + src:pcs

Please unblock package pcs

Package was already uploaded to unstable but did not have
enough time to pass to testing.

[ Reason ]
Include minor version update with some bug fixes and improvements
in the stable release.

[ Impact ]
Release is shipped with an older version of pcs that might
have some bugs.

[ Tests ]
Unit tests and autopkgtests are passing for the new package
version.

[ Risks ]
The change is somewhat large, but this is a leaf package so
the impact should be limited in case of problems.

[ 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

[ Other info ]
Whole debdiff is big for email so including only upstream
changelog below.

(Anything else the release team should know.)

unblock pcs/0.12.1-2


diff -Nru pcs-0.12.0.2/CHANGELOG.md pcs-0.12.1/CHANGELOG.md
--- pcs-0.12.0.2/CHANGELOG.md	2025-04-29 18:09:43.000000000 +0200
+++ pcs-0.12.1/CHANGELOG.md	2025-07-08 18:00:53.000000000 +0200
@@ -1,7 +1,57 @@
 # Change Log
 
-## [0.12.0.2] - 2025-04-29
+## [0.12.1] - 2025-07-08
+
+### Added
+- Commands `pcs cluster cib-push` and `pcs cluster edit` now print more info
+  when new CIB does not conform to the CIB schema ([RHEL-63186])
+- Commands `pcs cluster cib-push` and `pcs cluster edit` now print info about
+  problems in pushed CIB even if it conforms to the CIB schema ([RHEL-7681])
+- Command `pcs cluster rename` for changing cluster name ([RHEL-22423])
+- Command `pcs stonith sbd watchdog list` now prints watchdogs' identity and
+  driver ([RHEL-76176])
+- Prevent removing or disabling stonith devices or disabling SBD if the cluster
+  would be left with disabled SBD and no stonith devices ([RHEL-66607])
+- Support for exporting alerts in `json` and `cmd` formats ([RHEL-44347])
+- Output of `pcs status` now contains messages about CIB misconfiguration
+  provided by `crm_verify` pacemaker tool ([RHEL-7681])
+- Support for bundle resources in `pcs resource meta`, disallow updating
+  `remote-node` and `remote-addr` without `--force`, add lib command
+  `resource.update_meta` to API v2 ([RHEL-35407])
+- Support for exporting node attributes and utilization in `json` and `cmd`
+  formats ([RHEL-21050])
+- Support for reading sate and logs directories from systemd environment
+  variables `STATE_DIRECTORY` and `LOGS_DIRECTORY` ([RHEL-96074])
+
+### Fixed
+- Fixed a traceback when removing a resource fails in web UI
+- It is now possible to override errors when editing cluster properties in web
+  UI
+- Display node-attribute in colocation constraints configuration ([RHEL-81938])
+- Fixed cluster status parsing when the `target-role` meta attribute is not
+  properly capitalized as defined by pacemaker specification. Affected
+  commands:
+    - `pcs resource|stonith delete|remove`, `pcs booth delete|remove`,
+      and `pcs cluster node delete-remote|remove-remote` (broken since 0.12.0)
+      ([RHEL-92043])
+    - `pcs status query resource` (broken since 0.12.0)
+- Handle query limit errors coming from rubygem-rack ([RHEL-90151])
 
+[RHEL-7681]: https://issues.redhat.com/browse/RHEL-7681
+[RHEL-21050]: https://issues.redhat.com/browse/RHEL-21050
+[RHEL-22423]: https://issues.redhat.com/browse/RHEL-22423
+[RHEL-35420]: https://issues.redhat.com/browse/RHEL-35407
+[RHEL-44347]: https://issues.redhat.com/browse/RHEL-44347
+[RHEL-63186]: https://issues.redhat.com/browse/RHEL-63186
+[RHEL-66607]: https://issues.redhat.com/browse/RHEL-66607
+[RHEL-76176]: https://issues.redhat.com/browse/RHEL-76176
+[RHEL-81938]: https://issues.redhat.com/browse/RHEL-81938
+[RHEL-90151]: https://issues.redhat.com/browse/RHEL-90151
+[RHEL-92043]: https://issues.redhat.com/browse/RHEL-92043
+[RHEL-96074]: https://issues.redhat.com/browse/RHEL-96074
+
+
+## [0.12.0.2] - 2025-04-29
 ### Fixed
 - Fixed failing test in the 0.12.0.1 tarball

--- End Message ---
--- Begin Message --- 
Hi,
I'm sorry we couldn't unblock your request in time for trixie. I'm closing all open unblock requests in one go, so I'm not going into details of the particular request, but reasons are typically as follow: 
- the request came after the deadline of 2025-07-30
- the request came late and we just didn't have the time to deal with it
- the request was waiting for action from the submitter (moreinfo tag)
- the request didn't appear to be in line with the freeze policy and we
  didn't have the energy to engage (sorry for that, see our FAQ [1])
- there was discussion in the unblock request but no agreement was
  reached in time for the release.

Paul

[1] https://release.debian.org/trixie/FAQ.html

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: