You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "frank zhang (JIRA)" <ji...@apache.org> on 2013/07/31 20:53:48 UTC
[jira] [Resolved] (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:all-tabpanel ]
frank zhang resolved CLOUDSTACK-3894.
-------------------------------------
Resolution: Fixed
ipset has been added to centos repo since 6.4. Now you should be able to search it even in centos6.2.
if you still suffer this problem, open http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os to get a repo and add it to your yum configuration file.
> 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
> Assignee: frank zhang
> 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