I was finally able to build after I modified the spec file to remove the debug_package requirements and add the files to 'noreplace' list. I installed the rpm (and it complained about missing dependencies (on python and perl). I used the --nodeps and installed the rpm and did a 'service openvswitch start' to get the ovsdb-server and others started. I am now able to create a bridge and add ports to it. I will now try and get some VMs to use this bridge & OVS.
It would good to update the spec and the INSTALL.RHEL with this info. The
details of my system are below and I have attached my final .spec file.
[root@lab-sj1-140 init.d]# uname -a
Linux lab-sj1-140 2.6.32-358.6.1.el6.x86_64 #1 SMP Fri Mar 29 16:51:51 EDT 2013
x86_64 x86_64 x86_64 GNU/Linux
[root@lab-sj1-140 init.d]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)
[root@lab-sj1-140 init.d]#
thx,
Kishore
>________________________________
> From: Kyle Mestery (kmestery) <kmest...@cisco.com>
>To: K.R Kishore <krkish...@yahoo.com>
>Cc: "discuss@openvswitch.org" <discuss@openvswitch.org>
>Sent: Wednesday, June 5, 2013 1:35 PM
>Subject: Re: [ovs-discuss] Problems getting OVS to work on RHEL/KVM
>
>
>
>On Jun 5, 2013, at 2:40 PM, K.R Kishore <krkish...@yahoo.com> wrote:
>
>> After re-reading the Error message from rpmbuild, it occured that the error
>> is coming from the debug_package. So I added the following line
>>
>> %define debug_package %{nil}
>>
>> into rhel/openvswitch.spec and the build went further. This time, it fails
>> with the errors about finding these files. Can I remove them? Can I put them
>> in the .spec file to "no replace"?
>>
>We may need to update the RHEL (and likely Fedora) spec files. Which branch
>are you building on? I routinely build Fedora RPMs and I have not see these
>errors included. The Fedora and RHEL spec files are slightly different,
>however, which may account for the below.
>
>Thanks,
>Kyle
>
>> error: Installed (but unpackaged) file(s) found:
>> /usr/bin/ovsdbmonitor
>> /usr/share/applications/ovsdbmonitor.desktop
>> /usr/share/man/man1/ovsdbmonitor.1.gz
>> /usr/share/ovsdbmonitor/OVEApp.py
>> /usr/share/ovsdbmonitor/OVEApp.pyc
>> /usr/share/ovsdbmonitor/OVEApp.pyo
>> /usr/share/ovsdbmonitor/OVECommonWindow.py
>> /usr/share/ovsdbmonitor/OVECommonWindow.pyc
>> /usr/share/ovsdbmonitor/OVECommonWindow.pyo
>> /usr/share/ovsdbmonitor/OVEConfig.py
>> /usr/share/ovsdbmonitor/OVEConfig.pyc
>> /usr/share/ovsdbmonitor/OVEConfig.pyo
>> /usr/share/ovsdbmonitor/OVEConfigWindow.py
>> /usr/share/ovsdbmonitor/OVEConfigWindow.pyc
>> /usr/share/ovsdbmonitor/OVEConfigWindow.pyo
>> /usr/share/ovsdbmonitor/OVEFetch.py
>> /usr/share/ovsdbmonitor/OVEFetch.pyc
>> /usr/share/ovsdbmonitor/OVEFetch.pyo
>> /usr/share/ovsdbmonitor/OVEFlowWindow.py
>> /usr/share/ovsdbmonitor/OVEFlowWindow.pyc
>> /usr/share/ovsdbmonitor/OVEFlowWindow.pyo
>> /usr/share/ovsdbmonitor/OVEHostWindow.py
>> /usr/share/ovsdbmonitor/OVEHostWindow.pyc
>> /usr/share/ovsdbmonitor/OVEHostWindow.pyo
>> /usr/share/ovsdbmonitor/OVELogWindow.py
>> /usr/share/ovsdbmonitor/OVELogWindow.pyc
>> /usr/share/ovsdbmonitor/OVELogWindow.pyo
>> /usr/share/ovsdbmonitor/OVELogger.py
>> /usr/share/ovsdbmonitor/OVELogger.pyc
>> /usr/share/ovsdbmonitor/OVELogger.pyo
>> /usr/share/ovsdbmonitor/OVEMainWindow.py
>> /usr/share/ovsdbmonitor/OVEMainWindow.pyc
>> /usr/share/ovsdbmonitor/OVEMainWindow.pyo
>> /usr/share/ovsdbmonitor/OVEStandard.py
>> /usr/share/ovsdbmonitor/OVEStandard.pyc
>> /usr/share/ovsdbmonitor/OVEStandard.pyo
>> /usr/share/ovsdbmonitor/OVEUtil.py
>> /usr/share/ovsdbmonitor/OVEUtil.pyc
>> /usr/share/ovsdbmonitor/OVEUtil.pyo
>> /usr/share/ovsdbmonitor/Ui_ConfigWindow.py
>> /usr/share/ovsdbmonitor/Ui_ConfigWindow.pyc
>> /usr/share/ovsdbmonitor/Ui_ConfigWindow.pyo
>> /usr/share/ovsdbmonitor/Ui_FlowWindow.py
>> /usr/share/ovsdbmonitor/Ui_FlowWindow.pyc
>> /usr/share/ovsdbmonitor/Ui_FlowWindow.pyo
>> /usr/share/ovsdbmonitor/Ui_HostWindow.py
>> /usr/share/ovsdbmonitor/Ui_HostWindow.pyc
>> /usr/share/ovsdbmonitor/Ui_HostWindow.pyo
>> /usr/share/ovsdbmonitor/Ui_LogWindow.py
>> /usr/share/ovsdbmonitor/Ui_LogWindow.pyc
>> /usr/share/ovsdbmonitor/Ui_LogWindow.pyo
>> /usr/share/ovsdbmonitor/Ui_MainWindow.py
>> /usr/share/ovsdbmonitor/Ui_MainWindow.pyc
>> /usr/share/ovsdbmonitor/Ui_MainWindow.pyo
>> /usr/share/ovsdbmonitor/qt4reactor.py
>> /usr/share/ovsdbmonitor/qt4reactor.pyc
>> /usr/share/ovsdbmonitor/qt4reactor.pyo
>>
>> thx,
>> kishore
>>
>> From: K.R Kishore <krkish...@yahoo.com>
>> To: Kyle Mestery (kmestery) <kmest...@cisco.com>
>> Cc: "discuss@openvswitch.org" <discuss@openvswitch.org>;
>> "krkish...@yahoo.com" <krkish...@yahoo.com>
>> Sent: Wednesday, June 5, 2013 10:24 AM
>> Subject: Re: [ovs-discuss] Problems getting OVS to work on RHEL/KVM
>>
>> Hi Kyle
>> Thanks for responding.
>> I went back and followed the instructions in INSTALL.RHEL again and still no
>> luck..slightly different errors though.
>>
>> 1. Step 6 calls for building OpenVswitch userspace: 'rpmbuild -bb
>> rhel/openvswitch.spec'
>> - I get the following error:
>> /usr/lib/rpm/find-debuginfo.sh --strict-build-id
>> /root/rpmbuild/BUILD/openvswitch-1.10.0
>> extracting debug info from
>> /root/rpmbuild/BUILDROOT/openvswitch-1.10.0-1.x86_64/usr/sbin/ovs-vswitchd
>> *** ERROR: No build ID note found in
>> /root/rpmbuild/BUILDROOT/openvswitch-1.10.0-1.x86_64/usr/sbin/ovs-vswitchd
>> error: Bad exit status from /var/tmp/rpm-tmp.fNzzkw (%install)
>>
>> This is referring to the ovs-switchd it just built
>> [root@lab-sj1-140 openvswitch-1.10.0]# ls -l
>> /root/rpmbuild/BUILDROOT/openvswitch-1.10.0-1.x86_64/usr/sbin/
>> total 8932
>> -rwxr-xr-x 1 root root 44709 Jun 5 09:55 ovs-bugtool
>> -rwxr-xr-x 1 root root 3459332 Jun 5 09:55 ovsdb-server
>> -rwxr-xr-x 1 root root 5639898 Jun 5 09:55 ovs-vswitchd
>>
>> The INSTALL.RHEL indicates that there might be some issues due to buggy or
>> missing kernel-devel package. I followed the instructions in step 1 &2 and
>> undid the link to build dir and redid the link to the
>> /usr/src/kernel/<target>. Repeated the build and the problem persists.
>>
>> 2. Step 7b (I am using RHEL6.4) calls for using one of several rpmbuild
>> options
>>
>> [root@lab-sj1-140 openvswitch-1.10.0]# rpmbuild -bb -D "kversion
>> 2.6.32-131.6.1.el6.x86_64" -D "kflavors default debug kdump"
>> rhel/openvswitch-kmod-rhel6.spec
>> error: Failed build dependencies:
>> kernel-kdump-devel is needed by openvswitch-kmod-1.10.0-1.el6.x86_64
>> [root@lab-sj1-140 openvswitch-1.10.0]# yum install kernel-kdump-devel
>> Loaded plugins: aliases, changelog, downloadonly, kabi, presto,
>> refresh-packagekit, security, tmprepo,
>> : verify, versionlock
>> Loading support for Red Hat kernel ABI
>> Setting up Install Process
>> No package kernel-kdump-devel available.
>> Error: Nothing to do
>>
>> I removed the debug and kdump flavors and the rpmbuild completed
>> successfully (as it did yesterday). It put a new rpm into
>> $HOME/rpmbuild/RPMS/x86_64/ and I re-installed the packages using 'rpm -ivh
>> --force <...rpm>'
>>
>> The problems I have outstanding are:
>> 1, userspace rpm did not build correctly at all..how do I resolve this?
>> 2. I followed the instructions in INSTALL (not the .RHEL) and did a 'make &&
>> make install' and it created the various ovs-xxx binaries
>> 3. I do not see the systemd script you mentioned (I presume it gets
>> installed after the userspace rpm is installed?)
>> 4. I do not see the 'systemctl enable openvswitch.service' command you
>> mention in either INSTALL.RHEL or INSTALL. Where is the systemctl command?
>> Is it installed as part of a different package?
>>
>> Many thanks for your time.
>> Kishore
>>
>> From: Kyle Mestery (kmestery) <kmest...@cisco.com>
>> To: K.R Kishore <krkish...@yahoo.com>
>> Cc: "discuss@openvswitch.org" <discuss@openvswitch.org>
>> Sent: Wednesday, June 5, 2013 9:00 AM
>> Subject: Re: [ovs-discuss] Problems getting OVS to work on RHEL/KVM
>>
>> On Jun 4, 2013, at 7:13 PM, K.R Kishore <krkish...@yahoo.com> wrote:
>>
>> > Hi
>> > I have installed the latest version of OVS (1.10) on RHEL 6.4 with KVM and
>> > running two VM's on it. I followed the instructions per INSTALL.RHEL and
>> > INSTALL.KVM but had some problems during the process, but it looks like
>> > the install itself was successful.
>> > The install problems were:
>> > • yum install kernel-kdump-devel (Error: no package ..available).
>> >This resulted in only one (default) rpm being generated
>> > • make install could not install on /usr/local/bin/ because it was
>> >read-only file system (even when I was root). Redid the configure with a
>> >different destination and it seemed to work. (not clear if this in itself
>> >is a problem.
>> > After the install,
>> > • Started ovsdb server
>> > • ovsdb-server
>> >--remote=punix:/usr/local/var/run/openvswitch/db.sock \
>> >--remote=db:Open_vSwitch,manager_options \ --pidfile --detach
>> > • ovs-vsctl --no_wait init
>> > • Started open vswitch daemon
>> > • ovs-vswitchd --pidfile --detach
>> > • setup the bridge
>> > • ovs-vsctl add-br ovsbr0
>> > • ovs-vsctl add-port ovsbr0 p4p1
>> > •
>> > •
>> >
>> > After this I expected to see the bridges on ifconfig output, but I do not.
>> > dmesg tail shows:
>> >
>> > openvswitch: Open vSwitch switching datapath 1.10.0, built Jun 3 2013
>> >16:04:10
>> >
>> > Looking at the 'ps -ef' output shows ovsdb-server, ovs-vswitchd (2
>> > processes) and [ovs_workq] running. ovs_workq is owned by root, the others
>> > by the user.
>> >
>> > I went through the discussion archive and suggestions to similar problems
>> > were
>> > • Look through ovs-vswitchd.log - I do not find this file anywhere,
>> >where is it? did my install go wrong?
>> > • Create a new VM after creating the bridge - I tried that, but there
>> >is no bridge with the name I created to assign to the newly created vm
>> > ovs-vsctl shows the new interfaces and bridge created, but are these just
>> > showing the registered names? how do I debug this?
>> > thx,
>> > Kishore
>> >
>> INSTALL.RHEL indicates you should build RPMs. Did you really follow
>> INSTALL.RHEL? It will also install a systemd script to start/stop OVS during
>> boot. After you install the RPMs built by following the directions in
>> INSTALL.RHEL, make sure to do a "systemctl enable openvswitch.service".
>>
>> Thanks,
>> Kyle
>>
>> > _______________________________________________
>> > discuss mailing list
>> > discuss@openvswitch.org
>> > http://openvswitch.org/mailman/listinfo/discuss
>>
>>
>>
>>
>
>
>
openvswitch.spec
Description: Binary data
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
