When building off master, I receive the following errors:
./build_product rhel7
........ Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_enhanced.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_high.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_intermediary.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_minimal.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/C2S-docker.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/docker-host.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/rhelh-stig.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ansible-tower-upstream.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-http-disa.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ipa-server-upstream.profile. . Skipping None.Could not parse profile /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-satellite-upstream.profile.
The ssg-rhel7-ds.xml appears built successfully. "xccdf info" shows the profiles and I'm able to scan a host. But not sure what those output lines mean -- any pointers?
On Wed, Apr 3, 2019 at 4:49 PM Shawn Wells shawn@redhat.com wrote:
When building off master, I receive the following errors:
./build_product rhel7
........ Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_enhanced.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_high.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_intermediary.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_minimal.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/C2S-docker.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/docker-host.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/rhelh-stig.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ansible-tower-upstream.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-http-disa.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ipa-server-upstream.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-satellite-upstream.profile.
The ssg-rhel7-ds.xml appears built successfully. "xccdf info" shows the profiles and I'm able to scan a host. But not sure what those output lines mean -- any pointers?
These profiles are set as documentation_complete: false, and the
build_rule_playbook.py is skipping them during build time.
_______________________________________________
scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/scap-security-guide@lists.fedor...
On 4/5/19 7:16 AM, Watson Sato wrote:
On Wed, Apr 3, 2019 at 4:49 PM Shawn Wells <shawn@redhat.com mailto:shawn@redhat.com> wrote:
When building off master, I receive the following errors: > ./build_product rhel7 > > ........ > Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_enhanced.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_high.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_intermediary.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_minimal.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/C2S-docker.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/docker-host.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/rhelh-stig.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ansible-tower-upstream.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-http-disa.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ipa-server-upstream.profile. > . Skipping None.Could not parse profile > /media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-satellite-upstream.profile. The ssg-rhel7-ds.xml appears built successfully. "xccdf info" shows the profiles and I'm able to scan a host. But not sure what those output lines mean -- any pointers?These profiles are set as documentation_complete: false, and the build_rule_playbook.py is skipping them during build time.
Thank you!
Does it make sense to start a "build errors FAQ" or some other place to document common errors and what they mean? Where could be the best place for that?
Originally though something under docs/, but not sure if a wiki page is better/easier. Leaning towards everything as code though.
Personally, I don't see the benefit of these errors that are mentioned, and they should be removed.
On Fri, Apr 5, 2019 at 3:49 PM Shawn Wells shawn@redhat.com wrote:
On 4/5/19 7:16 AM, Watson Sato wrote:
On Wed, Apr 3, 2019 at 4:49 PM Shawn Wells shawn@redhat.com wrote:
When building off master, I receive the following errors:
./build_product rhel7
........ Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_enhanced.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_high.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_intermediary.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/anssi_nt28_minimal.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/C2S-docker.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/docker-host.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/rhelh-stig.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ansible-tower-upstream.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-http-disa.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-ipa-server-upstream.profile.
. Skipping None.Could not parse profile
/media/psf/src/ComplianceAsCode/content/rhel7/profiles/stig-satellite-upstream.profile.
The ssg-rhel7-ds.xml appears built successfully. "xccdf info" shows the profiles and I'm able to scan a host. But not sure what those output lines mean -- any pointers?
These profiles are set as documentation_complete: false, and the
build_rule_playbook.py is skipping them during build time.
Thank you!
Does it make sense to start a "build errors FAQ" or some other place to document common errors and what they mean? Where could be the best place for that?
Originally though something under docs/, but not sure if a wiki page is better/easier. Leaning towards everything as code though. _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/scap-security-guide@lists.fedor...
On 4/5/19 6:14 PM, Gabe Alford wrote:
Personally, I don't see the benefit of these errors that are mentioned, and they should be removed.
Imagine if you're a developer making a profile and it's not appearing in the datastream after a build. Would be frustrating you forgot to switch the documentation_complete option to true.
If we tweak/adjust the error message this could be prevented, e.g. "Skipping profile $foo because documentation_complete set to false"
With the current message it wasn't clear if this was a problem I should be concerned about, if something is going wrong, if there's an error, of if the output is expected/informational.
True, but the problem is that these error messages are thrown all over the place in the build process making it very, very difficult to determine where the issue truly is.
For example,
[ 90%] Built target generate-ssg-rhel7-guide-index.html [ 90%] Built target rhel7-guides [ 90%] Built target generate-ssg-sl7-guide-index.html [ 90%] Built target sl7-guides [ 90%] Built target sl7 [ 90%] Built target generate-ssg-centos7-guide-index.html [ 90%] Built target centos7-guides [ 90%] Built target centos7 Could not parse profile /home/ralford/development/testing/scap-security-guide/rhel7/profiles/stig-ipa-server-upstream.profile. . Skipping None.Could not parse profile /home/ralford/development/testing/scap-security-guide/rhel7/profiles/C2S-docker.profile. . Skipping None.[ 90%] Built target generate-rhel7-ansible-playbooks [ 90%] Built target rhel7-content [100%] Built target generate-rhel7-table-srg [100%] Built target rhel7-tables [100%] Built target rhel7
With how it is listed above, how am I to know that there is not something wrong with the centos build target? Also, do you know that this error is only generated for building playbooks and not for the rest of the content?
On Fri, Apr 5, 2019 at 4:22 PM Shawn Wells shawn@redhat.com wrote:
On 4/5/19 6:14 PM, Gabe Alford wrote:
Personally, I don't see the benefit of these errors that are mentioned, and they should be removed.
Imagine if you're a developer making a profile and it's not appearing in the datastream after a build. Would be frustrating you forgot to switch the documentation_complete option to true.
If we tweak/adjust the error message this could be prevented, e.g. "Skipping profile $foo because documentation_complete set to false"
With the current message it wasn't clear if this was a problem I should be concerned about, if something is going wrong, if there's an error, of if the output is expected/informational. _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/scap-security-guide@lists.fedor...
On 4/5/19 6:39 PM, Gabe Alford wrote:
True, but the problem is that these error messages are thrown all over the place in the build process making it very, very difficult to determine where the issue truly is.
For example,
[ 90%] Built target generate-ssg-rhel7-guide-index.html [ 90%] Built target rhel7-guides [ 90%] Built target generate-ssg-sl7-guide-index.html [ 90%] Built target sl7-guides [ 90%] Built target sl7 [ 90%] Built target generate-ssg-centos7-guide-index.html [ 90%] Built target centos7-guides [ 90%] Built target centos7 Could not parse profile /home/ralford/development/testing/scap-security-guide/rhel7/profiles/stig-ipa-server-upstream.profile. . Skipping None.Could not parse profile /home/ralford/development/testing/scap-security-guide/rhel7/profiles/C2S-docker.profile. . Skipping None.[ 90%] Built target generate-rhel7-ansible-playbooks [ 90%] Built target rhel7-content [100%] Built target generate-rhel7-table-srg [100%] Built target rhel7-tables [100%] Built target rhel7
With how it is listed above, how am I to know that there is not something wrong with the centos build target? Also, do you know that this error is only generated for building playbooks and not for the rest of the content?
All legitimate! What do you suggest?
scap-security-guide@lists.fedorahosted.org
-
Gabe Alford -
Shawn Wells -
Watson Sato