[PKG-Openstack-devel] Only-jessie install attempt

Turbo Fredriksson turbo at bayour.com
Wed Jun 8 12:29:03 UTC 2016


Installing my all-in-one (sans Compute) Controller node
again, from scratch, I took to hart the jessie/testing
comments earlier so this time I've ONLY enabled Jessie
(and Jessie/Backports).

This is what I get:

----- s n i p -----
bladeA01b:~# apt-get -d install barbican-api barbican-keystone-listener barbican-worker ceilometer-agent-central ceilometer-agent-compute ceilometer-agent-ipmi ceilometer-agent-notification ceilometer-alarm-notifier ceilometer-api ceilometer-collector cinder-api cinder-backup cinder-scheduler cinder-volume designate designate-agent designate-api designate-central designate-mdns designate-pool-manager designate-sink designate-zone-manager glance glance-api glance-glare glance-registry glances heat-api heat-engine ironic-api ironic-conductor ironic-fa-deploy ironic-inspector manila-api manila-scheduler manila-share mistral-api mistral-engine mistral-executor murano-api murano-engine neutron-server senlin-api senlin-engine zaqar-server nova-volume nova-scheduler nova-api magnum-api
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package glance-glare
E: Unable to locate package ironic-fa-deploy
E: Unable to locate package ironic-inspector
E: Unable to locate package murano-api
E: Unable to locate package murano-engine
E: Unable to locate package senlin-api
E: Unable to locate package senlin-engine
----- s n i p -----

That's bad, because Senlin (~ "AutoScalingGroups" in AWS
terms if I understand it correctly) is absolutly required
in my use case. And Glance is kind'a very important to me
as well.

But I preserver, and remove those packages from the command
line:

----- s n i p -----
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 barbican-api : Depends: barbican-common (= 1:1.0.0-6~bpo8+1) but it is not going to be installed
 barbican-keystone-listener : Depends: barbican-common (= 1:1.0.0-6~bpo8+1) but it is not going to be installed
 barbican-worker : Depends: barbican-common (= 1:1.0.0-6~bpo8+1) but it is not going to be installed
 ceilometer-agent-ipmi : Depends: ceilometer-common (= 1:5.0.0-6~bpo8+1) but 2014.1.3-6 is to be installed
 designate-mdns : Depends: designate-common (= 1:1.0.0-3~bpo8+1) but 2014.1-18+deb8u1 is to be installed
                  Depends: python-designate (= 1:1.0.0-3~bpo8+1) but 2014.1-18+deb8u1 is to be installed
 designate-pool-manager : Depends: designate-common (= 1:1.0.0-3~bpo8+1) but 2014.1-18+deb8u1 is to be installed
                          Depends: python-designate (= 1:1.0.0-3~bpo8+1) but 2014.1-18+deb8u1 is to be installed
 designate-zone-manager : Depends: designate-common (= 1:1.0.0-3~bpo8+1) but 2014.1-18+deb8u1 is to be installed
                          Depends: python-designate (= 1:1.0.0-3~bpo8+1) but 2014.1-18+deb8u1 is to be installed
 ironic-api : Depends: ironic-common but it is not going to be installed
 ironic-conductor : Depends: ironic-common but it is not going to be installed
 magnum-api : Depends: magnum-common (= 1.0.0~b1-5~bpo8+1) but it is not going to be installed
 manila-api : Depends: manila-common (= 1:1.0.0-6~bpo8+1) but it is not going to be installed
 manila-scheduler : Depends: manila-common (= 1:1.0.0-6~bpo8+1) but it is not going to be installed
 manila-share : Depends: manila-common (= 1:1.0.0-6~bpo8+1) but it is not going to be installed
 mistral-api : Depends: mistral-common (= 1.0.0-4~bpo8+1) but it is not going to be installed
 mistral-engine : Depends: mistral-common (= 1.0.0-4~bpo8+1) but it is not going to be installed
 mistral-executor : Depends: mistral-common (= 1.0.0-4~bpo8+1) but it is not going to be installed
 zaqar-server : Depends: zaqar-common (= 1.0.0-6~bpo8+1) but it is not going to be installed
----- s n i p -----

My enabled repos:
----- s n i p -----
bladeA01b:~# grep '^deb' $(find /etc/apt -type f -name '*.list' | sort)
/etc/apt/sources.list:deb http://ftp.uk.debian.org/debian/ jessie main contrib non-free
/etc/apt/sources.list:deb http://ftp.uk.debian.org/debian/ jessie-backports main contrib non-free
/etc/apt/sources.list:deb http://ftp.uk.debian.org/debian/ jessie-proposed-updates main contrib non-free
/etc/apt/sources.list:deb http://ftp.uk.debian.org/debian/ jessie-updates main contrib non-free
/etc/apt/sources.list:deb http://security.debian.org/ jessie/updates main contrib non-free
/etc/apt/sources.list.d/celia.list:deb http://celia/debian-jessie local local
/etc/apt/sources.list.d/hp.list:deb http://downloads.linux.hpe.com/SDR/repo/mcp/debian jessie/current non-free
----- s n i p -----

PS. My own repo does NOT contain any openstack stuff. Double
    checked and tripple checked!

----- s n i p -----
bladeA01b:~# apt-cache policy barbican-api
barbican-api:
  Installed: (none)
  Candidate: 1:1.0.0-6~bpo8+1
  Version table:
     1:1.0.0-6~bpo8+1 0
        100 http://ftp.uk.debian.org/debian/ jessie-backports/main amd64 Packages
bladeA01b:~# apt-cache policy barbican-common
barbican-common:
  Installed: (none)
  Candidate: 1:1.0.0-6~bpo8+1
  Version table:
     1:1.0.0-6~bpo8+1 0
        100 http://ftp.uk.debian.org/debian/ jessie-backports/main amd64 Packages
----- s n i p -----


The key here is

  ceilometer-agent-ipmi : Depends: ceilometer-common (= 1:5.0.0-6~bpo8+1) but 2014.1.3-6 is to be installed

and it gets worse and worse the more I try. So it seems
that there's package mismatches in the archive..



Now, since Jessie don't contain one of the services I absolutly
need (and one that I think is quite important), I just went a
head and disabled Jessie completely and upgraded to Testing.

It's been years since I felt the need to run bleeding edge
and I didn't enjoy the experience at the time. But in this
case it might be for the better - Openstack is quite an active
community so it makes more sense to keep with it.


PS. I'm just sending this mail as a comment/notes update.
--
If something's hard to do, then it's not worth doing.
- Homer Simpson




More information about the Openstack-devel mailing list