Deregister after integration tests

[Sergeykot]

No description provided.

[suse-tests-pass]

	1 Warning
⚠️	Unless this is a trivial change, please include a CHANGELOG entry. Run osc vc in the package directory to add one.

Generated by 🚫 Danger

[Sergeykot]

changed because had network issues locally inside of docker container

[thutterer]

You are de-registering only a system.
I haven't looked over the full test suite but I'm guessing this is a system you register against that test-RMT earlier? Then this would not be required, since you wipe out the full RMT including its database, right?

What is required instead and what I meant in the review meeting is that you have to make sure to remove any traces from that test-RMT itself from SCC.

Since you create these test-RMTs from scratch each time, they have a new uuid each time, then hit the SCC API which leads to new proxies in the SCC database. Just have a look at https://scc.suse.com/proxies?current_organization=70 😉

[ikapelyukhin]

Do those tests even register the system in SCC at all?

[Sergeykot]

@ikapelyukhin I register RMT host system in order to install packages
@thutterer the system I deregister is the one RMT installed on. I also added now setting the system UUID so that it will be always the same

[ikapelyukhin]

During which phase? If the system is being registered during docker build phase, it would be better to deregister right after.

[Sergeykot]

@ikapelyukhin I do deregister it in post stage of Jenkinsfile. Isn't that "right after" ?

[ikapelyukhin]

By "right after" I mean in docker build. The container doesn't need to be registered to run the tests, and it would prevent potential issues with caching or Jenkins not executing the post stage of the pipeline for some reason.