Bug 1649495 - Insight-client core egg hasn't been updated after --no-upload (without registering)
Summary: Insight-client core egg hasn't been updated after --no-upload (without regist...
Keywords:
Status: POST
Alias: None
Product: Cloud Software Services (cloud.redhat.com)
Classification: Red Hat
Component: Client
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: jcrafts
QA Contact: Pavol Kotvan
Kevin Blake
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-13 17:52 UTC by Eduard
Modified: 2020-02-07 05:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Eduard 2018-11-13 17:52:21 UTC
Description of problem:
The version of insights-core hasn't been updated.
Insights-client installed from the base repo.


How reproducible: 100%


Steps to Reproduce:
#yum -y install insights-client
#insights-client --version
Client: 3.0.3-9
Core: 3.0.4-3

#insights-client --no-upload
#insights-client --version
Client: 3.0.3-9
Core: 3.0.4-3

Actual results:
Core: 3.0.4-3


Expected results:
Core: 3.0.58-1


Additional info:

Comment 1 Eduard 2018-11-14 12:41:45 UTC
Reproduced another case, when insights-client hasn't been updated.

Steps to reproduce: 
1. Provision fresh vm
2. install client from base repo "yum -y install insights-client" 
3. insights-client --version
   Client: 3.0.3-9
   Core: 3.0.4-3

4. insights-client --register
5. insights-client --version
   Client: 3.0.3-9
   Core: 3.0.58-1

6. insights-client --unregister
7. yum -y remove insights-client
8. yum -y install insights-client
9. insights-client --register
10. insights-client --version
     Client: 3.0.3-9
     Core: 3.0.4-3

Comment 2 jcrafts 2018-11-14 13:22:17 UTC
^^ That case is a known bug because etags are mistakenly not removed on uninstall. It has been patched and will be included in the next RPM release.

Comment 3 Lindani Phiri 2018-11-14 13:28:42 UTC
@Jeremy,

Is there a workaround for the etag bug?
Seems like an important issue to resolve given our reliance on egg updates.

Lindani

Comment 4 jcrafts 2018-11-14 13:30:33 UTC
Currently the only workaround is to delete the *.etag files in /etc/insights-client


Note You need to log in before you can comment on or make changes to this bug.