Modify ↓
Ticket #911 (closed enhancement: fixed)
bcfg2 output for wrong package version with Packages is misleading
| Reported by: | m4z <[email protected]…> | Owned by: | https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc |
|---|---|---|---|
| Priority: | minor | Milestone: | Bcfg2 1.2.0 Release |
| Component: | bcfg2-client | Version: | 1.0 |
| Keywords: | Cc: |
Description
1.0.1, with plugin Packages (and YUMng, I assume).
Scenario: Client machine with outdated packages runs bcfg2(-client) with "-n". To a newbie like me, the following output is unintuitive:
[...] Package sysconfig failed verification. Wrong version installed. Want 0:2.88-10.1.1.x86_64, but have 2.88-9.4.x86_64 Package sysvinit failed verification. [...]
Contrary to my initial assumption, the version information is regarding sysvinit, not sysconfig.
Attachments
Change History
comment:1 Changed 12 years ago by solj
- Owner changed from desai to solj
- Status changed from new to accepted
comment:2 Changed 12 years ago by solj
- Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.2.1 Release (Bugfix)
comment:3 Changed 12 years ago by https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc
- Owner changed from solj to https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc
comment:4 Changed 11 years ago by https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc
- Status changed from accepted to closed
- Resolution set to fixed
- Milestone changed from Bcfg2 1.2.1 Release (Bugfix) to Bcfg2 1.2.0 Release
This is resolved in https://github.com/solj/bcfg2/commit/bd0fd1c4c32864414b60b51828c79198503cb3f6
Note: See
TracTickets for help on using
tickets.
Can you check whether this is coming from YUMng or RPMng? I just want to make sure we fix the problem in the right place.