2925
100%
master: 100%

Ran 28 Aug 2020 07:36AM UTC

Jobs 1

Files 37

Run time 2s

Badge

Embed ▾

pending completion

Build # 2925

Build Type

push

travis-ci

Committed by

tmuntaner

Commit Message

Write Config Even During Failure Conditions

We noticed a problem in RMT that came from a failure logic in
SUSEConnect.

* A server is registered against RMT with SUSEConnect, but that product
  isn't mirrored yet in RMT.
* As the Connect API announce endpoint does not verify that a product is
  mirrored, RMT has no idea that a subsequent call will try to activate
  an unmirrored product.
* The server is announced to RMT, so RMT gave it credentials which are
  saved on the server.
* During the activation phase, RMT tells the server it can't activate,
  so the registration process in SUSEConenct errors and the config isn't
  written.

The problem is that SUSEConnect already got the credentials from the
RMT server, but because it errored, it didn't save /etc/SUSEConnect to
know where those credentials are valid. Instead, we should save
/etc/SUSEConnect, as the system is valid in RMT, it's activation just
isn't and can be fixed without a deregistration.

Run Details

1210 of 1210 relevant lines covered (100.0%)

18.01 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	2925.1 (2.1)	28 Aug 2020 07:36AM UTC	0	100.0	Travis Job 2925.1

Source Files on build 2925

Detailed source file information is not available for this build.

SUSE / connect / 2925
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 2925

SUSE / connect / 2925 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 2925

SUSE / connect / 2925
100%
master: 100%

README BADGES
x