quickstart.sh fails installing libvirt packages on newly provisioned Centos 7 host

Bug #1599506 reported by James Slagle
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

On a newly provisioned Centos 7 host, quickstart.sh fails on the libvirt packages install task with:

Transaction check error:\n file /usr/lib/systemd/system/blk-availability.service from install of device-mapper-7:1.02.107-5.el7_2.5.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64\n file /usr/sbin/blkdeactivate from install of device-mapper-7:1.02.107-5.el7_2.5.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64\n file /usr/share/man/man8/blkdeactivate.8.gz from install of device-mapper-7:1.02.107-5.el7_2.5.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64

The command I'm running is:
bash quickstart.sh --config config/general_config/devmode.yml --release master-tripleo localhost

I suppose this might be an issue with using older installation media.

Doing a full yum update and then rerunning the quickstart.sh makes the issue go away. Perhaps we should recommend that in the README or add a task for it?

Tags: quickstart
Revision history for this message
Ronelle Landy (rlandy) wrote :

'yum upgrade lvm2' is all that is required.

I agree this needs to be added to the README.

Revision history for this message
Ronelle Landy (rlandy) wrote :
Revision history for this message
Gabriele Cerami (gcerami) wrote :

This is a very particular situation, I don't think the README is the right place. A FAQ maybe ? or TROUBLESHOOTING ? Maybe we should force an update of that package in the tasks ?

Ronelle Landy (rlandy)
Changed in tripleo-quickstart:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
John Trowbridge (trown) wrote :

moved to tripleo lp with quickstart tag

I think we should at least update lvm in a task in environment/setup.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-2
no longer affects: tripleo-quickstart
tags: added: quickstart
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Natal Ngétal (hobbestigrou) wrote :

It's already fixed:

https://bugzilla.redhat.com/show_bug.cgi?id=1325394

The conflict is not present with the new version of lvm2.

Revision history for this message
Jiří Stránský (jistr) wrote :

Thanks Natal, we've been bumping this bug forward since Pike and indeed it looks like it can be closed.

Revision history for this message
Jiří Stránský (jistr) wrote :

Or actually, i guess it depends if the fixed package is on recent newly provisioned CentOSes...

Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
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.