Bug 1359787

Summary: Running satellite-installer --scenario satellite --upgrade --noop resulted in an error.
Product: Red Hat Satellite Reporter: Andy MacMurray <amacmurr>
Component: Docs Release NotesAssignee: satellite-doc-list
Status: CLOSED DUPLICATE QA Contact: satellite-doc-list
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: adahms, inecas
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
The installer --nood option
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-08 11:29:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
noop log file. none

Description Andy MacMurray 2016-07-25 12:50:13 UTC
Created attachment 1183789 [details]
noop log file.

Description of problem:
Running satellite-installer --scenario satellite --upgrade --noop resulted in an error (below). It is thought that perhaps the error is due to the answer.yaml file containing credentials that may mismatch the actual credentials in our environment. 

It was explained that this error may be benign and that we should proceed. If this is indeed the case, then a note needs to be added to the upgrade documentation indicating that this error may be ignored

A note may also be required asking the user to review the YAML files.


Upgrade Step: remove_nodes_distributors (noop)...
Upgrade Step: Running installer...
 /Stage[main]/Foreman::Database::Postgresql/Postgresql::Server::Db[foreman]/Postgresql::Server::Role[foreman]/Postgresql_psql[CREATE ROLE foreman ENCRYPTED PASSWORD ****]: Could not evaluate: Error evaluating 'unless' clause, returned 512: 'psql: could not connect to server: No such file or directory
 /Stage[main]/Candlepin::Database::Postgresql/Postgresql::Server::Db[candlepin]/Postgresql::Server::Role[candlepin]/Postgresql_psql[CREATE ROLE candlepin ENCRYPTED PASSWORD ****]: Could not evaluate: Error evaluating 'unless' clause, returned 512: 'psql: could not connect to server: No such file or directory
Installing             --- /etc/foreman-proxy/settings.d/dns.ymllinux.cf2016-07- [99%] [...........................................................................................Installing             Done                                               [100%] [...............................................................................................]
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/foreman-installer/satellite.log
Upgrade failed during the installation phase. Fix the error and re-run the upgrade.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ivan Necas 2016-07-26 11:34:20 UTC
It seems the problem is that the noop is actually not creating the files, while some puppet resources in the module expect the files to be there and fail since the files are missing.

Comment 2 Bryan Kearney 2016-07-26 18:54:04 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 3 Ivan Necas 2016-07-29 14:52:24 UTC
The full-functional noop in puppet, what's our installer based on is not trivial to do (see [1] for some more details). I'm afraid we can't do more than having note about this behavior in our documentation.

[1] - http://stackoverflow.com/questions/24313147/missing-resources-when-running-puppet-agent-noop

Comment 4 Andrew Dahms 2016-08-08 11:29:19 UTC
Hi Ivan,

Thank you for raising this bug.

A variation on this issue has also been noted in BZ#1362234, where it is now being actively addressed.

I am close this bug as a duplicate for now, but will copy over your comments into that bug so that they can be tracked together there.

Feel free to reach out to us in that bug for further comments and questions.

Kind regards,

Andrew

*** This bug has been marked as a duplicate of bug 1362234 ***