LB did not serve deployed file, 100 days of DevOps (day:77)

[readoy]

While completing 100 days of DevOps day:77 (Jenkins Deploy Pipeline) on KodeKloud task, I ran into a confusing issue

Error shown: “LB did not serve deployed file” — but interestingly:

• The Load Balancer was returning the correct output
• curl from the terminal was also showing the expected response

So everything seemed to be working fine from both the LB and backend side, but the validation still failed.

I’ve attached screenshots for better clarity

:LB did not serve deployed file

[Santosh_KodeKloud]

Please refer to this solution and see if it helps.

[readoy]

I have already try this solution, but the problem is : task is updated ,

---

The development team of xFusionCorp Industries is working on to develop a new static website and they are planning to deploy the same on Nautilus App Server using Jenkins pipeline. They have shared their requirements with the DevOps team and accordingly we need to create a Jenkins pipeline job. Please find below more details about the task:

Click on the Jenkins button on the top bar to access the Jenkins UI. Login using username admin and password Adm!n321.

Similarly, click on the Gitea button on the top bar to access the Gitea UI. Login using username sarah and password Sarah_pass123. There under user sarah you will find a repository named web_app that is already cloned on App Server 1 under /var/www/html. sarah is a developer who is working on this repository.

1. Add a slave node named App Server 1. It should be labeled as stapp01 and its remote root directory should be /home/sarah/jenkins_agent (the repository is cloned under /var/www/html; the agent uses a separate directory so it does not pollute the repo).
2. We have already cloned repository on App Server 1 under /var/www/html.
3. Apache is already installed on the app server and is running on port 8080.
4. Create a Jenkins pipeline job named nautilus-webapp-job (it must not be a Multibranch pipeline) and configure it to:

Deploy the code from web_app repository under /var/www/html on App Server 1, as this is the document root of the app server. The pipeline should have a single stage named Deploy ( which is case sensitive ) to accomplish the deployment.

---

I have complete following this but, system cannot received the solution,

[rob_kodekloud]

As near as I can tell, your pipeline looks reasonable, although you can even simplify it further. Note that /var/www/html on stapp01 is already set up with the repo and belongs to the sarah user. So even the following very simple pipeline should work for this task:

pipeline {
    agent { label 'stapp01' }

    stages {
        stage('Deploy') {
            steps {
                script {
                    sh '''
                        cd /var/www/html
                        git pull origin master
                    '''
                }
            }
        }
    }
}

[readoy]

Its working Now, thanks for the response