Ask Your Question
1

Installing Controller Node: novncproxy

asked 2013-08-17 21:06:08 -0500

anonymous user

Anonymous

Hi, installing the required nova packages on the controller node as suggest in grizzly installation guide I get this:

root@nova-ctrl:~# apt-get install -y nova-api nova-cert nova-common nova-conductor nova-scheduler python-nova python-novaclient nova-consoleauth novnc nova-novncproxy
Reading package lists... Done
Building dependency tree       
Reading state information... Done
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:
 nova-novncproxy : Depends: nova-common (= 2013.1-2) but 2013.1.2-2~bpo70+1 is to be installed
E: Unable to correct problems, you have held broken packages.
root@nova-ctrl:~#

/etc/apt/sources.list:

root@nova-ctrl:~# cat /etc/apt/sources.list
deb http://archive.gplhost.com/debian grizzly main                                                                                                                        
deb http://archive.gplhost.com/debian grizzly-backports main                                                                                                              
deb http://ftp.us.debian.org/debian/ wheezy main
deb-src http://ftp.us.debian.org/debian/ wheezy main
deb http://security.debian.org/ wheezy/updates main
deb-src http://security.debian.org/ wheezy/updates main
deb http://ftp.us.debian.org/debian/ wheezy-updates main
deb-src http://ftp.us.debian.org/debian/ wheezy-updates main

cheers Mathias

edit retag flag offensive close merge delete

Comments

Mathias, why did you post the question anonymously? ;-)

Jobin gravatar imageJobin ( 2013-08-18 06:31:23 -0500 )edit

I don't know to be honest :D This system for asking questions is really weird I think and I guess it was just a reflex to tick a check box when I see it :D Just being curious: How the heck do you know it was me? :D

Mathias Ewald gravatar imageMathias Ewald ( 2013-08-18 08:47:33 -0500 )edit

See the list line of the question :D Just guessed you were honest to give your real name!

Jobin gravatar imageJobin ( 2013-08-19 01:03:40 -0500 )edit

4 answers

Sort by ยป oldest newest most voted
2

answered 2013-08-23 07:52:18 -0500

kourindou Hime gravatar image

I ran into exactly same issue. Clean wheezy install fully upgraded. This dude helped much https://bugs.launchpad.net/nova/+bug/1200643

You can download http://archive.gplhost.com/debian/pool/grizzly/main/n/nova/nova-novncproxy_2013.1-2_all.deb dpkg --force-depends-version -i nova-novncproxy_2013.1-2_all.deb

it seems work for me..

by the way, This is not a debian issue. All packages are belong grizzly repo.. Maybe, reported it to grizzly maintainer.

So basically, just run apt-get as documented, but without nova-novncproxy package:

apt-get install -y nova-api nova-cert nova-common nova-conductor \ nova-scheduler python-nova python-novaclient nova-consoleauth novnc

and then install it manually as above.

edit flag offensive delete link more
0

answered 2013-09-10 05:07:30 -0500

sph gravatar image

I followed the question on launchpad as mentioned earlier and added a way to use nova-novncproxy without doing a force install. Here's the snippet of the answer I posted:

Doing the --force-overwrite does install nova-novncproxy but further package installation cause errors like:

The following packages have unmet dependencies: nova-novncproxy : Depends: nova-common (= 2013.1-2) but 2013.1.2-2~bpo70+1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

So I uninstalled nova-nonvcproxy by dpkg --remove nova-novncproxy

and as i was setting up the controller node - I installed nova-consoleproxy which AFAIK acts as a frontend proxy for novnc, spicehtml5 and other types of console viewers. That got installed and along with it came /etc/init.d/nova-nonvcproxy

nova-consoleproxy decides which console viewer to use depending on the value set in /etc/default/nova-consoleproxy. I updated it to have novnc and then doing:

ls /etc/init.d/nova* | while read line; do $line restart; done

started nova-novncproxy along with the usual set of services.

Hope this helps.

edit flag offensive delete link more
0

answered 2013-09-11 05:35:55 -0500

elurkki gravatar image

updated 2013-09-11 05:36:40 -0500

I bumped to this problem as well. Seems that the nova-novncproxy requires exactly nova-common 2013.1-2 and no newer. What I did was extracting the original deb package, allowing newer nova-common and packaging the packet back. After installation I did not get any problems with cinder or other installations.

1) wget http://archive.gplhost.com/debian/pool/grizzly/main/n/nova/nova-novncproxy_2013.1-2_all.deb
2) dpkg -x nova-novncproxy_2013.1-2_all.deb tmp
3) dpkg-deb --control nova-novncproxy_2013.1-2_all.deb
4) vim DEBIAN/control
Changed the row Depends to be:
Depends: nova-common (>= 2013.1-2), lsb-base (>= 3.0.6), python
5) mv DEBIAN tmp
6) dpkg -b tmp nova-novncproxy_2013.1-2n_all.deb
7) dpkg -i nova-novncproxy_2013.1-2n_all.deb

-Mika

edit flag offensive delete link more
0

answered 2013-08-18 06:20:36 -0500

Jobin gravatar image

Try the following commands:

  1. sudo apt-get clean
  2. sudo apt-get autoclean
  3. sudo apt-get -f install
  4. sudo dpkg --configure -a
  5. sudo apt-get -f install

Then resume your installation process. Refer to How do I resolve unmet dependencies asked on AskUbuntu for a more detailed explanation or alternatives.

edit flag offensive delete link more

Comments

I tried everything suggested on the link you gave me and ran the commands. As I am using Debian I added the contrib and non-free repositories instead. But not luck, I still receive the same error message.

Mathias Ewald gravatar imageMathias Ewald ( 2013-08-18 08:56:42 -0500 )edit

You sure you removed the packages too and re-did the complete installation process? The error you reported is not specific to OpenStack, its a common debian-package system issue(or even RPM ones). Googling will perhaps be more useful, if the above link proved otherwise.

Jobin gravatar imageJobin ( 2013-08-19 01:05:45 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-08-17 21:06:08 -0500

Seen: 1,479 times

Last updated: Sep 11 '13