You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/07/29 11:25:49 UTC
[jira] [Commented] (CLOUDSTACK-3894) upgrade of KVM agent failed on
rhel 6.2 with ipset
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722290#comment-13722290 ]
Wei Zhou commented on CLOUDSTACK-3894:
--------------------------------------
it is ok on CentOS 6
[root@cs-kvm013 ~]# yum list | grep ipset
ipset.x86_64 6.11-1.el6 @base
ipset.i686 6.11-1.el6 base
ipset-devel.x86_64 6.11-1.el6 base
[root@cs-kvm013 ~]# yum repolist
Loaded plugins: fastestmirror, presto, security, versionlock
Loading mirror speeds from cached hostfile
* base: mirror.nl.webzilla.com
* epel: mirror.nl.leaseweb.net
* extras: mirror.nl.webzilla.com
* updates: mirror.nl.webzilla.com
repo id repo name status
base CentOS-6 - Base 6,381
epel Extra Packages for Enterprise Linux 6 - x86_64 9,349
extras CentOS-6 - Extras 13
updates CentOS-6 - Updates 1,023
repolist: 16,766
[root@cs-kvm013 ~]# cat /etc/yum.repos.d/CentOS-Base.repo
[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
#released updates
[updates]
name=CentOS-$releasever - Updates
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib
#baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
> upgrade of KVM agent failed on rhel 6.2 with ipset
> ----------------------------------------------------
>
> Key: CLOUDSTACK-3894
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3894
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Environment: KVM host on rhel 6.2
> Reporter: shweta agarwal
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Installed 3.0.3 KVM agent on Rhel 6.2
> Trying to Upgrade to CloudPlatform-4.2-dbupgrade-64-rhel6.2
> Failed with following message
> --> Finished Dependency Resolution
> Error: Package: cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64 (cloud-temp)
> Requires: ipset
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
> NOTE: it first failed with JSVC dependency failure
> Which I resolved by manually installing
> FOR IPSET I enabled first epel repo on my KVM agent
> yum repolist
> Loaded plugins: product-id, security, subscription-manager
> Updating certificate-based repositories.
> repo id repo name status
> epel Extra Packages for Enterprise Linux 6 - x86_64 9,349
> rhel rhel6 3,529
> repolist: 12,878
> still IPSET is shown as no package found.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira