placement-common dpkg error (typo: chmod != chown)

Bug #1848484 reported by Daniel 'f0o' Preussker
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Cloud Archive
Fix Released
Medium
Unassigned
Train
Fix Released
Undecided
Unassigned

Bug Description

Setting up placement-common (2.0.0-0ubuntu1~cloud0) ...
chmod: invalid mode: ‘placement:placement’
Try 'chmod --help' for more information.
dpkg: error processing package placement-common (--configure):
 installed placement-common package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of python3-placement:
 python3-placement depends on placement-common (= 2.0.0-0ubuntu1~cloud0); however:
  Package placement-common is not configured yet.

dpkg: error processing package python3-placement (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of placement-api:
 placement-api depends on python3-placement (= 2.0.0-0ubuntu1~cloud0); however:
  Package python3-placement is not configured yet.

dpkg: error processing package placement-api (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          No apport report written because the error message indicates its a followup error from a previous failure.
             Errors were encountered while processing:
 placement-common
 python3-placement
 placement-api
E: Sub-process /usr/bin/dpkg returned an error code (1)

summary: - placement-common dpkg error
+ placement-common dpkg error (typo: chmod != chown)
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Hi Daniel,

I haven't seen that. Is this on bionic-train? Also can you paste what you have in /var/lib/dpkg/info/placement-common.postinst?

Thanks,
Corey

Revision history for this message
Corey Bryant (corey.bryant) wrote :

Ahh, I see the issue. This will occur if /var/lib/placement/placement.sqlite exists:

    if [ -e /var/lib/placement/placement.sqlite ];
    then
        chmod placement:placement /var/lib/placement/placement.sqlite
        chmod 640 /var/lib/placement/placement.sqlite
    fi

Changed in cloud-archive:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Daniel, I have this fixed in the package source. As it is release day for Eoan (and Train goes through Eoan first), I think we need to treat this as an SRU. Can you work around this in the mean time?

Revision history for this message
Daniel 'f0o' Preussker (dpreussker) wrote :

Corey, removing the sqlite db fixes the issue, Thanks :)

Revision history for this message
Corey Bryant (corey.bryant) wrote :

Great, thanks for letting me know. We'll likely pair this up with the first stable point release of placement if that is ok.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

This has been fixed in Focal (Ussuri) since placement 3.0.0~b1~git2019121614.3eab6acb-0ubuntu1.

Changed in cloud-archive:
status: Triaged → Fix Released
Revision history for this message
Corey Bryant (corey.bryant) wrote : Please test proposed package

Hello Daniel, or anyone else affected,

Accepted placement into train-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:train-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-train-needed to verification-train-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-train-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-train-needed
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Tested successfully:

-rw-r----- 1 placement placement 0 Dec 6 19:39 /var/lib/placement/placement.sqlite
root@b1:~# apt policy placement-common
placement-common:
  Installed: 2.0.1-0ubuntu1~cloud1
  Candidate: 2.0.1-0ubuntu1~cloud1
  Version table:
 *** 2.0.1-0ubuntu1~cloud1 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-proposed/train/main amd64 Packages
        100 /var/lib/dpkg/status
root@b1:~# sudo ls -al /var/lib/placement/placement.sqlite
-rw-r----- 1 placement placement 0 Dec 6 19:39 /var/lib/placement/placement.sqlite

Revision history for this message
Corey Bryant (corey.bryant) wrote : Update Released

The verification of the Stable Release Update for placement has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

This bug was fixed in the package placement - 2.0.1-0ubuntu1~cloud1
---------------

 placement (2.0.1-0ubuntu1~cloud1) bionic-train; urgency=medium
 .
   [ Corey Bryant ]
   * d/placement-common.postinst: Fix chown typo (LP: #1848484).
   * d/gbp.conf: Create stable/train branch.
 .
   [ Chris MacNaughton ]
   * d/control: Update VCS paths for move to lp:~ubuntu-openstack-dev.
   * New stable point release for OpenStack Train (LP: #1923038).
 .
 placement (2.0.0-0ubuntu1) eoan; urgency=medium
 .
   * New upstream release for OpenStack Train.
   * d/control: Align (Build-)Depends with upstream.
   * d/p/add-skip-locks-flag-to-mysql-migrate-db.patch: Dropped.
     Fixed in new upstream release.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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