-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCP - zypper being blocked by other process during salt deployment #875
Comments
@lpalovsky I could not reproduce the issue with Also, I cannot find any Is this an error that breaks the deployment or is it only informational? Also, having the full log would help finding when this actually happens and which components might run the |
@yeoldegrove Hello, sorry for late reply. I have been on vacation last week. I did run the deployment again and it looks like the registercloudguest is at fault. I will put logs below.
salt-result.log
salt-os-setup.log
|
@lpalovsky We had issues/bugs with Maybe to debug this further, you could try installing different versions of This versions works fine for me on a SLES4SAP 15 SP4:
You could use this command to apply the specific salt state by hand locally on the system:
If you find anything related to |
@yeoldegrove Hmm... looks like the version might be the case:
This seems to be newest version on the host. Need to check where is the problem. Test from openqa seems to be passing, I will try as well what package version is it using. |
Did some poking around and found few things.
I did run the registercloudguest manually and command passed fine:
After that I was able to update cloud-regionsrv-client to 10.0.4-150000.6.73.1, but the salt-call still fails:
|
@lpalovsky I did quite a few deployments yesterday with the official os images:
|
Used cloud platform
GCP
Used SLES4SAP version
SLES15SP3
Used client machine OS
SUSE linux
Expected behaviour vs observed behaviour
Issue happens after product registreation while salt is attempring to run "zypper product" command.
This occured with both OpenQA based deployment and manual one.
I tried both 'master' branch and tag "8.1.5"
How to reproduce
Used terraform.tfvars
The text was updated successfully, but these errors were encountered: