Ticket #830 (closed enhancement: fixed)

Opened 13 years ago

Last modified 12 years ago

RPMng unspecified epoch in Instance causes verify to fail

Reported by: Owned by: desai
Priority: trivial Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-client Version: 1.0
Keywords: RPMng verification epoch Cc:


If an 'Instance' of a package does not include the 'epoch' attribute package verification will fail, e.g.,:

Verifying package instances for mod_ssl

Wrong version installed. Want 1:2.2.3-31.el5.centos.2.x86_64, but have 1:2.2.3-31.el5.centos.2.x86_64 Package mod_ssl failed verification

Defining the 'epoch' attribute: <Instance epoch='1' version='2.2.3' release='31.el5.centos.2' arch='x86_64'/>

causes the verification to succeed as expected.

I am filing this as desai wanted to take a look. Now that I know 'epoch' is an attribute I don't think this is a bug. I would rather define 'epoch' than bcfg2 guess at the correct version.


Change History

comment:1 Changed 13 years ago by solj

  • Milestone changed from Bcfg2 1.1.0 Release to Bcfg2 1.2.0 Release

comment:2 Changed 12 years ago by desai

  • Status changed from new to closed
  • Resolution set to fixed

This issue is resolved with the re-written yumng.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.